Charlotte Foust
cfoust at infostatsystems.com
Mon Oct 12 10:48:31 CDT 2009
You can walk through the parameters collection. If you look back at the code I posted, it does that and when it finds a parameter you didn't include in the arguments, it pops up a dialog asking for the value. The "name" of the parameter is the prompt or unrecognized field name. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin Sent: Monday, October 12, 2009 8:45 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] AccessD Digest, Vol 80, Issue 13 Ken: I think that's what I'm looking for. In a query where you need multiple parameters, how do you identify the parameter? TIA Rocky -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kenneth Ismert Sent: Monday, October 12, 2009 8:15 AM To: accessd at databaseadvisors.com Subject: Re: [AccessD] AccessD Digest, Vol 80, Issue 13 Rocky > Thanks. Although I'm a DAO guy not and ADO guy. Can it be done in DAO? > In case someone else hasn't given a sample, handling parameters in DAO is easy: Set Db = CurrentDB() Set Qdf = Db.QueryDefs("myQuery") With Qdf .Parameters("myParm") = "Value" Set Rs = .OpenRecordset() .Close End With I have found that parameter queries are slow to load, particularly the the first time. But, if you want 'independent' parameters, where you can select values for some, and have the rest not affect the query output, you still have to use the kind of optional expressions that I described in my earlier post. -Ken -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com