Any technique to incrementally saving as code is developed?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm looking for some wisdom on a technique or method that lets me keep track
of incremental saves to a database as I write code to automate database
functions.

Looking for anything you all have done or currently do in order to keep
track of revisions to your database.

thanks.
 
Well, actually what we do is split our database.

That means you pulled out all code and design aspects (code, forms, reports)
and made this SEPARATE from the data.

The instant you do this, then to save your "current" state, you simply make
a copy of the so called "front end".

Thus, at the beginning of a day, I open up a folder called backup, and in
inside that folder is another folder called backup. I open that folder, and
delete the application part, go back down one level, and then drag + drop
the application into the backup folder. I then go back down one level..and
am in the main develop folder..and make a copy of the current application
into the back up folder. I actually do this 3 levels deep. This means I can
go back to the last 3 days of revisions..and if I delete some code...or
change something, I can go back to the previous 3 revisions....

So, #1 on your list is to adopt a split environment, and this really solves
your problem......

I speak of splitting here:
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

You can also use source code control with ms-access (visual source safe 6
DOES work with a2003 if you download the add-in).
 
ramblinwreck said:
I'm looking for some wisdom on a technique
or method that lets me keep track of incremental
saves to a database as I write code to automate
database functions.
Click to expand...

I may be lazier than some, and want to strictly minimize the catch-up typing
I have to do, or it may be just that I have more free disk space than some.
I make a backup copy of databases on which I am "in-progress" whenever I
make a change significant enough that I don't want to re-type it if it
crashes Access. That means, in an average full day of development, I may
save ten copies of the database... I usually create a new (sub-)folder with
the current time and date for a title, and copy the database into that
folder.
Looking for anything you all have done or
currently do in order to keep
track of revisions to your database.
Click to expand...

I use a "versioning" technique to let the user's front ends determine if
they need to be replaced. You'll find some information on the topic at
http://accdevel.tripod.com, if I remember correctly.

Larry Linson
Microsoft Access MVP
 
Back
Top