Separate the front-end from the back-end for simple applications

[Top Spin]

For simple, one-person applications such as a home inventory that will
be accessed from a single PC not on a network, is there any need to
build a "back end" for the tables and a separate "front end" for the
reports and forms?

Is there any great harm in building everything in one mbd file, at
least while I am learning how databases work?

Thanks

--
Running MS Office 2K Pro
PC: HP Omnibook 6000
OS: Win 2K SP-4 (5.00.2195)
Email: Usenet-20031220 at spamex.com
(11/03/04)

 

[Rick Brandt]

For simple, one-person applications such as a home inventory that will
be accessed from a single PC not on a network, is there any need to
build a "back end" for the tables and a separate "front end" for the
reports and forms?
No.

Is there any great harm in building everything in one mbd file, at
least while I am learning how databases work?

No.

 

[Mark]

No harm that I can think of. Once you want to create a database that you
know will eventually be used in a multi-user environment, you should design
it as a Front-end/Back-end from the start. The built-in database splitter
might not make the best decisions and will probably cost you more time to
fix the splitting.

 

[Top Spin]

No harm that I can think of. Once you want to create a database that you
know will eventually be used in a multi-user environment, you should design
it as a Front-end/Back-end from the start. The built-in database splitter
might not make the best decisions and will probably cost you more time to
fix the splitting.

Great. If I ever get that skilled, I would want to do it right, right
from the start. But for learning, I'm trying to eliminate as many
variables as possible.

Thanks


--
Running MS Office 2K Pro
PC: HP Omnibook 6000
OS: Win 2K SP-4 (5.00.2195)
Email: Usenet-20031220 at spamex.com
(11/03/04)

 

[PC Datasheet]

There is a BIG advantage to splitting your databases!!

While in your development stages if you want to add/edit or delete data or
just experiment to see if what you created so far works, you just need to
make a copy of the BE file and then you can do whatever you want with the
database. When you are done doing whatever, delete the BE file you have been
using and rename the BE copy to the same name as the BE file you just
deleted. You will be then back in business with just your good data.