Problem after updating to .accdb

[Gkirkup]

I have a large application which runs fine in 2003. I am in the process of updating it to 2010 and .accdb.
I have updated a test system (front end and back end) to .accdb, but now hardly any of the programs work. I try to display a form and I get many 'Enter parameter value' error messages. All of this worked fine in 2003.
Is there something that I am missing? It seems as thought some of the queries are not working.

Robert

 

[Gkirkup]

Pat: Yes, I removed the BE links before converting the front end, and then reset the links to the .accdb BE after. I can see all of the linked tables in the front end, and all looks OK. I am mystified as to what may be wrong. Should 2003 programs work OK in .accdb, or are there limitations?

Robert

 

[Gkirkup]

Pat: Understood. I didn't explain my question very well.
What I meant was, I have programs which work perfectly in 2003. After I update my back end and front end to .accdb, should those programs still work perfectly? Or are there significant changes that I need to make when I get to .accdb?
None of my programs seem to be working. All I have done so far is to convert my FE and BE to accdb.

Robert

 

[The_Doc_Man]

I'm wondering if you are getting caught on differences in the references. I had some similar problems that were resolved by switching to the newest DAO libraries. Can't remember the details, but you should be aware that Microsoft will sometimes change the .DLL reference files on you without telling you too much about it.

 

[Gkirkup]

Doc Man: I don't use DAO, does that make any difference? It seems as though nothing works. As soon as I try to display a form, I get an 'Enter parameter value' message. I get that many times, and then Access crashes.
Does that indicate that it can't find the underlying queries? Or the tables? I could try reloading both. Just that this is not an isolated error, it happens to almost all forms.

Robert

 

[Gkirkup]

I found that many of the queries had lost their field names, and were showing EXPR1, EXPR2 etc, in place of field names. I deleted all of the queries and reloaded them, and now the application now works, though I think there is some tweaking.
One obvious change is that all forms fill the entire screen, even Switchboard. There is no setting to reduce the displayed for size. Is there a way to change that behavior, or do I have to go into every form and change the settings? I have probably 150 forms.

Robert

 

[Gkirkup]

Pat: What sort of changes are there to VBA? How will I know if a change is needed? The form will not display?

Robert

 

[The_Doc_Man]

I missed this error message at first - 'Enter parameter value' - but I'll say that 99.99% of the time, you have a spelling error. But you found the other 0.01% when you pointed out that your queries had lost some field names. That is an almost certain guarantee that you will get the 'Enter parameter value' input box. It simply means Access can't find something. So the question that really matters is where something got lost (i.e. in which step).

Is there a chance that you could repeat the process on a copy of the original database one step at a time and see when your queries lost their contents? Because it sounds (vaguely) like one of the system tables didn't copy correctly. Is there a chance that you had local tables as well as backend tables and that a query joined FE and BE tables together? Because that would invalidate all the cross-segment queries before you relinked them.

 

[Gkirkup]

Pat: I think you are correct. I started with a blank front end database (because the existing one refused to convert) and loaded all of the queries before setting up the links to tables on the back end. Many of the queries then referenced EXPR1 etc.
I deleted all of the queries and reloaded them, with the table links in place. That seemed to fix the problem.

Robert