> Kevin,
>Use Image type that maps to general in VFP. It can store any type of file as binary.
>Binary and varbinary has limitations in that they shouldn't exceed 8KB and for binary every row should have the same fixed length.
>Cetin
>
>Cetin,
>
>Thanks for the input. Would using a memo field in the VFP cursor cause any problems versus using a general field?
>
>kevin

Memo would have problems if you don't care of data is 'binary' and code page conversions should be avoided. General fields are in fact memo fields. You could anytime save a file stored in general or memo field to disk or the reverse. General fields are of course slightly different in fpt at least in their header bytes.
Inage datatype maps to general in VFP and varchar, nvarchar to memo. If you'd go memo way than use varchar. You'd decide in which to store on where would you store it if used pure VFP. Image directly stores binary data where text stores nonunicode data that's in code page of the server. Since there are tricks to write general field content to a file I think I'd go with Image datatype.
Cetin