To Split or Not to Split

[CDM]

I have developed a database four my department that is working quite well. IT
wants to distribute it to multiple locations, but they don't like the split
database design. We work in a Citrix enviornment and I'm wondering if that
reduces the need for a split database especially since maintaining the FE
for every remote location (which I'm sure will be dumped in my lap) might be
difficult. Each location would have its own data.

 

[John Spencer]

IF the data is unique to each computer (or client) and you don't share the
data among computers (users) then you don't need to split the database.
HOWEVER, if you don't split the database, then updating the forms, reports,
macros, etc can be a major problem.

So if you share data or need to update the non-table objects of the database,
it is a very good idea to split and a very bad idea not to split.

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

 

[tedmi]

As John notes, the problem with not splitting is the process of making
changes to the forms, reports and queries. With a monlithic db, here is the
procedure you need to follow:
1. Make sure that all users are out of the database.
2. Make the database unavailable to end users.
3. Make your changes/additions to forms, reports, queries, VBA code, etc.
4. Test, test, test.
5. Test some more
6. Make the database available again.

What is your dept. boss' tolerance for the length of time for steps 3-5?

 

[Larry Daugherty]

Something that may not have been emphasized in the other responses is
the fact that with the split application you need only make your
changes one time, then compile your application and make an MDE/ACCDE
and distribute that **E version to all of your users. It your
application remained monolithic then you'd either need to change the
design of each copy or (better) import all of the tables from that
user's old copy into their new one. Still very awkward.

Look up Front End Updater on Tony Toews's site.

As for people using Citrix server or Terminal Server, wouldn't their
applications reside on the Server rather than on the client machine?
That would be true whether split or not.

HTH

 

[Tony Toews [MVP]]

I have developed a database four my department that is working quite well. IT
wants to distribute it to multiple locations, but they don't like the split
database design.

You've already got your answer but why don't "they" like the split
database design? What's the problem with that approach?

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/