Interesting about the different drive. I wonder if there might be a flaky spot on the original HD?

Is this a new application or one that had been running fine before?

Below is a list of fixes in SP1 that have either "remote" or "column" in them:----- start list
Requery() on prepared remote view fails

Fatal exception on REQUERY() after tableupdate() to remote view with batchupdatecount = –1 and table buffering

Query processor fails to find column in SELECT list if it is enclosed in parenthesis, reports false "SQL: ORDER BY clause is invalid." error

SQLCOLUMNS() fails with complex names if at least one part of the name contains a space or other "illegal" character

Grid – Fatal exception setting value property in init of control in grid column

ALTER TABLE ... ALTER COLUMN to change character field to integer also changes value
---- end list

Does the HD have "write behind cache" disabled. If not, be sure it is.

Again, good luck


>Hi Jim
>
>It is version 9 (no service pack) under Win XP on laptop
>
>Furthermore and forthwith
>
>On my laptop I pretty much get the problem in the same places. When I tried placing the data on a different physical drive the problem shifted and was less frequent. I'm not sure what this is telling me. Perhaps it is a caching issue.
>
>I am in the process of trying it on another computer.
>
>Regards
>Geoff
>
>>What version of VFP?... On what workstation OS and Server OS?... Any wireless involved?
>>
>>good luck
>>
>>
>>>Just an update.
>>>
>>>The problem does not appear to berelated to a corrupt index either (unless it is becoming corrupt but continued updates in the session). I deleted and recreated all tags on the affected files to no avail.
>>>
>>>ho hum
>>>Geoff
>>>
>>>
>>>>Hi
>>>>
>>>>I am getting the above weird error when doing a TABLEUPDATE on a remote view. The remote database is a VFP database and the column refered to does not exist but it is not in the update list either.
>>>>
>>>>I seem to get error after a certain amount of records are processed.
>>>>
>>>>The strange thing is that if I repeat the TABLUPDATE command it works (appears to). Unfortunately, I also get a Window SERIOUS ERROR not long after. If I restart the process at the same position in the table where the error occurred it also works.
>>>>
>>>>Does anyone have I have any idea why it is occuring?
>>>>
>>>>Regards
>>>>Geoff Scott