Access 2003 Problems

[Friday]

Anyone out there experience problems when moving up to Access 2003? We have two new machines in our department that came with Office 2003. One of them is in my office. The other machine is in another city. When that user tried to open a front end/back end db, the reported corruption and wouldn't work. I sent the user a back-up copy of the front end (at the time, I wasn't aware they were using A2003). Same problem. Found out about the new version (cursed the user for not telling me first). Copied the back-up front end to my new machine, got the same errors. Built an entirely new front end with A2003, same problem. Built an entirely new db, with new tables and data, just as a test, and encountered the same problem. Does this sound like a installation problem, or has someone else experienced this?

 

[seth_belgium]

I would guess it's the installation... If you restarted from scratch and it still corrupts, better do a reinstall.

Seth

 

[Friday]

That's pretty much what I thought. This is going to be fun. Corporate Help Desk has to do the uninstall and re-install, though they know nothing about Access. Explaining problems like this to them is usually a lonnnnnng process.

 

[ghudson]

You have a lot more fun ahead of you.

Ensure that the users gets the latest SP2 update for Office 2003 and also has the latest Jet update installed.

Search around for there are plenty of posting discussing the new fun stuff you need to be aware of with Access 2003.

 

[Friday]

Had a new install done, same problem. Checked version, it already has latest SP installed. Updated Jet version to latest. Same problem. I give up...

 

[boblarson]

Curious, because I took several A2K databases and moved them to A2K3 with no problems (also frontend/backend split - in fact also replicated).

You may want to try this out:

Open up any A2K3 database and then click on the Tools / Options menu. Then, go to the Advanced tab and select Access 2000 as the default file format. Click OK and then close Access.

Then, try opening up the other database.

 

[Friday]

Thanks, Bob I'll try that sometime this week.