You haven't actually stated your business rule, nor have you mentioned any need to preserve a history of addresses, but the correct structure from a db design point of view is likely to be that the table storing the owner of the addresses has a one-to-many relation with the address table. i.e. you store all address in one table and include an address-type column.
On Monday, May 14, 2012 10:14:04 AM UTC+1, Yogesh Kamat wrote: > > I am working on candidate employment tracking portal.. wherein the > requirement is to collect Permanent Address, Current Address. > > Situation is similiar to Shipping and Billing Address scenario... > > Also how should i separate the address details in 2 different tables and > link to main registration table using foreign key scenario. > > I have gone through the test examples.. but i am unable to visualize the > same for my project.... > > Also how to relate this with sqlform since i am planning for a form > wizard.. >
