Splitting a Database

[Gary.]

Good Idea Or Bad?

Thanks again

 

[Douglas J. Steele]

Good idea. No question.

 

[Gary.]

Good idea. No question.

What are some of the reasons why?

 

[Keith Wilby]

What are some of the reasons why?

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

Keith.
www.keithwilby.com

 

[Douglas J. Steele]

Take a look at what Tony Toews has at
http://www.granite.ab.ca/access/splitapp/index.htm (or, more specifically,
http://www.granite.ab.ca/access/splitapp/why.htm)

A shared application, especially, should always be split. Only the back-end
(the tables and relationships) should be on the server: each user should
have his/her own copy of the front-end (the queries, forms, reports, macros
and modules), ideally on his/her hard drive.

 

[Albert D. Kallal]

What are some of the reasons why?

Good question!! No one wants to be told "just do it!!!".

You do need the "whys".

I explain the "why" here:


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

 

[George Nicholson]

While reading the sites suggested by other respondents, keep in mind that
this isn't an "it would be nice and slick to do it the way the MVPs do"
issue, its a "this is how Access was designed to be used and you'll have
lots of problems with a shared app if you don't" issue.

HTH,