[AccessD] Access 2016 w/MDB's

[Darryl Collins]

Sounds like the best path forward John, given the circumstances.  Access 2016 can work in MDB mode and hasn't given me any issues - but it has been a few years since I have used MDB and I cannot validate this to the level of confidence you would want.



-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bodin
Sent: Thursday, 1 March 2018 2:25 PM
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Access 2016 w/MDB's

Hi Darryl,

Customer is eventually going to have program re-written for the web and mobile app, so for now they want to keep things steady (and it has been working very well for over 15 years except for some query problems I posted about a few years ago.)  They don't want to spend the bucks on upgrading everyone to an O365 package that comes with Access 2016 or spend money on me getting 2016 runtime on all the machines.  They just bought new building so there will be the craziness of the move and prep, and they don't want to deal with any problems that tend to creep up with incompatible libraries and the like when you migrate up the Access chain.

I have an opportunity to push out a separate access app to their mobile technicians on a new RDS Server, that talks to the same tables on the back end of their existing MDB data database.  Thought I'd try and bring that to light in a new 2016 FE-format and publish on the RDS server.  It's not a major piece, so I could fairly quickly convert it back to the older MDB should problems come up that I can rectify in 2016.

Since there will be about 60 users on the system once I put the new piece on, I was looking for some validation that the 2016 FE would work or not work well with MDB BE.

Thanks,

John
-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins
Sent: Wednesday, February 28, 2018 9:49 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Access 2016 w/MDB's

Access 2016 has been the most stable version of Access I have used to date - and have been stuffing around with is since Access 2.0.
Not sure if / how this translate to your question though on using MDB and A2003 FE set up.

Any reason you cannot convert to the newer format and update the FE db(s) to suit?



-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bodin
Sent: Thursday, 1 March 2018 5:04 AM
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: [AccessD] Access 2016 w/MDB's

Do any of you have experience in running a back-end Access MDB with a front-end Access 2016 along with other A2k3 and below front-ends?  Data portion of the Database is MDB format.   I know it can be done, just have a potential multi-version access front-end project that will be banged on 10 hours a day every day and didn't know how reliable the 2016 version is running the older MDB format.  Thanks.

John

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com