>I know this is .net but as an aside for people using vfp remote views it is worth noting that among the frailties of the VFP 9 view designer is a failure to see SQL varchar(max) fields as Memo and instead setting them by default to C(0). Attempting to save the view causes it to barf. You can view the code, change the dbsetprop type and all is well. Annoying nonetheless.

Oh, that *does* suck. When did VFP9 come out? Was it prior to 2005? You'd think though, that they would have known about this new VARCHAR(MAX) that was going to go into SQL 2005 and would have made the view designer compatible. Unless it was well before that was even thought about to be put into SQL 2005.

Oh well ... there *is* a workaround, so all is good. =0)

~~Bonnie





>
>>Michel,
>>
>>If you migrated to SQL 2000, text was the only datatype that would make sense to use for a VFP memo field, because of it's almost unlimited size (well, right around 2GB).
>>
>>Now, with SQL 2005, there's a new version of varchar, specified as VARCHAR(MAX) and that's what you should be using now. I don't know why they came up with this MAX concept. It stores the same amount of data as the old text data type, but text is going to be removed in the future. Straight out of BOL:
>>
>>ntext, text, and image data types will be removed in a future version of Microsoft SQL Server. Avoid using these data types in new development work, and plan to modify applications that currently use them. Use nvarchar(max), varchar(max), and varbinary(max) instead.
>>
>>~~Bonnie
>>
>>
>>>When I migrated two of my applications to SQL Server, a while ago, whatever was memo fields ended up to be within a Text type. However, a client of mine is wondering why we are not using VarChat for that? Anyone would like to comment on that?