Hi Jim

Unfortunately not. I'm am getting other errors now also.

The latest was a "trigger failed" error. This is even odder because the only trigger on the table in question is a delete trigger and the view has an UpdateType of 1.

Basically, I am getting errors about once every 1250 updates. I am using Transactions.

At the moment I am doing a conversion run. The update function is a core part of a new module and it kinda needs to be 100%. (not unusual). While I could write code to bypass the remote views it would not resolve the potential live problem.

Regards
Geoff Scott


>Hi Geoff,
>
>I have never seen this error either.
>
>But I have seen other weird errors with views (remote or local), in our case with TRANSACTIONS active.
>The workaround in this case was to put a =SYS(1104) before the BEGIN TRANSACTION.
>
>good luck
>
>
>>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