Hi!

I forget about General fields so far because they are quite bad thing in VFP and quite not reliable. If you have ability, get rid of then as sson as possible. If you cannot... well, see below.

VFP general field mapped to SQL Server 'image' field type. In views you also can map image field at SQL Server to memo field in VFP.

If you consider to store documents in the image field on the SQL Server as files, following articles might be useful for you:

Thread#427023 Message#427217

HTH.

>Hey folks,
>
>I have an application that makes extensive use of General fields and in-place editing of Word documents stored in those fields. There is also a lot of document assembly using multiple General fields and a Word.Application object.
>
>It was a nightmare to work out the logistics on the first go-round, now I'm faced with another challenge: Migrating the whole ball of wax to SQL Server 2000.
>
>Any advice on how to re-architect this part of the app?