Re: SOLUTION: Reports in ADP based on stored procedures; child rowset error

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Vadim Rapp (vr_at_myrealbox.nospam.com)
Date: 08/07/04 

Date: Sat, 7 Aug 2004 16:57:17 -0500

Hello Geoffrey:
You wrote in conference
microsoft.public.access.reports,microsoft.public.access.adp.sqlserver on
Sat, 07 Aug 2004 13:26:20 GMT:

 GB> It turns out that when you have a report based on a stored procedure,
 GB> and that stored procedure has more than one parameter, you can't use
 GB> the '@name = value' format any longer.

According to http://msdn.microsoft.com/library/default.asp?url=/library/en-us/off2000/html/acconOptimizeADPPerformance.asp
and also the description of InputParameters,

"If a form or report is based on a parameterized stored procedure, use the
Input Parameters property to supply the parameter values."

If you choose another (undocumented) way (i.e. you supply parameters in
recordsource), you get unpredictable results*. When you specify the 2nd
parameter, if you look at the input parameters, you notice that Access puts
there its own (wrong) interpretation of parameters - already at this point
you can see that you have confused Access.

Vadim
----------------------------------------
Vadim Rapp Consulting
SQL, Access, VB Solutions
847-685-9073
www.vadimrapp.com

*) this also applies to your workaround.

Quantcast