Desiree
|
| Posted: 02/27/2002, 12:23 PM |
|
Let me see if I understand the relationship thing with code charge. It is pointless to create relationships in access because in a sense you have to do that in code charge by passing the parameter. So If on the initial assessment page I want it to populated some of the same fields from the create risk table I would have to pass the parameter through to the page? If so which page does the parameter go on and what should the other boxes contain? Can someone try to explain this to me? Thanks.
|
|
|
 |
Tom
|
| Posted: 02/28/2002, 10:51 AM |
|
I always create the relationships in access (but I deal more with Oracle). The relationships keep the integrity of your database intact and (I'm not positive about access), it creates indices to make the queries go faster. My recommendation is to always keep the relationships..
You second question to me is that you want to identify the Primary Key for each table and use the PK as a foreign key to look up the data in the child table. As long as I have had my database 'correct' this has not been an issue.
Good luck
|
|
|
|
|
