> > See if this help:
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B308215> >
> > > I have a SQL Server 2000 table and a Remote View set to this table which the end result is the following structure...
> > >
> > > Structure for table: C:\DOCUME~1\KBLUM\LOCALS~1\TEMP\E63W004H.TMP
> > > Number of data records: 3474
> > > Date of last update: / /
> > > Memo file block size: 64
> > > Code Page: 1252
> > > Field Field Name Type Width Dec Index Collate Nulls
> > > 1 CFR172101_IDKey Integer 4 No
> > > 2 SHIPPING_NAME Memo 4 Yes
> > > 3 SYMBOLS Character 8 Yes
> > > 4 HAZARD_CLASS Character 15 Yes
> > > 5 UN_NUMBER Character 10 Yes
> > > 6 PACKING_GROUP Character 5 Yes
> > > 7 LABEL Character 30 Yes
> > > 8 SPECIAL_PROVISION Character 90 Yes
> > > 9 PKGEXCEPTION Character 15 Yes
> > > 10 PKGNONBULK Character 15 Yes
> > > 11 PKGBULK Character 15 Yes
> > > 12 PASSENGER_AIR Character 15 Yes
> > > 13 CARGO_AIR Character 15 Yes
> > > 14 VESSEL Character 5 Yes
> > > 15 VESSELSP Character 10 Yes
> > > 16 REPORTABLE_QTY Numeric 11 4 Yes
> > > ** Total ** 270
> > >
> > > Whenever I attempt to add an EditBox with the ControlSource set to CFR172101.Shipping_Name I get an "Invalid Cursor State" error, and VFP crashes. It does not crash when doing a Modify Memo (using it in a grid).
> > >
> > > I have numerous other SQL Server tables that have Text fields which are converted to memo fields in VFP Remote Views and use them without a problem. It's just this one Remote View that has been a little !@*$ for a week now. I have tried recreating the SQL Server table along with the Remote View numerouse times.
> > >
> > > Anybody else have this problem before?
> > >
> > >
> > > KTB
>
> Nope, that's for using VFP ODBC driver, but thanks.
>
> KTB
FYI I resolved this problem by checking the Fetch Memo option in Query - Advanced Options which is the same as CURSORSETPROP("FetchMemo",.T.). While I understand what it does, I do not know why this does not need to be checked on my other views with SQL Sever Text/VFP Memo fields but this did fix the problem.
I also checked the Precompile SQL on Backend Server option. Anybody know why this should not be the default and exactly what this means?
KTB