[AccessD] Speed Issues on network just with Access App

Darryl Collins darryl at whittleconsulting.com.au
Tue Oct 18 16:28:53 CDT 2016


Yes. I would support this 100%. Best bit is you can do it in little steps until you get familiar with it all.  Eventually you'll move everything 'server side' and just have access as a UI FE.

Stability, scalability, security and performance are all superior to using an Access BE.  Even using the free SQL Server express variant is a powerful upgrade.  In 99% of case Express will do the job brilliantly anyway.

Something to consider.

Regards
Darryl.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Wednesday, 19 October 2016 2:04 AM
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Speed Issues on network just with Access App

Lambert,

I suppose that it's not immediately relevant to your situation, but you should at least consider migrating the BE to any one of SQL Express, MySQL, MariaDB or PostGreSQL, all of which are free. The data-port is easy; besides the Microsoft migration tools, there are a couple of tools available free from Bullzip that do an excellent job of porting Access data to various "real" databases.

The difference in performance, as compared with the standard FE/BE in any format (MDB, ACCDB) is astounding. And it only gets better as you progressively migrate queries to Views and SPs. Using Access 2000 and beyond, a system I wrote supported upwards of 75 users at once, all hitting one single SQL Express database, and it far surpassed the MDB FE/BE system I replaced.

I took it a bit at a time. Step 1 was to find all the data and row sources that began with the word "SELECT", and then change them to named Access queries. That makes them portable to Views. Step 2 was to migrate the data to one of the databases mentioned previously. Step 3 was to change one test workstation to address the new database. Step 4 was to compare the performance. Step 5 was to slap my forehead and exclaim, "Why didn't I think of this sooner?"

Since then, I have never even considered an MDB BE other than for little test programs I write, and most of those don't even need a BE; they're just little one-offs to test some theory or other that I'm pondering. Other than that, I have not much use for MDBs or ACCEDBs as the back end for anything serious.

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



More information about the AccessD mailing list