By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,952 Members | 1,438 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,952 IT Pros & Developers. It's quick & easy.

Report with Subreport gets Enter Parameter Value Message

P: 68
The Problem: I have a report with one sub-report that give an Enter Parameter Value message on loading. The message appears when we open the report on a different computer than the development computer. When we go back to the development computer the error remains until we magically try something and compact/repair and the error disappears until the next time. The magical something is not consistent. For example: we could delete the link master and child fields and it will fix the issue after compacting and repairing but the next time we try this it does not fix the problem. We have not come up with any one action that fixes this or an underlying cause for the message. Below is as detail about the database, report and sub-report. Let me know if you need other information to help troubleshoot this reoccurring issue. Thanks for looking at it, I am extremely frustrated.

The Database: This is an Access Front End Database that has Linked Oracle and Access tables. In the next month or so all tables will be converted to Oracle but at this moment we are pulling data for the report from both Oracle and Access linked tables.

Data Source for Report: The report is based on a series of queries including 1 union query pulling from both Oracle and Access tables. These queries go down two paths and the final query pulls them both together with a left join. The queries are filtered from a form where the user has the option to enter parameters.

The Report: The report is set to show 2 detail records (Current and Baseline) for each Subproject in a linear view. I have grouped by SubprojectID but all the information is shown in the Detail records. The information that would show duplicates (SubprojectID, Subproject Title, Division, Status Indicator) are set to hide duplicates = Yes. There are multiple fields that are being conditionally formatted. The report also has 1 other grouping that is an expression (=1). We are using this to allow the page header of the report to show differently when the report footer (separate page) loads.

Without the Sub-report the report as described above runs great.

Data Source for Sub-report: The sub-report is based on 4 Tables (2 Oracle and 2 Access). The sub-report criteria is all set in the query (either hard coded or functions i.e. Month(Date()) ) and does not pull from the parameters. We are counting on the linking fields (SubprojectID) in the report and sub-report to limit the data on the report.

The Sub-report: The sub-report shows 1 field (Comments associated with the SubprojectID). The sub-report groups by SubprojectID but like the report the data is all in the detail. The sub-report also sorts by 3 other fields that are in the query and not showing in the sub-report. There can be multiple records in the sub-report linking to the two records in the base report for each subproject.

I hope I explained this so you are able to visualize this report and can help troubleshoot the issues. Below is a picture of the report in design view


I have tried everything I can think of and am still having problems.
Attached Images
File Type: jpg Snap1.jpg (37.2 KB, 162 views)
Aug 5 '13 #1

✓ answered by zmbd

It is only a guess; however, then I suspect that your issue is the different versions. A lot of weirdness can happen when different versions start messing with stuff.

Now, I hope that all of the clients are getting their own copy of the frontend. If not, then that is your first issue and hopefully once distributed to the clients this will fix the problem(s) (HOWEVER, I doubt this will do the trick - but it's an easy fix and easy is always worth a try :) )

I think instead that you are going to have to test my hypothesis. The only way I see to test this is to take at least one of the pilot PCs and install v2010 to it. I would HIGHLY advise a complete un-install of all prior versions of Office. Reboot at least twice... have all of the OS updates installed, reboot once more after the last update. THEN and ONLY then install your Office-2010.
Then Give that pilot its own copy of the frontend and go from there. I have feeling that this will solve the issue.

Share this Question
Share on Google+
7 Replies


Expert 100+
P: 1,221
Can you run the sub-report by itself? Does it get this error sometimes/all the time?
Aug 5 '13 #2

P: 68
Yes, I can run the sub-report by itself. The Sub-report runs successfully with no message when I run it alone. Once the report get the message it will stay until we take some undetermined action then it is good until we try it on a different computer and we get the message again.
Aug 5 '13 #3

zmbd
Expert Mod 5K+
P: 5,371
Please be aware of the fact that your image is not available to most of us due to Local IT policies.
You can use the "advanced" editor to upload the image to Bytes using one of the image formats.
Aug 5 '13 #4

zmbd
Expert Mod 5K+
P: 5,371
I've heard of this happening when two different versions of Access are used... is this the case here (You are using 2007/2010 on the development PC and an older version on the other PC)?
Aug 5 '13 #5

P: 68
We are about to upgrade all computers to Access 2010 but the computers we have been pulling this report up on are not part of the pilot and have not yet been upgraded to Access 2010.
Aug 5 '13 #6

zmbd
Expert Mod 5K+
P: 5,371
It is only a guess; however, then I suspect that your issue is the different versions. A lot of weirdness can happen when different versions start messing with stuff.

Now, I hope that all of the clients are getting their own copy of the frontend. If not, then that is your first issue and hopefully once distributed to the clients this will fix the problem(s) (HOWEVER, I doubt this will do the trick - but it's an easy fix and easy is always worth a try :) )

I think instead that you are going to have to test my hypothesis. The only way I see to test this is to take at least one of the pilot PCs and install v2010 to it. I would HIGHLY advise a complete un-install of all prior versions of Office. Reboot at least twice... have all of the OS updates installed, reboot once more after the last update. THEN and ONLY then install your Office-2010.
Then Give that pilot its own copy of the frontend and go from there. I have feeling that this will solve the issue.
Aug 5 '13 #7

P: 68
I apologize for the delay in closing this thread. I have tested zmbd's theory about the issue being related to the two versions of Microsoft Access being used with this database at once. When I go into the database on a computer that uses Access 2010 and then open the database in Access 2007 I get a compile error and missing references for the Word and Excel libraries. I fix the references, compile VBA, and compact the database. Now my report runs. The odd part is the issue is happening with machines that are running Access 2007. The same actions are consistently correcting the issue. So my guess is that it has to do with the VBA not being compiled when the database was closed.

As for my users who have upgraded to Access 2010, I have created a copy of the database for them in Access 2010 and asked them to only use this database. These actions seem to have solved the issue so I am going to close this thread. Thank you all for your input and assistance with this issue.
Aug 15 '13 #8

Post your reply

Sign in to post your reply or Sign up for a free account.