I have a report that is run by using a custom built dialog screen. If the user chooses the "Print" command button, no problem, the report prints. If the "Print Preview" command button is chosen the reports comes up as normal in the print preview mode.
Here is the problem. If the user clicks "Print Preview" then from the print preview screen they click to print it the report prints but not before an error that states,
"...database engine does not recognize 'tblCurrentMaint.*' as a valid field name or expression."
I am just trying to figure out where I can trap this error. Any ideas? What event runs differently when you print from print preview window versus just printing it outright not previewing first.
Too add the report changes recordsets based on what the users chooses in the dialog box but again why do I get an error one way but not the others.
DB, Access2k.
thanks
Remember the Past, Plan for the Future, yet Live in the Now for tomorrow may never come.
-etrain
Here is the problem. If the user clicks "Print Preview" then from the print preview screen they click to print it the report prints but not before an error that states,
"...database engine does not recognize 'tblCurrentMaint.*' as a valid field name or expression."
I am just trying to figure out where I can trap this error. Any ideas? What event runs differently when you print from print preview window versus just printing it outright not previewing first.
Too add the report changes recordsets based on what the users chooses in the dialog box but again why do I get an error one way but not the others.
DB, Access2k.
thanks
Remember the Past, Plan for the Future, yet Live in the Now for tomorrow may never come.
-etrain