Ok, I have some idea of how this is done; I'm looking for an example that will help me firm up my understanding.
Users of my application can export their data to tab delimited files. However, the sticking point is the previous application creates one tab delimited file per table. (Not the way I would have done it). So, what I'm wondering is how best to accomplish this.
I am using SQL CE 4.0 for the new DB backend. The previous DB version for the legacy product was Paradox 5. It spits the data out in a clean format since my new tables line up exactly with the old ones (KISS method). So, does anyone have one or more good examples of the best way to do this?
The file name convention on each file is:
Bg [TableName]_Firstname Lastname.TXT
(i.e. Bg Data_John Doe.TXT)
Obviously, I would want to check the imported files for any duplicates of the live data and remove them from the temporary table. So I'm thinking to check based on Date, Time, and measurement.
Users of my application can export their data to tab delimited files. However, the sticking point is the previous application creates one tab delimited file per table. (Not the way I would have done it). So, what I'm wondering is how best to accomplish this.
I am using SQL CE 4.0 for the new DB backend. The previous DB version for the legacy product was Paradox 5. It spits the data out in a clean format since my new tables line up exactly with the old ones (KISS method). So, does anyone have one or more good examples of the best way to do this?
The file name convention on each file is:
Bg [TableName]_Firstname Lastname.TXT
(i.e. Bg Data_John Doe.TXT)
Obviously, I would want to check the imported files for any duplicates of the live data and remove them from the temporary table. So I'm thinking to check based on Date, Time, and measurement.