Steps/Process to Normalizaing an Existing Database

How bizarre.

I do not define relationships for linked tables as that's backend's job. To link only half of them is quite odd, indeed.

You should only worry about the local tables that do not depend on the linked table (e.g. lookup table for linked tables' fields, for example, normally isn't linked because backend should have it already linked with its copy of the lookup table). Ask whoever manages the backend for a relationship diagram.

HTH.
 
Img0115,

have a look at this thread http://www.access-programmers.co.uk/forums/showthread.php?t=100211&highlight=kraj

There's a tutorial in post 18 I found helpful when starting out, and a bunch of helpful links on the topic of normalization elswhere too.

However, you've got some of the best folks on the issue already having replied to you so I won't muddy the waters further.

Except to say this: if the data is critical to your business, then your company can't afford NOT to invest resources in securing it and making it accessible to those who need access. Part and parcel of that is starting with proper database design.
 
Unfortunately, I can not strip out enough information not to compromise my companys data and also to provide you with a picture of what I am trying to do. Would it help if I provided a screen shot of the current relationship window? If this doesn't help I appreciate your willingness to offer assistance. I'll just have to work it out. Thanks again.

Yes a screen shot would be a good start -
 

Users who are viewing this thread

Back
Top Bottom