Charlotte Foust
cfoust at infostatsystems.com
Wed Dec 23 11:25:04 CST 2009
It isn't clear to me what you're doing. It looked like you were referring to the form control values in the query, which is something I long ago stopped doing. Instead, you can use code to create querydef (if dao) object and set the parameters it needs in code without a direct reference to the form controls. That's what I was suggesting. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Clark Sent: Wednesday, December 23, 2009 4:36 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Try this one again I don't think I'm understanding you Charolotte...I thought that is what I was doing. Unless what you are saying, is that, instead of using a query as the source of the data, that I just put this code, behind the report itself. I guess I could have gone this way. And, I used to do this more, when I was programming more. But, this time I wanted a "backup" plan, in case it was late, or if the report didn't work correctly...they can still use the query if they had to. >>> Charlotte Foust <cfoust at infostatsystems.com> 12/22/2009 11:15 AM >>> An easier way would be to pass the required parameters for the report to the voucher report and let it populate itself either creating its SQL in code or passing the parameters to a query. Trying to make everything "see" everything else is a good way to bring on a migraine. Charlotte Foust -- 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