Servoy Forum

I have the following two methods on the same layout linked to: OnRecordEditStart

databaseManager.acquireLock(foundset, 0)

and OnRecordSave

databaseManager.releaseAllLocks()

This works well, between all clients, but it does'nt work well in combination with Servoy Developer. If I edit a record in Developer and I go thru a client to the same record, i'll get the message: Record is locked. So far so good! If I leave the record in the developer and go back to the client en try to have acces, it still give me the message: record is locked!
As I said: between all clients, it works good!
[/quote]

Nobody has this problem?

Other question: Is it possible to make from these 2 methods --> global methods?
So I can use them on every layout??

It has been identified as an issue in Servoy Developer, the good news is that you only need locking in Servoy Client. The client functionality in developer is meant for quick access to your data only. We recommend doing lock testing in client only for the time being.

It is certainly possible to create this in a global method, in fact this kind of things is exactly where global methods were meant for.

How? I tried several things, but I can't get it work!

Code: Select all

databaseManager.acquireLock(forms[currentcontroller.getName()].foundset,0)

Make sure you are careful when you drill down to a foundset inside a global method, it is quite easy to introduce memory leaks in your solution.

I'm sorry, but it doesn't work in my solution.
The little blue-lock is'nt visible when i click into a field.

That appears to be a 1.01 issue, I can't reproduce it on 1.1

This works well, between all clients, but it does'nt work well in combination with Servoy Developer. If I edit a record in Developer and I go thru a client to the same record, i'll get the message: Record is locked. So far so good! If I leave the record in the developer and go back to the client en try to have acces, it still give me the message: record is locked!
As I said: between all clients, it works good!

This is fixed in next release (after rc3)