Hi, I'm not actually including the msys* tables explicitly. However when the data migration tool does it's copyFKeys step for one of my application tables, that's when I get the error. Presumably the ODBC functions for getting FKey info map to reads of these tables. Not sure how to get around this as there are no options other than table selection in the migration tool.
"Gustav Brock" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi Erich > > > K, thanks for the tip. I have one other problem. The data migration > > reports a permission error trying to read the msysrelationships > > (presumably > > access' meta-data). I changed the ODBC config to use the actual "Admin" > > username, but I still get the error. > > Exclude MSys* tables from the migration. Some of these you can't read at > all and none of them are needed outside Access. > > /gustav > > >> I would export the Access/Jet table to a new Jet table without the GUID > >> field - then you could import that table. > >> > >> /gustav > >> > >> > I am trying to import some data from MS Access. I'm not able to use > >> the > >> > "Data Migration" function because it does not let me limit columns > >> and some > >> > of the Access column data types (i.e. GUID) are not supported in > >> Cache.
