Michael,

Thank you for jump in. I have a table on the SQL Server called specimen with these fields: nidspecimen(surogate primary key), cspecimenid (my 'real' key), mnote (text filed causing trouble). In VFP, a remote view vspeciman is based on the specimen table.

When I do some thing in VFP, I can see exactly what SQL Command are sent to the server by using SQL Server Enterprise Manager, selecting menu Server-Current activities and right click on the connection to view detail.

In the VFP command window:
use vspecimen no data
insert into vspecimen(nidspecimen, cspecimenid, mnote);
values(14800, 'testmemo', 'this is memo contents')
=tableupdate()

Then the SQL Server goes crazy for a few minutes, and the record is inserted.
From the server current activities I found out this:

insert into specimen(nidspecimen, cspecimenid, mnote)
values(14800, 'testmemo ', '#odbc#chenna2')
select TEXTPTR(mnote) from specimen
where mnote like '#odbc#chenna2'

my SQL server user name is chennan and my workstation is also called chennan.

I also tried these:
1 - inserting a record without memo contents through vspecimen;
2 - using SPT to insert a record with memo contents;
3 - updating a record with memo contents throuth vspecimen;
The SQL Command they send to the server look normal.


>Scott,
>
>I jumping into this thread late but I kinda interested in what's going on.
>
>Would you mind reposting the VFP code that is in question along with the output from SQLTrace (6.5) or SQL Profiler (7.0). This will tell us exactly what SQL Server is receiving from VFP and ODBC.
>
>-Mike