Enter Parameter Error - For no reason

[okerix]

Hello,
I am having a bit of a strange issue with Access 2007. I have an access frontend with an SQL backend for my application. There is a report I have that is rather complex and pretty big. About 1 page full of fields and the Query consists of multiple queries to make one final one. In addition there are a couple of subreports embedded into the report. To make this possible I have two id fields on the report that are set to be invisable but are used by the various subreports/fields that require some additional querys. The two id fields have always been there and are never deleted.

So to run the report someone opens a form and from the dropdown selects the manager and pushes the button. For some reason the user is then prompted with the "Enter Parameter Value" popup and asks for those two id fields idCase and idChild. The thing is the fields are still there! So I have to remove the fields and readd them and the reports work again once or twice and then it messes up again. I even changed the fields to visable and made their color white and it is still doing it.

In addition, it is happening in one persons front-end database but not the others. I have no clue what is going on with it or why it repeatedly cannot find the fields. Hopefully someone can provide me a little insight on where to look for the issue.
Thanks,
Shaun

 

[the_net_2.0]

is it possible that the one person's form or report is corrupt? or the entire front end file?

happening on one machine and not the others is odd, if the same file was distributed to everyone. do the users have executables or the original developed file? if they have the original, is it possible that the one person could have added a couple of lines of code, or something they thought would work, and causes the popups?

 

[boblarson]

Usually if you get the parameter prompt like that and you aren't expecting them, it is because you either have misspelled something or are trying to reference a field, or object, which doesn't exist in the current tables/queries, etc.

 

[boblarson]

Or also you might have a Sort/Grouping in the report defined for that field but it isn't in there anymore.

 

[CraigDolphin]

Another thing to try is to wrap the criteria parameter reference in the record source with an eval function.

ie: instead of:
Forms!Yourform!Yourfield
try:
Eval("Forms!Yourform!Yourfield")

Sometimes this helps resolve parameter prompts in various situations. Sometimes not. Easy to try though

 

[okerix]

the_net - You might be right about that. We have two version of the front end file one for each manager(theme differences and differences in whats defaulted in). So maybe I through the other managers on there computer and try that. Maybe it is corruption and I need to just rebuild that managers front-end file. I will get back to you on that. The managers dont code or change the db at all. They only make there own queries thats about it. I just give them the access file not an executable.

Bob - I have checked all the reports parameters and nowhere in there is there any sorting or grouping using these fields. Plus the fields have not gone anywhere they are still there. It's nothing misspelled because I can delete and readd the field without any issues and then after a couple of runs it will fail again. I just used the standard name from Access so that never got changed.

Thanks for the responses guys. I will check int othe corruption of the front end file.

 

[okerix]

Okay got an update. It is definitely an issue with just the computer. I can use either front end file which work perfect on my computer and on other people’s computers and they fail on hers. Another thing I found out is that after I delete the field and readd it it will work until we close the database and then upon opening it up again it will fail again and the fields have to be readded. So something about closing the databases on her computer causes those fields to not be recognized I guess. Craig I will try that as well

 

[boblarson]

Open the database on their computer and then go to the VBA window and to TOOLS > REFERENCES. Check to see if any are marked MISSING. If so, uncheck them and close and reopen. If none are marked MISSING uncheck the DAO one if it is checked and then close the dialog and then reopen it and scroll down the list and reselect the DAO reference.

 

[okerix]

Hey Bob,
I checked her references and none were missing and I dont use DAO but I do use ActiveX Data Objects 6.0 reference and I removed and readded that and BOOM it worked! I even shut down the DB mutliple times and it continued to work. You were spot on with the diagnosis of a corrupt reference. Thanks Bob for the answer and everyone else for your time and ideas!

 

[boblarson]

Glad we could help.