Can U mix 2003 and 2010 Access Front-ends

Does each user have their own seperate copy of the database FE? Or are the users sharing the same copy of the FE (e.g. you've placed the FE on a network share, and all users launch it via that network share)?

If each user has their own copy, then we'll need some more information.

If your users are sharing the same copy, then you'll have to change this so that each user has their own copy of the FE. Users running Access 2003 or earlier cannot share the same database as users running 2007/2010. In fact, this should be your design paradigm regardless of whether your users are running the same versions of not. Running sepearte copies of the FE tends to be more stable (i.e. less corruption), you have fewer issues with recordlocking, and performance typically is much better, especially as you add users to the mix.

Hi there LSM,

Yes, everyone has their own copy of the FE and they all point to the same BE.

Cheers,

John

Hmmm ... then I'd first see if you can recreate this using 2003, and see where your code is failing. I'd also try to redeploy a fresh copy to those 2003 users to see if there is something amiss with their local copy.

Okay. I don't think there is a coding issue as it works on most others but I could give them a fresh copy I suppose...

John,

"Blank gray screen" comes up as a symptom of a read-only database. Check that the users with A2003 can read, write, create, and delete files in the directory of the back end.

pT72

Hi Pt72,

Hmmm, interesting. I'm not getting any messages of any kind. Does that sound like the correct symptoms?

If your users could access the system prior to the changes, then their permissions should be okay. It never hurts to check permissions, of course.

I assume you're using Access User Level Security?

A blank grey screen generally indicates your startup form hasn't loaded (assuming you're using a startup form, of course). You might try temporarily choosing a different form as the startup form to see if that one shows.

Have you made changes in the database since users were migrated to 2010? If you have, did you use 2003 or 2010 to make those changes? If you used 2010, you could have some reference issue. The fix for that is to do your development work (or at least your final compile) in Access 2003.

LSM,

Also Interesting. I did make a small fix after I had been migrated to 2010 which may have coincided with my problems. This may all be academic as the two users have now been migrated but I think you may be on the right track. Absolutely no messages appeared which seems odd though...

"That's seems to be the norm with this sort of issue, however."

This is somewhat misleading. I didn't mean that this is the norm with ALL reference issues, just with this specific reference issue. In most cases, if you have missing or invalid references, Access will just refuse to start.

Wow. Thanks for your help. I think you may have cracked it although all users have now been migrated! You still desrve full marks for this.

Can I be cheaky and ask a quick question. I haven't been actively compiling my vba.

Should I do this?, Will it make it quicker?

Cheers...

Anyway, Cheers

< I haven't been actively compiling my vba. >

You should compile your application regularly. It helps to iron out troublesome code before it becomes too firmly entrenched in your app, and can sometimes speed up your app.