I've got no idea.

For me it's mostly a matter of principle, the reasoning being that SP's come for a reason, and while they frequently introduce new bugs, they usually do away with most of the old ones.

Just as an example, I used to have C00005 (never mind the number of zeros) fatal errors frequently but have -knock wood- not had one for well over a year.

This may be a coincidence or have been caused any number of other updates - the fact is, it's now pretty stable.

I hesitate to ask, but you are sure you've got all your multi-user stuff set up correctly?

Are you are doing asynchonous fetching?

Do you know if the message is about the file that you are selecting from?


>Not much reason, we just never did. Do you think it would be better with SP2?
>
>>I'm not claiming any knowledge here, but are there any particular reasons why you have not applied SP2 to VFP?
>>
>>
>>>Hi everybody,
>>>
>>>Quite often we're getting this error just by running simple select statements (sometimes using CursorAdapter.CursorFill method). What could be a reason and how can we avoid / fix this problem?
>>>
>>>Thanks a lot in advance.