Hi,
First thanks for your time to read and maybe respond to this question.
I have a new client with an ADO database on a server being used by
three users. Not split, everyone uses the same one. So I made a copy
of the database, changed the name on the original (as a backup) and set
them up with front ends linked to the back end....Oh my gosh now it
takes 5 minutes to open a form. So I got rid of what I did and put
back there original with the original name. Now the only difference is
that I gave them a shortcut on their desktop that goes to the db on the
server instead of them opening Access directly. I made one fix in a
report "a label was missing" and when I left it was much faster then
the split database.
Now the client calls and says the computers I "worked" on are running
very slow and their db is taking longer to open then before.
I don't know ADO I have always worked in DAO...what could I have
possibly done to their database????? I don't believe I did anything, I
think its perception after they saw the split db work. But I wanted to
ask the experts here if there is any way I may have mucked it up????
I wasn't going to do any heavy work on this db without knowing more
about ADO but I thought what I did was safe.
Thanks,
Debbie
Steve - 22 Dec 2005 17:31 GMT
Try running a Compact and Repair on the database on the server.
Incidentally, running Compact and Repair on the front ends and back end
right after you made the changes could have also helped increase
performance. Also, if you are using a version of Access prior to 2002,
you can try decompiling it (/decompile switch in commandline).
If you didn't change any of the code I don't see any reason to assume
ADO has anything to do with the computers' slowdown. Access bloats:
fact of life with Access.
Br@dley - 22 Dec 2005 22:46 GMT
> Hi,
> First thanks for your time to read and maybe respond to this question.
[quoted text clipped - 19 lines]
> Thanks,
> Debbie
What do you mean by 'ADO database'?
An MDB is an MDB. You can use ADO instead of DAO when coding but the
MDB, table linking etc is the same generally. ??
What version of Access are they using?
There is no way I an see that a shared MDB on a network drive would run
slower when split if it's done properly.

Signature
regards,
Bradley
A Christian Response
http://www.pastornet.net.au/response
David W. Fenton - 22 Dec 2005 23:58 GMT
> There is no way I an see that a shared MDB on a network drive
> would run slower when split if it's done properly.
Sure it can be -- it could be the overhead of opening and re-opening
the LDB file on the server that is to blame for the slowdown. The
solution is the old cached link to the back end.
Tony Toews performance FAQ has details on it.

Signature
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
debbie - 29 Dec 2005 15:52 GMT
Yes a database is a database, I figured if I said ADO you all would
know I meant the code. Sorry for any confusion. I didn't change any
code so whether there is a cached link or not, did not change...but the
customer has noticed a changed and assumes it was because I was there.
I just wanted to make sure there wasn't something I might have done
inadvertantly. The compact/repair is definately an idea...when they
open again after the first of the year I will walk the user thru that.
Thanks again for you time, energy and expertise.
Debbie