Re: transferring data

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Tim Ferguson (FergusonTG_at_softhome.net)
Date: 02/17/05 

Date: Thu, 17 Feb 2005 08:58:53 -0800

=?Utf-8?B?TWF4?= <Max@discussions.microsoft.com> wrote in
news:74DA045D-22B1-48BB-A18F-B17C8CC394F7@microsoft.com:

>
> In fact, one of the things I have read on i-net sites, is that the d/b
> should be split. Today, I came across an article the gives 3 reasons
> why; I realized that the first 2 reasons disprove my need to split our
> d/b. (We do not have multiple users, nor developers, I'm the sole
> user, and I'm the only one learning to develop it.

I don't know the list you are referring to, but I can guess what the
reasons are -- in fact there are many more than three good reasons for
always splitting a db, even in a single-user, single-developer setup.

Wait until you have spent ages working on a form and then realised it's a
dead end (yes, that happens to all of us!); and then spot the fact that
you can't go back to a working backup because the data (that you have
been updating all the while) are out of date in that one. Moreover, the
simple convenience of having different front ends (for data entry, for
reporting, for mailmerges and label printing, etc) makes an invincible
argument on its own. Not to mention the ease with which you can swap
between testing and live back ends -- you don't program and test against
live data do you?

Splitting is _strongly recommended_ if you are at all serious about
moving out of the "toy database" brigade.

All the best

Tim F