Splitting DB Needed???

[Guest]

I'm building a db that is going to be used by a single user on a single
machine. It is not going to be in a server environment. What are the
advantages to splitting the db into FE/BE? I can understand it in a multiple
user environment but I can not see the need for a single user setup.

 

[Guest]

Even then there is one very good reason to split: Recovery from corruption.
Usually a Compact and Repair or a JetComp can fix a corruption problem with
tables; however, they are pretty useless when a form, report, or code
corrupts. Therefore having all them in a front end reduces the possibility
that a corruption issue would lose everything. Just reverting to a backup of
the FE would get them back up and running again.

A second advantage would if you need to make changes to a form, report, etc.
The customer could email you a zipped up copy of the FE. You could make the
changes and email it back. No down time for your customer. Now if you have to
make changes to the BE, that's a different story.

 

[Guest]

1. The front end can be further developed independently of the real data and
remotely from it by using a development copy of the data against which
changes in the front end can be tested without affecting the integrity of the
real data. Its then simply a case of replacing the old front end with the
new one.

2. Backing up the data only is possible, making the back-up files smaller
and eliminating the redundant storage of the unchanging front end objects in
each back up file. One-click backing up of the data can easily be undertaken
from within the front end.

3. Should the front end become corrupt its simply necessary to replace it
with a back up copy.

4. Should it be decided at any time in the future to upsize to a multi-user
environment you can be confident that the functionality within the front end
will still work.

Ken Sheridan
Stafford, England

 

[aaron.kempf]

please explain how this is 'one-click backup'

****ing retards from england; we should have attacked england in WWI
instead of germany

 

[aaron.kempf]

front ends dont just 'go corrupt' if you use Access Data Projects

of course, backends don't either

but if you went with a reliable platform like ADP then these dipshits
wouldn't be able to sell you on support / maintenance

 

[aaron.kempf]

I had a boss once that REFUSED to let me split a MDB into frontend and
backend.

she just thought that it made it 'too complex' while reducing some
functionality

I thnk that splitting is worthless as best; if your tool keeps on
failing you then LOSE THE TRAINING WHEELS AND MOVE TO ADP