Blank screen in Access 2000 1

[dotdavid]

Hello, I wondered if anyone could help with an issue I'm having with a database.

The database was developed in Access 97, but one client has Access 2000 installed on their machine. We converted the database using Access 2000 and sent it to them but when they try to load it Access 2000 just sits at the default "unopened" grey-background state with "Ready" in the status bar. We tried manually opening the database from the File -> Open menu too to no effect.

I then sent the client a copy of the original Access 97 database and talked them through the conversion process over the telephone. The process "generated compilation errors" similar to those generated when you do not include the correct references, but on pressing "OK" and attempting to continue loading the database to correct the references the database reverts to its "unopened" grey-opened state and makes no visible attempt to load the database. This differs from our local test machine's behaviour when compilation fails, in that one you can view the forms as normal and make the appropriate changes.

As far as I can tell the Access 2000 converted database doesn't even attempt to execute any VBA code on the client's machine. I wondered if anyone else had this problem, and if there are any tweaks to Access configuration to allow us to proceed?

Thanks in advance.

 

[OnTheFly]

There are some big differences between the code of Access97 and Access2000. The most problematic is if you are using Recordsets of any kind in the code. You have to reference the type of Recordset in Access2000 if you are using DAO even if the referances are loaded.

My suggestion would be to sent them the Access97 database and have them run it as is with no conversion. They may still run into problems depending on what the database does as it will be read only so you won't be able to create or destroy some objects.

Another thing to try is to Open the database from the file open menu holding down the shift key in case there is an AutoExec that is trying to run and is failing.

Good Luck!

Hope this helps.

OnTheFly

 

[dotdavid]

Thanks for your help. It may be an issue with recordsets, but another client is running the same database on Access 2000 without any major problems - the only issue encountered was that a couple of the references needed changing.

As far as I'm aware the database doesn't load up using the shift key, but this client is one of those that "does his own thing" when you give him instructions over the phone so he may not have grasped the necessity of that action

I'll give it a try on Monday.

 

[dotdavid]

Thanks for your help OnTheFly, it turns out the issue was due to the user not having a certain Outlook reference installed - we sent them an shift unlocked database and they disabled the reference (they weren't using Outlook functionality of the system anyway). That was curious behaviour as another user also didn't have that reference installed and the error generated for them was completely different. But nevermind.

Thanks again.