Compatability across platforms

[steveg242]

I have a shared database at a university across 2 campuses with about 50 end users. I have been using Bob Larson's method of front end-back end, creating an mde and making updates from my master mdb database (Access 2003). This has been working fine for years. Then along comes win7 and Access 2010. Of course at a large university, they are not going to upgrade everyone at once. So only the new computers coming in have this platform. Others still have win XP with either Access 2003 or Access 2007.

Users with win7 could not run the mde file, which led to this discussion.

http://www.access-programmers.co.uk/forums/showthread.php?t=246830

Our solution was to uninstall the 64-bit version of MS Office 2010 and install the 32-bit version on the new computers. A pain, but it has worked.

Now -I- have gotten a new computer, this week. I hoped creating the mde from this Access 2010 machine would resolve the issue but now if I do, those with XP/ac2007 cannot run the mde. It states "This database may have been created with a later version of Microsoft Office Access than the one you are using..."


So what are my options here? I've got people with combinations of win XP, Access 2003, 2007 and win7/Access 2010. How can I create a client that can be run by everyone?

I looked through the forums and found this:
http://www.access-programmers.co.uk/forums/showthread.php?t=207837
which suggests I need a 2003 box and a 2010 box?? There has to be a better way than this.

And I haven't even thought about converting to accdb yet!

 

[Galaxiom]

The mde needs to be created on the oldest version that will be run by users.

This also affects those who use runtime. The runtime version they use must be at least the one matching the version on which it was compiled or later.

 

[Simon_MT]

Whilst, Galaxiom is right it is still providing for the "dumbest" version. How about a BE in 2003 and Front Ends 2003 and 2007. Bob Larson would get out of bed for Access 2010!

Simon

 

[steveg242]

So basically I have to compile two different mde's? Bummer. Oh well, I'll do what I have to. Thanks.

 

[Galaxiom]

No. Compile it in Access 2003 and it will work on the others.

 

[steveg242]

Then I get this error for the 2010 users:

Which means I'd be back to asking IT to uninstall the 64-bit version and install the 32-bit version of Office 2010 for all the new computers.

 

[Galaxiom]

Yes but hat is nothing to do with 2003 vs 2010 but due to the 64 bit version being installed.There is no way around this except to design and compile separate versions.


It is a pity your IT department didn't do thier homework before installing. Even Microsoft advises that there are very few reasons to install the 64 bit Office applications.

You will need three versions unless you compile the 32 bit version in Access 2003 because the 2007/10 32 bit mde will not run in 2003.

However note that Office 2003 reaches end of life next week so you really should not have to support it anyway.

 

[steveg242]

While I'm trying to come up with solutions, what about using Access 2010 runtime? I tried it on an XP laptop I have but now I get this each time:

In the full version I just go to the trust center and enable all macros. I do this when I set up the icon on every end users desktop. But I don't have that option in the runtime version. This is not a disaster but still annoying to expect all end users to deal with this message every time they launch the app.

Any idea how I disable this in runtime 2010? I did a quick google search and it looks like dealing with the registry?

 

[Galaxiom]

If you are using an mde then it can be digitally signed. Once the user accepts the signature they won't be asked again.

You can use a self signed certificate or use certsvr if you have a domain controller.I posted some information about it here. Using certsvr is a bit of a learning curve.

Unfortunately Microsoft removed this option for accd* file and only packages can be signed, adding a lot more stuffing around.

 

[steveg242]

Gah! Doesn't matter. Even when I create the mde digitally signed, I still get the "please open it with the 64-bit version of Microsoft Access."

Oh well, so I took a laptop and installed Office 2003 on it. I'll have to make my updates there from now on.