[AccessD] Child records entered before parent

Um, John?  In bound forms, moving from the parent form to the subform
saves the parent record.  If there's no parent ID, it sounds like you
have a bigger problem.  I generally disable the child subform until the
parent form is complete.  Of course, you could also enforce referential
integrity between the two tables, which wouldn't allow you to save the
child record anyhow without a parent.  I know you know about all that,
so are you doing something exotic that you didn't explain?

Charlotte Foust


-----Original Message-----
From: John W. Colby [mailto:jwcolby at colbyconsulting.com] 
Sent: Friday, September 09, 2005 9:22 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Child records entered before parent


Regardless of the PK type of choice, allowing the user to enter child
records before the parent is valid can create a mess in your database.
Using bound forms, a subform will happily allow the user to enter a
child record when the parent form is on the new record.  What happens
then is that the child record is saved  but there is no valid parent ID
so the entered record is immediately "orphaned".

So how do you guys handle preventing the user from entering data in
child forms if the parent form is on the new record?

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com