>I'm constantly getting this message:
>
>"can't update the cursor"
>
>But isn't a cursor is a table, the part of the program that fires up this error tries to update a field on a record of a table by using the replace command
>
>This is form a multiuser application that haven't got this problem before.
>
>Thanks
After read most of reply and your further explan, I can suppose what you have
already done.
- Use Direct Cursor on Table
- Set MultiLock On
- Set Exculsive Off
- CursorSetProp(...) either 2,3,4,5 most likely is 3 or 5!
Then, what maybe left I suppose?
Form.BufferMode = 2
Set it on Form Designer, if you find you fail to open table, check "DataSession" property!
If after check those 2 properties but got right value!
You need to check whether any "Replace" execute at once
Before the user can do any Action, Because If 2 or more application modify the first Record information at once...
Only one of the application can update the cursor... ~_~
Besides, there is some observation that
EVEN for the fail Update cursor TableRever(), it still can update in other records!! This means forever fail to update, you need to release the form object and Re-create the Cursor again!
This bug seem fixed in VFP 6.0
In my point, I suggest you to check the field value before any replace statement!
e.g.
if myTable.myField <> cNextFieldValue
Replace myTable.myField With cNextFieldValue
Endif
because the replace statement claim you are editing the record if need not update, don't lock if possible!
Anyway, just a suggestion!
The weak wait for chance, The strong bid for chance,
The clever notch up chance, but The merciful give you chance.