Jan 20, 2010; 19:43
Frank Wilson
Database design
Living in a changing world also means that when creating new software soultions we need to look at what is needed in the world today. I have been developing databases for 25 years and have just started to develop a new software package for an Indian based NGO. So I got to thinking about the contact table and as to what segments of data do we need to keep to make it not only friendly but to have the necessary data on hand when needed.
More to the point, What format to follow when starting with the basic architecture, once we would ask the client what they needed, however with changing times, that question maybe best answered by others, as with the ever increasing demands of the Homeland Security department in the USA and other international instrumentilities, there is a need to supply requested information on demand and yet still not invade the privacy of the contact.
Example of changing times, is that that now when you ring a government office, the service person asks you to supply your name as it is written on your ID or Passport, then that is followed up by asking you to give your date of birth to confirm your identity. So is a Contact_ID field a thing of the past, is best to just have? First Name, Other names (As shown on your ID or Passport), Salute and if as prefix or suffix, sex, date of birth etc.
So what is the best practice and does anyone know the information required by Homeland security for those non-USA citizens flying to the USA?
See: http://www.cbp.gov/xp/cgov/travel/id_visa/esta/
Will welcome any input on this matter
Thanks in Advance
Pak Frank
--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/