Once DBase is split

  • Thread starter Thread starter Linda
  • Start date Start date
L

Linda

Hi,

Knew I had a 3rd question. Now that I have split my DB,
the copy that I keep separate for development, does it
need to be linked to a copy of the Data or do I just need
the Table with the objects only without the link?

Thanks again to those who can help!!

Kindest regards,
Linda
 
For data-safety it is probably best to keep a development copy of both the
data & the application...
 
Hi,

Knew I had a 3rd question. Now that I have split my DB,
the copy that I keep separate for development, does it
need to be linked to a copy of the Data or do I just need
the Table with the objects only without the link?

Thanks again to those who can help!!

Kindest regards,
Linda
Click to expand...

For development purposes, you should have the tables linked so that
the environment in which you're developing is the same as the eventual
production environment. You must have the tables *somewhere* - none of
your objects will work without them!

You may want to have two separate backends: the "production" backend,
with real, live data being used by your users; and a separate copy
with data which you can use to test update queries or other operations
which would make changes to data. You don't want to discover that you
have the wrong criteria on a Delete query by erasing the past month's
data entry!
 
Linda said:
Hi,

Knew I had a 3rd question. Now that I have split my DB,
the copy that I keep separate for development, does it
need to be linked to a copy of the Data or do I just need
the Table with the objects only without the link?

Thanks again to those who can help!!

Kindest regards,
Linda
Click to expand...

It is really up to you. Often, you will keep your front end attached to the
production data. However, what about routines that either delete data, or
update lots of data? If there is a bug, or problem during testing, surly you
don't want to develop on live data?

Once you test the deleting code, the update code, and who knows what else,
then, and ONLY then would you link to the production data. Of course you
also likely create mde (that ensures no compile code errors) and then
distribute that new mde to EACH of the uses pc's.


It seems to me to be far better to make a copy of the back end data and link
to that. This way, you are complete free to develop, test delete code, test
update code...and can play and make as many mistakes as people like me do!
But at least I make the mistakes on a COPY of the data!

I suppose if one was really careful, and you experience very few bugs, and
all your code works well the first time..then I would stay attached to the
actual production data.

I am just not that good enough of a developer to be able to risk my clients
real data like that during development. Your situation and amount of
development experience may very well be different them mine.
 
Back
Top