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.

Adam


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

Just a suggestion

Roy Lambert

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

My question was in regards to DBISAM, sorry.

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

Hi Tim,

OK - no problems. Thanks.

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

Kind regards,
Frederic