comparing and updating tables
Thanks for the tip....I wouldn't consider myself a developer yet
though, this is only my first Access Database, and I have only been on
it for about a month and a half. I know what you mean about that much
data movement needs automation. One of the things that I needed this
database to do was to keep track of our schedules, which would include
information like Week Of, which displays the Mondays full date then
"Through" Sunday's full date, plus who is on call , and who is on
backup on call, etc. etc. etc. Also, when a user wants to make or
change his schedule, he clicks a command button for this month, or next
month, and those dates and all relevant info has to be in the table.
So I decided to create an Automation that 'creates' records in this
schedule table and puts in all of the information. I based most of the
information data entry off of the DateValue of June30, 1999 + the
AutoNumber generated Index number of the entry. I figured that since I
was going to be the only one generating this info, it would be safe to
use the autonumber in the calculations. Anyways, back when I did that,
about a month ago, I had only been working with access for about a week
or so, and I had no 'formal' training, only a very basic, and
UNINFORMATIVE manual on Access, so I created that entire automation
sequence with macros, boy was that fun. In fact I created most of the
automation on my database with macros, but since then I have turned all
but a few macros to code. Changing those deeply involved macros, like
the schedule creation process into code was no simple task, because
macros were running macros all over the place. I'm sure you catch my
drift. Anyways, Thanks for the advice!
Quote:
> >Situation: When I want to change the format of the database, I copy
it
> >off of a public network drive into my private network drive. When I
am
> >finished, and I want to replace the old database, how can I compare
the
> >old databases Tables with the new tables, and both see/record any
> >changes, and actually change the data within the new tables, to that
of
> >the old tables.
> >The only part of the database that will change when users are on the
> >database is the data in the tables, so sure, I could delete all of my
> >tables and import the tables from the old database, but is there
anyway
> >to do that from code. Although deleting all of the tables might
change
> >what I accomplished on my 'new' database if I changed the design, or
> >created a table. Any ideas would be appreciated!
> One thing that all developers do most of the time is separate the data
> tables into a separate database from the rest of the stuff. Make a
copy
> of your database and then play with the database splitter addin.
> If you religiously keep ALL tables in the "back end" and have no other
> objects in with them you can make all the changes you need to a copy
of
> the front end and then just copy it back later.
> If you need to make changes to your table structure then prototype
them
> offline and make the changes in the evening when everyone is off the
> system. This should not be a very common event if you have got your
> design right.
> I recently wrote a set of routines that do exactly what you ask, but
> that was to handle a specific problem involving 90 (very badly
designed)
> databases that needed their table designs modifying to be Y2K
> compatible. Migrating that much data in a weekend took automation
> .
> --
> Albert Marshall
--
He who learns but does not think is lost, he who thinks but does not lea
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
