Question Access 2003 db in win 7

Sorry if this has been answered. I did a search and saw it loosely discussed here and there but I figured I'd post my issue fresh.

I got very comfortable using MS Access 2003. I tried poking around 2007 and had a hard time finding anything and I haven't even looked at 2010 yet. One of these days, I know. But for now I'm sticking with 2003 for my development purposes.

So I have my db split into a front end and back end where the .mde is put on users local drives and the back end is on a network (about 40 users total). Now (yes just now) finally all new computers are coming with win 7 and MS Access 2010. When I try to run the db on these pcs I get a "32 bit database cannot run on a 64 bit machine" (or some such) error. So I can't seem to run the database at all. This of course is a massive problem.

Right now we've got most users on XP but all new computers have the above config. It's going to be some time before everyone is caught up, so until then it's going to be a mix and match. Most have access 2007 now but some like me still have 2003 even. Until this there have been no compatibility issues.

How can I at least get my database to run on these win7 machines? Do I need to get the 32-bit version of access 2010 installed or is there something less extreme I can try first?

I have never seen any problems with 32 v 64 bit Windows so don't worry about that just yet.

I have noticed moving from Win XP to Win 7 that there has been some Focus problems with Forms and Sub Forms. This may have been fixed with Microsoft's updates.

Leave your Back End as 2003.mdb. I don't know of any problems there.

So this just leaves the Front End which is currently 2003. Don't convert it until you have fixed all problems and keep that mdb as your development copy.

Do I need to get the 32-bit version of access 2010 installed or is there something less extreme I can try first?

Click to expand...

I have heard a few things but have no hands on experience. I think you will find that Access comes in both 64 and 32 bit versions.

I would be keen on removing Office 64 then reinstall the 32 bit version. Also with the new machines see if they can be delivered in that configuration.

Once that is done have a look at any problem you may be left with. Then go looking for the solution.

One more thing I would suggest you do is to wait until you get other opinions. I would like to hear what "Bob Larson" has to say about the issue. He is fairly well versed with this.

I agree. It sounds like the problem is the 64-bit office. The only advantage (and I'm not sure it is a real advantage) is that the 64-bit version of Excel supports humongous workbooks. IMNSHO, they should be using a relational database if they have that much data. So, uninstalling the 64-bit version of Office and replacing it with the 32-bit (on the same DVD, same product key) will probably fix the problem. It is not possible to mix and match so you can't have 32-bit Access and 64-bit everything else so if they refuse to go to the 32-bit version, you will need to convert the database to A2010 and that means that EVERYONE will need to upgrade to use the database.

Steve,

Pat has experience in this area so I suggest you take notice of her.

Once you get this problem fixed, you can continue to use 2003 as the Front End. There may be some fixes required, but I run a 2003 DB in a multi user environment.

It has anything from Vista to Win7 mostly 64 bit. And they run Access 2003, 2007 and 2010. I did have some problems at first but it does work as an MDE file.

The most important thing now is to convert back to 32 bit.

Cheers.

Ooh, interesting update. I have 2 databases and somehow one of them runs without error on a couple of the newer PCs with win 7. On those machines, one of the databases runs fine, the other hits the error. Both databases were created in the same way, both from Access 2003. Weird. (and for the record, now I have the error below). But seems the easiest way to resolve is to install 32-bit of Access 2010. Now I just have to convince IT to do so.