I created a DB in MS Access 2003 that generated a report without any problems.
I upgraded to MS Access 2007 and converted the DB just fine. Unfortunately, I now have some minor issues with the report generation.
1. I have a form that has a date feild. That date is used by queries which feed into the sub-reports that ultimately make it to the report. The Queries have a criteria [Forms]![Generate Report]![Date For Report]. Running the report in MS A 2007, It is as if the query does not recognize that [Date For Report] is populated. The query asks for the date in each query. Since there are 8 queries that feed info to 8 sub reports, this is pretty bothersome. What can I do to make the Queries recognize the date feild in the form?
2. A different report generation gives me an error "Prop Res DLL not loaded". Where do I start looking for a solution to this?
Thanks.
Full Version: Errors When Generating Report
QUOTE (shathway @ Mar 10 2010, 06:54 AM) 
1. I have a form that has a date feild. That date is used by queries which feed into the sub-reports that ultimately make it to the report. The Queries have a criteria [Forms]![Generate Report]![Date For Report]. Running the report in MS A 2007, It is as if the query does not recognize that [Date For Report] is populated. The query asks for the date in each query. Since there are 8 queries that feed info to 8 sub reports, this is pretty bothersome. What can I do to make the Queries recognize the date feild in the form? So, the form remains open? Also did you make sure to set your trusted location? (not a likely source of the problem but sometimes it is)
2. A different report generation gives me an error "Prop Res DLL not loaded". Where do I start looking for a solution to this?
Sounds like you have a MISSING REFERENCE. Go to the VBA Window and then to TOOLS > REFERENCES and look to see if you see one listed as MISSING. If so, uncheck it and close the dialog and then see if that helps.
2. A different report generation gives me an error "Prop Res DLL not loaded". Where do I start looking for a solution to this?
Sounds like you have a MISSING REFERENCE. Go to the VBA Window and then to TOOLS > REFERENCES and look to see if you see one listed as MISSING. If so, uncheck it and close the dialog and then see if that helps.
SOS, Thanks for the response.
Yes the form window remains open.
I will check my VBA.
Yes the form window remains open.
I will check my VBA.
enabling the Microsoft Access 12.0 Object Library in VBA got rid of the Prop Res DLL error. Thanks.
I still have the issue with the date not being read off the form. Just so you know, I am able to hit enter without putting a date in the dialog box. When the report completes, all the queries have run using the date that was in the form. So, the routine is pulling the correct date from the form. It is just annoying to hit enter 8 times to generate the report.
-Steve
I still have the issue with the date not being read off the form. Just so you know, I am able to hit enter without putting a date in the dialog box. When the report completes, all the queries have run using the date that was in the form. So, the routine is pulling the correct date from the form. It is just annoying to hit enter 8 times to generate the report.
-Steve
QUOTE (shathway @ Mar 10 2010, 09:20 AM)
enabling the Microsoft Access 12.0 Object Library in VBA got rid of the Prop Res DLL error. Thanks.
I still have the issue with the date not being read off the form. Just so you know, I am able to hit enter without putting a date in the dialog box. When the report completes, all the queries have run using the date that was in the form. So, the routine is pulling the correct date from the form. It is just annoying to hit enter 8 times to generate the report.
-Steve
I still have the issue with the date not being read off the form. Just so you know, I am able to hit enter without putting a date in the dialog box. When the report completes, all the queries have run using the date that was in the form. So, the routine is pulling the correct date from the form. It is just annoying to hit enter 8 times to generate the report.
-Steve
That usually means that there is something on the report (or sub reports in this case) that are referring to the field but has the wrong spelling.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.