I couldn't understand. c(16) nocptrans and varbinary(16) works very well (and similar data like encrypted passwords).
The purpose is automating I understand that and what I'm saying is also automation. ie:
In SQL server:
-Get data from VFP via DTS into a temp database (just structure really)
-Script the database
-Edit script for uniqueidentifier columns (and real database name)
-Run script
-Get data from VFP using VFP code.

What I did was shorter. I created a routine (sort of gendbc) that'd write the script for me (unfortuantely to keep the code easier at that time I hardcoded parts for my own databases). But in general it's a simple 'code genmerator'.
Cetin

>Yes, you can specify the transformation with DTS, but if you have a c(36) field on the VFPOLEDB side you do not have the option of picking uniqueid and if you pick binary you get a binary(1)
>
>It is true you can modify the script and I think that the c(36) can be cast there, but the purpose here is to automate that process and it is just faster to import the data as c(36) and then open the SQL Server table designer and just change the data type there.
>
>
>>BTW I don't know VFP's upsizing wizard but I think with SQL DTS you can specify datatype for SQL server side.
>>With VFP's upsizing wizard I remember "generate code". Take that code and change SQL server type to be uniqueidentifier (and possibly ROWGUIDCOL) and run with osql,isql or query analyzer (or even VFP).
>>Cetin