Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

When to store data using Tab Control

Status
Not open for further replies.

JSchumacher

Technical User
Jun 17, 2001
31
US
I am creating a form for setting up a new account. The form is a tab control with 4 tabs. Tab 1 collects the name of each customer on the account. Tab 2 collects address and phone information for each of those customers. Tab 3 collects information regarding each piece of collateral on the account. At any time a user can "Cancel" and not save any of the data. I have a number of tables to store all the data - all Normalized. I'm trying to determine at what point to write information to tables. As I add a new customer or piece of collateral, do I store that information then and just delete if the user "Cancels", or would it be preferable to gather the data until the final page of the tab control and then write it all at once? I've been looking up information on arrays to see if that is my best route, but I'm still not sure in which direction to move.

Any ideas would be appreciated!

Thanks,
Judie
 
One approach is to ensure that your underlying data schematic has referencial integrity 'turned on', and that you have the 'cascade delete' option set. That way, when you delete an account, all related associated tables will have their corresponding records removed. This can all be controlled from within the relationships view, available by right clicking from within the database window.
Check online help for more info.
Good luck Steve Lewy
Solutions Developer
steve@lewycomputing.com.au
(dont cut corners or you'll go round in circles)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top