Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Feature Request: Identify User locking records
Thu, Jun 14 2018 1:06 AMPermanent Link

Adam H.

Hi Tim,

Back in the days of using Paradox, if a user attempted to edit a record that was already in edit mode by another user, we used to get a message saying "Record is locked by user <name>"...

I was wondering if this would be something that could be implemented in a future release of Edisoft as an enhancement. (Even if it's only available for remote connections if it's easier to do for remote connections having user names already in the engine?) - as opposed to just saying record is locked by another user.

I have no idea of the complexity to implement this, but thought I'd ask.

Cheers

Adam.
Thu, Jun 14 2018 4:26 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Adam


Do you think it would be a good idea to post this on Edisoft forums?

Just a suggestion Smiley

Roy Lambert
Fri, Jun 15 2018 12:05 AMPermanent Link

Adam H.

That was silly of me... that shouldn't say Edisoft - that should say DBISAM. Smile

My question was in regards to DBISAM, sorry.
Mon, Jun 18 2018 2:01 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Adam,

<< Back in the days of using Paradox, if a user attempted to edit a record that was already in edit mode by another user, we used to get a message saying "Record is locked by user <name>"...

I was wondering if this would be something that could be implemented in a future release of Edisoft as an enhancement. (Even if it's only available for remote connections if it's easier to do for remote connections having user names already in the engine?) - as opposed to just saying record is locked by another user. >>

Unfortunately, no, this can't be implemented in DBISAM, given its current architecture.  DBISAM doesn't use a lock file where this type of information is "registered" for record locking, rather it uses straight OS byte-offset locking for locking, and there really isn't any way to capture information such as the user name of the user/session that currently has a given record lock.

Tim Young
Elevate Software
www.elevatesoft.com
Wed, Jun 20 2018 8:49 PMPermanent Link

Adam H.

Hi Tim,

OK - no problems. Thanks.
Thu, Sep 26 2019 8:46 AMPermanent Link

Frederic Schneider

Avatar

You could use a MailSlotTerminal to register users in the network who are locking records, like BDE or Paradox did...

Kind regards,
Frederic
Image