Splitting My DB

[S Jackson]

I have been designing a case management database now for weeks. I am now
ready to begin testing it. But, before I do that I would like to split it.
I have come across an article on the net that talks about splitting, but
since I am relatively new to all this I did not understand most of it. It
talked about not splitting your original db, not using the wizard in Access
because when you are designing and making changes to the db such as module
changes, it creates hidden tables and causes the application to "bloat" and
something about "replication." Please forgive me if this all sounds like
gibberish, but I did not understand what I was reading. I intend to go to
the MS Access Developers page and see if I can read more.

In the meantime:

I have a db that I have loaded up with data from my old db and it resides
currently out on the server. Currently, only myself and one other user
accesses the db. It runs fairly well, but I believe we would see a marked
improvement in speed if I split the db. What are your suggestions on how I
go about doing this? Do you recommend using the Access wizard to split the
db? I will need to split the database eventually as it will soon be
accessed by numerous users.

TIA
S. Jackson

 

[Immanuel Sibero]

Hi,

Your intuition about splitting is correct.
Have a look at below:

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

Can't explain Access database splitting better than the above site. It's
concise, easy to understand, and to the point.

I would follow the above steps on splitting instead of using the wizard.


HTH,
Immanuel Sibero