Actually, figured this out. The Access DB was setup for replication and the GUID field is part of the replication meta-data. Disabled replication and it went away.
"Erich Oliphant" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > 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. > > > > "Gustav Brock" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > Hi Erich > > > > 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. > > > I'm > > > now trying to import the data/table defs based on .csv data I exported > > > from > > > Access. According to the docs, I should be able to select an existing > > > table > > > or type a new table name at import time. Since these are new tables, I > > > need > > > to type the new table/class name. The "Please choose a table name" > combo > > > box, on the "Select Table Name" dialog is not allowing me to type in a > > > new > > > table/class name. > >
