It worked when appending parameters individually, and command type = adCmdStoredProc. More code, but workable.
Bryant --- In [email protected], "Tom Oakes" <[EMAIL PROTECTED]> wrote: > What was the issue with the ADO code? > > Tom Oakes > Personal PC Consultants, Inc. > [EMAIL PROTECTED] > 503.230.0911 (O) > 402.968.6946 (C) > 713.583.7091 (F) > > > > _____ > > From: [email protected] > [mailto:[EMAIL PROTECTED] On Behalf Of Bryant > Sent: Monday, July 18, 2005 1:35 PM > To: [email protected] > Subject: [AccessDevelopers] Re: ADO parameters for action query > > > Hi Dawn, > > I'd just gotten that to work before you posted that! :) It's more > lengthy than DAO, but at least it works. > > I'll post something I was doing with ADOX and which failed silently, > to see if I can get some guidance on it ... maybe the prob with > different values being returned from ADO and DAO will solve that one > as well. > > Thanks, > Bryant > > --- In [email protected], "Crosier, Dawn" > <[EMAIL PROTECTED]> wrote: > > I am able to use this type of code for a parameter query in SQL > > > > Dim cmd As ADODB.Command > > Dim rst As ADODB.Recordset > > Set cmd = New ADODB.Command > > > > 'Retrieve all the Customers associated with a specific Client > > With cmd > > .CommandText = "qryClientAddress" > > .CommandType = adCmdStoredProc > > .ActiveConnection = CurrentProject.Connection > > .Parameters.Append .CreateParameter("@ShortCaseCaption", adVarChar, > > adParamInput, _ > > 100, strShortCaseCaption) > > Set rst = .Execute > > End With > > > > I don't know if it will help you or not, but..... > > > > Dawn Crosier > > Application Specialist > > "Education Lasts a Lifetime" > > > > > > ________________________________ > > > > From: [email protected] > > [mailto:[EMAIL PROTECTED] On Behalf Of Tom Oakes > > Sent: Monday, July 18, 2005 2:21 PM > > To: [email protected] > > Subject: RE: [AccessDevelopers] Re: ADO parameters for action query > > > > > > Yeah, I'm having the same problem when testing this. I tried manually > > appending the parameter object, but it doesn't seem to take it. If you > > can get around using the saved query, you can do it in ADO by building > > your SQL statement and using adCmdText. If not, I'd stick with DAO or > > ADOX, assuming they get the job done. > > > > What does your ADOX code look like? > > > > Tom Oakes > > Personal PC Consultants, Inc. > > [EMAIL PROTECTED] > > 503.230.0911 (O) > > 402.968.6946 (C) > > 713.583.7091 (F) > > > > > > > > ________________________________ > > > > From: [email protected] > > [mailto:[EMAIL PROTECTED] On Behalf Of Bryant > > Sent: Monday, July 18, 2005 12:00 PM > > To: [email protected] > > Subject: [AccessDevelopers] Re: ADO parameters for action query > > > > > > That gave an error 3265 (Item cannot be found in the collection > > corresponding to the requested name or ordinal.) It makes sense to > > have tried that, since it's the way to do it with SQL Server. Having > > gotten that error previously, and being stuck on the > > adCmdStoredProc/adCmdText area, is where I headed out to ADOX. > > > > Bryant > > > > > > Please zip all files prior to uploading to Files section. > > > > _____ > > YAHOO! GROUPS LINKS > > > > * Visit your group "AccessDevelopers > <http://groups.yahoo.com/group/AccessDevelopers> " on the web. > > > * To unsubscribe from this group, send an email to: > [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > > * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service > <http://docs.yahoo.com/info/terms/> . > > > _____ Please zip all files prior to uploading to Files section. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AccessDevelopers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
