[AccessD] Speed Issues on network just with Access App

[John Bodin]

Thanks Arthur.  Does make sense.  Customer not up for that challenge right now as they are flat out.  Not sure how their wallet is these day either.  I do know they are starting to stick needles in a pin cushion that looks an awful lot like me...


btw, what did you do with all the DAO links you had?  Or did you use ADO from the get go?  Did the Bullzip have any tools regarding that?


Thanks,


John






John Bodin

sBOR Office Systems

jbodin at sbor.com<mailto:jbodin at sbor.com>




________________________________
From: AccessD <accessd-bounces at databaseadvisors.com> on behalf of Arthur Fuller <fuller.artful at gmail.com>
Sent: Tuesday, October 18, 2016 11:04 AM
To: Access Developers discussion and problem solving
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