Charles,

Not sure if this is the answer you were looking for, but I find DTS much easier to work with and much faster if I import delimited text files. Copying the fox table to DELIMITED WITH TAB and running DTS on the output is a lot faster than importing directly from the fox table. The issues you're having may be related to the ODBC or OLE driver. Direct text import seems to have far fewer issues. I can't remember if I've ever imported GUIDs with DTS, but I think I have with BULK INSERT, which I think is supposed to basically be the same.

Dan


>I always use 36 char guids ( formatted exactly like SQL Server UniqueIdentifiers ) as my surrogate keys in my VFP apps. When I upsize, using the upsizing wizard, I can only upsize as character(36) Then I must modify the tables in SQL Server to change the char(36) fields to uniqueidentifiers ( I realize I could probably fiddle the scripts on the vfp end to cast the values to binary(16) somehow, but that hardly seems a time saver.
>
>If I do my conversion with DTS, I am faced with pretty much the same thing.
>
>I realize that though these fields are correctly formatted and NOCPTRANS on the VFP side, they are not the same as SQL Server UniqueIDs
>
>Is there a trick to facilitating this upsizing (assuming I don't have my structures already in Visual UML etc ) to cast my guids as unique ids ( and keep my pk indexes )
>
>Suggestions appreciated
>
>TIA