Re-designing and re-working database

[Anne]

I wrote this database for payroll input, the data which is then being
transmitted to a leasing company. It was my first database and it really does
a lot of things like keeping track of the jobs. However, every time I have to
make a change, I find it hard to follow and I am realizing that I made a lot
of mistakes, like too many field names are duplicated. I would like to rework
it and do things properly.

For example, in my Tbljobdesc I have, 3 foremen, 3 laborers and 3
carpenters, each name belonging to 3 different locations. Is there a best way
of making a major change like that? I want to reworking it from the tables to
the relationships, but retain the existing data.


Do I start a new database and copy over? That would seem like a lot of work.
The database is split.

 

[Steve]

I have done this many times! Make a copy of your database and delete all the
data in the tables. Make the changes you want in your tables. Use append
queries to append the data in your original tables to the tables in the new
database. The fact that the new database is very similar to the original
database makes appending the data much easier. Be sure to preserve all
primary key/foreign key data in the tables.

Steve
(e-mail address removed)

 

[John... Visio MVP]

I have done this many times! Make a copy of your database and delete all
the data in the tables. Make the changes you want in your tables. Use
append queries to append the data in your original tables to the tables in
the new database. The fact that the new database is very similar to the
original database makes appending the data much easier. Be sure to preserve
all primary key/foreign key data in the tables.

Steve
(e-mail address removed)

Are you planning on behaving and NOT pester posters for work?

These newsgroups are provided by Microsoft for FREE peer to peer support.
Stevie is famous for ignoring that fact and likes to harrass posters
forwork.

John... Visio MVP

 

[Gina Whipp]

Anne,

If it were me, I start by creating a new database to import the information
into. Why don't you start with what tables you do have?

Everyone here, with the exception of Steve, will provide FREE help and
support. We will ALL, with the exception of Steve, even provide FREE coding
help and if there a sample database available for FREE we will provide a
link for you to go get it. The point is the help here is FREE, with the
exception of the help from Steve who feels the need to sell his services.
IF you decide to use the NOT FREE services then PLEASE check references!

One of the many VOLUNTEERS providing FREE services!
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[John W. Vinson]

Are you planning on behaving and NOT pester posters for work?

These newsgroups are provided by Microsoft for FREE peer to peer support.
Stevie is famous for ignoring that fact and likes to harrass posters
forwork.

John... Visio MVP

John, let's cut Steve some slack. He's actually posting reasonable answers
with no job solicitations. That's behavior we should encoursge, not attack.

 

[John... Visio MVP]

John, let's cut Steve some slack. He's actually posting reasonable answers
with no job solicitations. That's behavior we should encoursge, not
attack.

John W. Vinson [MVP]

Normally I would live his benign posts alone, except that he has not posted
in a while and and when he returned yesterday, three of his four posts were
solicitations.

John... Visio MVP

 

[Piet Linden]

I wrote this database for payroll input, the data which is then being
transmitted to a leasing company. It was my first database and it really does
a lot of things like keeping track of the jobs. However, every time I have to
make a change, I find it hard to follow and I am realizing that I made a lot
of mistakes, like too many field names are duplicated. I would like to rework
it and do things properly.

For example, in my Tbljobdesc I have, 3 foremen, 3 laborers and 3
carpenters, each name belonging to 3 different locations. Is there a bestway
of making a major change like that? I want to reworking it from the tables to
the relationships, but retain the existing data.

Do I start a new database and copy over? That would seem like a lot of work.
The database is split.

Before doing anything, I would map it out on paper and rethink the
design. Then once you have it set up properly on paper, go ahead and
build properly. Then you can use append queries to move the data
around and clean it up.

 

[Anne]

The tables are not my problem. I added key fieldsID with append queries and
changed field names. I am really taking about relatively few, but major
changes. I have one new redesigned TlbLocations, because the existing one was
causing the main problem. I had some duplication and no relationships.

However, all tables are in the backend. What is the best way of reworking
the front end without having to redo the front from scratch?

 

[Gina Whipp]

Anne,

You are asking about redoing the front-end which is usally no problem as
long as you are not adding new fields... which need to be added in the
back-end for the front-end to see. You are asking us about making changes
and we can't see what you have already, nor what it is you want to change.

Think of it like this... I need some remodeling done. I call and tell the
potential company I want some remodeling, give them my number and I hang up
the phone. See where I am going?

You need to tell us what you have and what changes you want to make before
we can suggest anything.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm