Help! I just normalized my database

D

Deb

I'm one of those inexperienced database people who ended
up with a d/b with 120 fields. I'm getting a lot of
the "Too many fields defined" errors on update. I have
researched and now know how to normalize my database. I
have many tables now. My database is for customers to
track there loan status. It has fields like.. name,
address, date of app, lender, appraisal ord, appraisal
rec, closing date set etc......
I can't figure out how to set up relationships in Access
2002. Each borrower wil will have a record in all tables.
When I use the wizard to set up tables it asks will there
be a record in the Borrower Table that matches many
records in the Address Table or vice versa. It doesn't ask
will there be 1 record in each table that matches 1
records in all the tables. Can someone please help me. I'm
very frustrated!
 
P

Peter N Roth

Hi Deb -

If each lender has a record in each table, then it sounds
like the normalization could use some more work.

In an oversimplified database, the Borrowers table will have the fields
BorrowerID, Lastname, Firstname, Street, City, Zip, Phone, etc.
and the Loans table will have fields
LoanID, Amount, DateofLoan, DateDue, Rate, ... BorrowerID
where the BorrowerID is what connects the tables.

This is not trivial stuff. Most likely you'd get Real Good responses
in an Access NG. Also, study some of the databases Access provides
via templates

--
Grace + Peace,
Peter N Roth
Engineering Objects International
http://engineeringobjects.com
Home of Matrix.NET
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top