OasisUnknown
New Member
- Joined
- Oct 15, 2015
- Messages
- 46
Hello All,
I had some basic/intermediate questions on how you guys would deal with social security numbers. I am working with several systems that I am combining raw data into my access database.
I am trying to make this database as easy to maintain and update as humanly possible because when I am gone there will be no one to maintain or even update the database so it really needs to go the distance for a while to keep the people that I work for going for a while.
The problem that I am running into is with social security numbers. I am using them as the relational key for all of my tables in my database because they make the most sense.
But I have a few situations that I need to solve.
the SSN come from the raw data formatted three different ways.
1.123-45-6789 (formatted with dashes)
2.012345678 (formatted no dashes)
3.12345678 (formatted no dashes and leading zeros missing.)
for the database I would prefer for all the references to have all socials formatted this way.
2. 012345678 (formatted no dashes and preserved leading zeros).
I only have a few tables of source data in my database and a few tables to hold persistent data.
Each table should hold anywhere from 500 - 1500 records. I dont anticipate any more than that at any given time.
In my self pondering I was thinking about having the source data pulled into the database unchanged and then either use an update query on the data to remove dashes and add leading zeros but I dont really know how to go about this.
or I can make a select query of each table with SSN's on it and use a calculated field to manipulate the data.
I would think that using an update query to format the data on upload would probably be best because it makes the change one time and then it is persistant for the rest of the life of the table.
I just wanted to run it past you guys and see what you pro's would do.
I had some basic/intermediate questions on how you guys would deal with social security numbers. I am working with several systems that I am combining raw data into my access database.
I am trying to make this database as easy to maintain and update as humanly possible because when I am gone there will be no one to maintain or even update the database so it really needs to go the distance for a while to keep the people that I work for going for a while.
The problem that I am running into is with social security numbers. I am using them as the relational key for all of my tables in my database because they make the most sense.
But I have a few situations that I need to solve.
the SSN come from the raw data formatted three different ways.
1.123-45-6789 (formatted with dashes)
2.012345678 (formatted no dashes)
3.12345678 (formatted no dashes and leading zeros missing.)
for the database I would prefer for all the references to have all socials formatted this way.
2. 012345678 (formatted no dashes and preserved leading zeros).
I only have a few tables of source data in my database and a few tables to hold persistent data.
Each table should hold anywhere from 500 - 1500 records. I dont anticipate any more than that at any given time.
In my self pondering I was thinking about having the source data pulled into the database unchanged and then either use an update query on the data to remove dashes and add leading zeros but I dont really know how to go about this.
or I can make a select query of each table with SSN's on it and use a calculated field to manipulate the data.
I would think that using an update query to format the data on upload would probably be best because it makes the change one time and then it is persistant for the rest of the life of the table.
I just wanted to run it past you guys and see what you pro's would do.