Redesign of database to transition from unique to multiple records

A

Ann Scharpf

(My session seems to have timed out, so I am reposting. I apologize if this
is a duplicate.)

I have a database I used all last year. One of the primary tables in it is
a funding source table. Among the fields on this table are, a project number
(the key) and a funding document number. I have just found out that there
can be MULTIPLE funding documents linked to a single project number, so my
current table design is no good.

Can you please let me know if this plan of attack makes sense:

1. Add another table to the database that will consist of only three
fields: project number, funding document number and funding amount.

2. Write a query that produces an output with the same columns that were in
the original table. The query will calculate the total funding amount for
each project and us the concatenate (function that someone has posted here)
to include all the funding document numbers associated with the project.

3. Edit the SQL of every query that is linked to the old funding source
TABLE and change it to use the new funding source QUERY. Field names will
stay the same, so nothing else should change.

I am still fairly new at building databases and am not sure if anything can
“blow up†with my planned changes. I’d appreciate any feedback you
experienced database designers can give me. Thanks a lot!
 

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