Re: Sufficient reason to de-normalize a field?
From: Earl (brikshoe_at_newsgroups.nospam)
Date: 06/15/04
- Next message: Paul Clement: "Re: Insert Picture from Access"
- Previous message: Ivan Dormain: "Re: Creating Database file w/o Access or SQL"
- In reply to: Kevin Yu [MSFT]: "RE: Sufficient reason to de-normalize a field?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 15 Jun 2004 10:08:33 -0500
Great solution Kevin. Thank you very much.
"Kevin Yu [MSFT]" <v-kevy@online.microsoft.com> wrote in message
news:Ggec$trUEHA.2628@cpmsftngxa10.phx.gbl...
> Hi Earl,
>
> First of all, I would like to confirm my understanding of your issue. From
> your description, I understand that you need to know how to design the
> database structure without redundant data in a senario that payee is
> automatically added into database. If there is any misunderstanding,
please
> feel free to let me know.
>
> Based on my experience, you can also keep your database from redundant
data
> in this case. When adding payee to the database table, we can first check
> for existence in the subordinate table to see if this name has been added.
> If it hasn't been added, add it. The insert procedure returns the ID for
> the payee. Then we use this ID to update the payee's ID in the main table
> and insert the payment transaction into database.
>
> HTH. If anything is unclear, please feel free to reply to the post.
>
> Kevin Yu
> =======
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
>
- Next message: Paul Clement: "Re: Insert Picture from Access"
- Previous message: Ivan Dormain: "Re: Creating Database file w/o Access or SQL"
- In reply to: Kevin Yu [MSFT]: "RE: Sufficient reason to de-normalize a field?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|