How is ADO/DAO affected when splitting a db?

[Julia Boswell]

Apologies if this is a duplicate post. I've had a look through postings and
found quite a lot on this subject but have ended up more confused than
before!

I have a 2003 db that uses mainly ADO and a few bits of DAO (where ADO is
not so good). It's currently not split and used directly on a network
directory, but I'm proposing to split it as there's a proposal for more
users to be introduced to it.

I've not used the db splitter before and am nervous regarding the effects on
the ADO/DAO code. Here are the questions:

1) When splitting the db, do I need to amend any code or will it work as it
is?
2) Does it make any difference if the front end is stored on a network
directory or should a copy be sent to each user for placing on their C
drive, and will this have an effect?
3) If I need to make any amendments in the future will I need to write the
code differently or can I do it the same as before (e.g. does Set db =
CurrentProject.Connection recognise the back end?)
4) Is there anything else I should be aware of?

Thanks in advance for your help.

Julia

 

[gandalf]

1)Probably but not too much
(Linked tables can replace locally stored)
2)each user should have a local copy of the front end
(in mdb or mde format)
to avoid risc on corruption...
3)Not sure, probably you will have to store a connection
to the backen
4)So far I read, keep a connection alive to the backend
and turn the autocorrect feature off.

Have a look at these sites
more of them specifically have an issue on split db's

http://www.granite.ab.ca/access/corruptmdbs.htm
http://www.able-consulting.com/ado_conn.htm
http://www.mvps.org/access/api/api0001.htm

http://www.mvps.org/access/tables/tbl0009.htm
http://accdevel.tripod.com
http://members.rogers.com/douglas.j.steele/AccessReference
Errors.html
http://www.lebans.com/mousewheelonoff.htm
http://support.microsoft.com/?id=258049
http://www.mvps.org/access/general/gen0005.htm
http://www.trigeminal.com/usenet/usenet001.asp?1033
http://www.pksolutions.com

mailmerge

http://www.attcanada.net/~kallal.msn/msaccess/msaccess.html
http://appdevissues.tripod.com

inventory control:
http://members.iinet.net.au/~allenbrowne/AppInventory.html

 

[Julia Boswell]

Thanks for the response. I've had a look at the sites you referenced, and I
can't really find anything specifically to help with this problem.

Could you give me any more clues, especially regarding (1) and (3).

Thanks
Julia

 

[Albert D. Kallal]

1) When splitting the db, do I need to amend any code or will it work as it
is?

Your code should work as is. The only function that don't work is seek
command via DAO (and there is a work around for that). You 6 are NOT using
the seek command...so don't worry.

2) Does it make any difference if the front end is stored on a network
directory or should a copy be sent to each user for placing on their C
drive, and will this have an effect?

Yes..it makes a huge difference. ONE reason why you are splitting is because
you NEVER want to allow multiple users into the same code mdb. So EACH pc
MUST get a copy of this front end. For the last 10 years every piece of
software you purchased goes on each pc. You install word on your pc. You
install Excel on each pc. Now that YOU ARE the software developer and
creating software...then you MUST do the same as everyone else. You can
certainly share some word doc on the server..but you don't install word ON
the server. So, keep in mind the difference between some data that you
share..and how you share applications!. You MUST NOT have multiple users in
the application part.

3) If I need to make any amendments in the future will I need to write the
code differently or can I do it the same as before (e.g. does Set db =
CurrentProject.Connection recognise the back end?)

There is no difference. Just make sure when you link the tables..you use UNC
path names.

4) Is there anything else I should be aware of?

There is can be some performance problems if you do NOT keep a connection
open to the back end. That connection can be some form that loads..or some
code that runs to open a table on the back end. You want to KEEP the
connection open at all times.

There is a great perfomance faq you can read here:

http://www.granite.ab.ca/access/performancefaq.htm

 

[Tony Toews]

2) Does it make any difference if the front end is stored on a network
directory or should a copy be sent to each user for placing on their C
drive, and will this have an effect?

As Albert states you must give each user their own copy of the FE.

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version. For more info on the errors or the Auto FE
Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm