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

From: Top Spin (ToppSpin_at_hotmail.com)
Date: 02/28/05 

Date: Sun, 27 Feb 2005 19:19:16 -0800

On Sun, 27 Feb 2005 20:50:46 -0600, "Mark" <Pseudo Access Expert>
wrote:

>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

>"Top Spin" <ToppSpin@hotmail.com> wrote in message
>news:ag0521dausc67dljtv9ahp93trefkcssli@4ax.com...
>> 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)
> 

-- 
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)
Loading