>>Go to http://msdn.microsoft.com ... click the Support button in the top banner...one of the options you'll then see with be to report a problem.
>>
>>>I found a bug in the new ODBC driver. How do I report to MicroSoft? Thanks.
>
>You might want to tell us as well <g>
>
>
>Wayne

Hi Wayne,
Sorry about that. Not really new. Supposedly fixed (but listed under C++, naturally). Also, have not ruled out one possiblity of miscoding on my part.


That having been said, the error went something like this:

I am connecting from Visual FoxPro 5.0 into a Remote Visual FoxPro 5.0 database. I get the following message

ODBC Error Message: "Connectivity error: [Microsoft][ODBC Driver Manager] Invalid cursor state"

ODBC SQL state: "24000"

The error number from the ODBC data source: 0


I found article Q154683 in the MS knowledge base. I think this means that the 24000 SQL state error 0 can be caused by a bug in the VFPODBC driver that was fixed (but maybe not). If data is small, no error. So just used nodata when opening the cursor. This seems to work so far.


Possible miscoding:
Originally opened the remote file using the DE at form load. Had to change it to use files in a different location, so opened the files manually. The cursor settings still said nodata, but I did not open the cursor using this option. This may have caused the problem, but I have not had a chance to test yet.

As the remote file got larger and larger, the error occured more and more reliably. As soon as I included the nodata option, I no longer had the problem.

Daniel