When to split database

[tuesamlarry]

Should I split a new database before or after I import data into it? Am
developing a new relational database for an agency to replace their current
spreadsheet application. It will be a multi-user application on a LAN. I am
developing the database using Access 2007 but the agency will probably be
using Access 2003. Would there be any complications from this scenario? Would
appreciate your advice.

 

[Albert D. Kallal]

Should I split a new database before or after I import data into it? Am
developing a new relational database for an agency to replace their
current
spreadsheet application. It will be a multi-user application on a LAN. I
am
developing the database using Access 2007 but the agency will probably be
using Access 2003. Would there be any complications from this scenario?
Would
appreciate your advice.

Actually you can wait until fairly late into the development cycle to split.
I find the time to split is about when the table design changes settles down
to a dull roar. In the early stages, you going to be adding/changing the
tables at a very high rate. After a bit of time, that rate of change will
subside, and that is about a good time to split.

If they are using the current data your going to import, then likely you
wait until as long as possible. However, you will want to be up to speed
with a split database, and likely even test your re-link code etc.
Furthermore, if you do something in your design that runs very slow when
split, you see that instantly if you running a split system.

I talk about this "ideal" split time in the following article:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[tuesamlarry]

Albert,

Thank you very much. Hadn't seen anything on timing. Will check your article.

Larry

 

[Guillermo_Lopez]

 Albert,

Thank you very much. Hadn't seen anything on timing. Will check your article.

Larry








- Show quoted text -

Larry, Access 2007 has a runtime mode that is free. This will allow
you to create an application where your clients do not have to have
access installed.

-GL