Hubert,

I don't have much help to offer, but under Sybase I've seen VFP cursors corrupt with blocks of Hex0 written randomly into the file, some time after the cursor was generated with a SQLExec() call. We've not been able to create a reproducible chunk of code that causes the error to send to MS and Sybase to track down the problem. If you are seeing it with other backends that would lead me to point the finger more at VFP.

One work around we've found is to reselect from the SQLExec cursor into another VFP cursor and use that one instead:

SQLExec( "select ..." )
select * ;
   from sqlresult ;
   into cursor ThisOneWontCorrupt ;
   ...

>I have a client/server application running under NT and three databases (SQL-Anywhere, Oracle 8, MSSQL).
>Starting the application requerys some remote views to the database. So far so good.
>Sometimes, when I close a form of my application, some data sets of several remote views change into Hex0. For that some objects loose the record source. I only work with the default data session, no private data sessions.