Re: migrating data process with data type mismatch
- From: "Jeff Boyce" <nonsense@xxxxxxxxxxxx>
- Date: Tue, 7 Aug 2007 14:19:40 -0700
One approach might be to create queries against the old data that parses it
into the (normalized) pieces you need for the new data tables. A potential
wrinkle is if, as in your example, you have a old list of values that may
have duplication (there could be more than one person with the same name -
john smith?!). In that case, you'll have to add some kind of identifier
(for temporary use, during the transfer) to the old data so you can match
John Smith#1's other data to the correct John Smith in the new data.
Regards
Jeff Boyce
Microsoft Office/Access MVP
"Cheese_whiz" <Cheesewhiz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:98E8DD81-D204-407E-BB97-F0F29C6F0082@xxxxxxxxxxxxxxxx
Hi all,
I'm pretty green when it comes to migrating data and action queries and
such.....
I'm trying to get some data out of an old db into a new one. The old
tables
weren't normalized, though, so where my new table stores the fk from
another
table, the old db stores a text entry (like someone's name) and doesn't
have
the second table.
I'm thinking to get the data migrated, I need to rework the old db table
structure. Once it's normalized (like my new db), then maybe I could use
append queries to add the old records. I'm sure I'd have more questions
during the process, but is that the way you have to do it? If not, how do
you deal with a situation like that where the old records in a table
represent what amounts to a query in the new db?
Thanks for any assistance,
CW
.
- Prev by Date: Re: ignoring format/control codes exporting data from access to ex
- Next by Date: Re: Can I turn off the error generated tables
- Previous by thread: Re: Problem with exported Excel files
- Next by thread: Re: migrating data process with data type mismatch
- Index(es):
Relevant Pages
|