The Upsizing Wizard does not support GUID (UniqueIdentifier in MS SQL Server data type) out of the box because there's no such data type in VFP.
All the data type mapping is stored in the typemap.dbf which is a part of the Upsizing Wizard application.
You can add mapping for C to uniqueidentifier. You'll have to manually map GUID columns in the Wizard.
In VFP you should store GUID as 36 characters string value (without {}). That's the way you'll get uniqueidentifier from MS SQL Server using RV or SPT.


>have to transfer VFP-data to MS-SQL. Also have to change from incrementing primary keys to GUIDS. Wrote a routine, that adds columns to existing tables and put GUIDS in. Getting crazy because I don't know how to store GUIDS in Fox-tables. Using the following code to get the GUIDS (Source: http://www.berezniker.com):
>
< snip >
>Tried c(36)-fields (without {}), c(38)-fields (with {}) and varbinary q(16)-fields. The stupid SEDNA-wizard never changes to UniqueIdentifier as the target-field type. Can anybody tell me how to store the GUIDS in Fox-tables so the Upsizing-Wizard realizes to use a UniqueIdentifier-field?
>