Simutaneous usage of Access 2010 and 2013 against database

I have an Access front end which connects to two backends.  I have users will be upgrading to 2013 but over time.  I have concurrent users (about 20) and some on using Access 2010 and some on 2013.  Anyone see any problems with this.  Whenever I switch versions of access during testing, it appears Access is doing some kind of conversion or something as it takes a long time to open.
Also I know to create an ACCDE or ACCDR, you have to do that in Access 2010.  If you do in Access 2013, it won't open if the user only has Access 2010 installed.  Any words of wisdom on different versions of Access opening and updating the same database?  I'm sure this has been run into before elsewhere.
LVL 4
Keyboard CowboyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<Whenever I switch versions of access during testing, it appears Access is doing some kind of conversion or something as it takes a long time to open. >>

 That's the Office self -repair feature and there is no way to stop it.

<<Any words of wisdom on different versions of Access opening and updating the same database?  I'm sure this has been run into before elsewhere. >>

 Since each user should have their own copy of the FE, create two versions of it; one for A2010 and one for A2013 and then give them the appropriate version.

Jim.
0
Nick67Commented:
Each user should have their own front end, put on their local drive.
Then it can all play nicely.
I have concurrent A2003, A2013 and A2013 users all using the same backends.
I've built a script for distributing frontends.
This is a well-regarded distribution method
http://autofeupdater.com/
All development must take place in the earliest version of Access.

You cannot have two differing versions sharing the same front end.
You shouldn't simultaneously use front ends, anyway.
You can --like driving a car with your feet -- but you shouldn't
0
Keyboard CowboyAuthor Commented:
Thanks - Right now, they all use the same FE copy  from shared drive (I inherited this).  Actually, they're not even split into FE/BE right now - I'm doing that.  I'm looking into what's required to give them front ends individually but of course then you get into the FE distribution game.  I can't get custom purchased software approved without MONTHs of approval process reviews.  The network I'm on is hyper paranoid about anything other than trusted distributors.  

I have been able to run the same FE (same copy) with two different versions of Access at the same time though I know that's not what I want to do in production.

Thanks - info very helpful - any other thoughts from others or additional feedback.
0
Nick67Commented:
I use a VBScript to distribute the front-ends.
But if they're paranoid enough about that, then you might not be able to do that.
Group Policy can distribute files, though.
https://technet.microsoft.com/en-us/library/cc772536.aspx
Or roll them out through logon scripts
0
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
You can use a simple batch file to deploy your FE.

On each FE machine, create a Batch file that does this:

@Echo Off
Copy \\ServerName\ServerFolder\YourMasterFE.accdb C:\SomeLocalFolder\YourFE.accdb /y
Start /max "Full path to msaccess.exe on the local machine" "C:\SomeLocalFolder\YourFE.accdb"
Exit

Now create a shortcut that calls that file, and instruct users to use that shortcut when opening the file. The batch file copies over a NEW copy of the FE (and overwrites if needed), and then starts that copy. Only issue you'd have is with linking - I'd suggest you use UNC (or mapped drives) when linking. If you use mapped drives, be sure all users have the same drive mapping.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.