CachedUpdates is FALSE and CommitOnPost is TRUE. Is there anything else that could be going on?
I can't imagine that the component was designed to work this way.
CachedUpdates=False
CommitOnPost=True;
* Put record in edit mode, make changes (or don't, doesn't matter), cancel, and the record...
Thanks for the help, Marco.
I am using an immediate lock but NOT cached updates. The documentation for DOA states that
lmLockImmediate When the user starts editing a record, it is locked and a check is performed to see if it has been changed. The lock remains until the user posts or cancels...
I notified you of this problem with version 3.3 of DOA. You stated that it would be fixed in the new release of DOA but this doesn't seem to be the case.
We are now using DOA 3.4.2 for Delphi 5 and have run into the following problems:
Scenario #1:
- User A puts a record in edit mode...
Okay I just checked the table again from SQL*Plus and it's only giving me one record. Looks like it's a user headspace problem (i.e. I'm an idiot) Sorry for the confusion. If I have anymore problems I'll let you know.
Thanks,
Eric Dye
Thanks for the reply, Marco. I know that the query will return more than one record. I'm doing a select * from the tblinfomemo table. Copy and pasting the query from my DOA Query component into SQL*Plus returns all of the rows fine. I'm at a loss here.
Thanks,
Eric Dye
I had this working in Delphi 2 w/BDE but I'm attempting to migrate the App to Delphi 5 using a combination of BDE and DOA.
I've got one table that has the following structure in Oracle:
TBLINFOMEMO
-------------------------
INFORMATION_ID CHAR(5)
DESCRIPTIONRAW LONG RAW
Whenever I...
I'm using DOA3.3 with Delphi5 and Oracle 8.0.4 and what I want is the following:
User1 pulls up a record and puts it in edit mode.
If User2 tries to pull up the same record they can, but when they try to edit the get the message 'Record is locked by another user.'
User1 makes changes and...