Yep, I found that out during some testing with two instances of my program
running. I could never get the TABLEUPDATE to fail. So I copied the
SaveRecord procedure from the framework class, put it in my datahandler
application class, and then renamed it. So those instances I need to check for
>> sllOK = TABLEUPDATE(0,.T.)<<
This is forcing the update no matter what. The second parameter should be .F.
and I would expect it
to fail. From the Help file:
llForce: True - Overwrites any changes made to the table or cursor by another
user on a network. The
WHERE clause uses only key fields
Hi
The way to it is as I said.
One instance(I1) grabs the value let's say 27. The other instance(I2)
also grabs 27.
The instance I1 subtracts 1, Instance I2 adds 1.
Instance I1 is updating, it locks the record grabs what is on
disk using curvalue(), that's 27, so he adds 1.
The second instance
] On Behalf Of James Trogdon
Sent: Monday, October 27, 2008 09:19 AM
To: [EMAIL PROTECTED]
Subject: RE: View Resolution Conflict
The view is set to Key and modified fields and Update using SQL Update. The
changed data is based
on the value of an existing field. So first, you have to get the value,
hummer.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Trogdon
Sent: Monday, October 27, 2008 09:19 AM
To: [EMAIL PROTECTED]
Subject: RE: View Resolution Conflict
The view is set to Key and modified fields and Update using SQL Update. The
changed data is ba
Hi
What you do is to use the curval() function. You lock the
record, grab the current value, change it accordingly and save.
HTH, E.
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free ver
The view is set to Key and modified fields and Update using SQL Update. The
changed data is based on the value of an existing field. So first, you have to
get the value, add or subtract one from it and then save it. The problem I'm
seeing is if two people query the view at the same time and g
Hi James,
>>I'm using the VFP 9 framework Visual Promatrix which relies on the Last Save
>>method. I have run
into a situation where this doesn't work for me. In particular, the scenario
I'm dealing with is
Inventory On Hand. I'm using local views with the hope of moving to SQL in the
future
James
If you have control of the database schema maybe some form of
'soft-locking' approach would work, i.e. add a lock field and write into
it on the backend, and clear it when finished. Then nothing else can
work with that record until the lock field is cleared.
--
Alan Bourke
[EMAIL PROTEC
9 matches
Mail list logo
