E
Erin
I asked this question at xmas without response...hope
somebody sees it and can help this time:
I created a db in Access 2000. There are several reports
which are each built upon several parameter queries. I use
a form to ask for the parameter which then supplies the
parameter to all queries and prints the parameter in the
report. On opening the report the macro opens the form
asking for user input, the OK button on the form hides the
form, keeping it open, so the queries can access the
parameter. Closing the report closes the form. This is
straight from Access Help files and is something my users
use daily. It has always worked beautifully.
I upgraded to Access 2003 and now the macro errors at the
SetValue action (Object: my input form, Property:
[Visible] Value: No). Sometimes I get the message that I
need to register my Active X control, but I am only using
the standard command button on the form toolbox. I have
seen a few other posts here describing a similar problem.
Does anyone know about how to solve this? Please! is this
a bug with 2003? I can't allow my company to install the
upgrades we already obtained if the databases won't work
after!
Thanks for your help.
somebody sees it and can help this time:
I created a db in Access 2000. There are several reports
which are each built upon several parameter queries. I use
a form to ask for the parameter which then supplies the
parameter to all queries and prints the parameter in the
report. On opening the report the macro opens the form
asking for user input, the OK button on the form hides the
form, keeping it open, so the queries can access the
parameter. Closing the report closes the form. This is
straight from Access Help files and is something my users
use daily. It has always worked beautifully.
I upgraded to Access 2003 and now the macro errors at the
SetValue action (Object: my input form, Property:
[Visible] Value: No). Sometimes I get the message that I
need to register my Active X control, but I am only using
the standard command button on the form toolbox. I have
seen a few other posts here describing a similar problem.
Does anyone know about how to solve this? Please! is this
a bug with 2003? I can't allow my company to install the
upgrades we already obtained if the databases won't work
after!
Thanks for your help.