Raul

>The only other thing i can think of is mixing the LargeFileSupport
>setting between different apps access the DB (but again this should not
>result in multiple lck files - just screw up locking on existing file).

It would have to be a very popular restaurant to achieve that

Roy Lambert

Roy Lambert wrote:

> 5. data vanishes

My thinking on this is that it would happen if one instance doesn't see
the locks of another, and that would make it overwrite the file changes
as it didn't know it was in use.

First step, make sure everything points at the same places. The main
database directory, and the Temporary directory to another location,
but shared across them all.

--

Matthew Jones

> However there are records that remains locked sometimes and when the windows program try to access these records it raises an exception (this program is not prepared to deal with that, but it should not have any record locked based on the context that we use it)

My second wild guess is whether this something like incident 3395
(http://www.elevatesoft.com/incident?action=viewrep&category=dbisam&release=4.29&incident=3395)
- however it would require your rest server to crash out of session
(i.e. not properly completing an edit or such).

Raul

Guys,

Many thanks for the replies.

Seems I made a mess with this lck file.

I started using DBISAM 10 years ago in an emergency situation, getting out of paradox that was causing troubles. But due my project deadline i could not have time to learn and understand how it worked.

At that point I had some trouble with lck and I just thought that it should have a temp folder for each one. Since than it remained like that working.

Since this application does not happen to have many locking situations for the way it is used, this problem never shown up.

But now with a lot of Tablets accessing the same database via my rest server, locking became important. It is common place they add items to a order and forget to close the order, then try to open in another place.

There are hundreds of places using my software this way.... scary thing..

So, if I understood correctly I need to make all of them point to the same .lck file. That could be stored on the database folder all together?

Eduardo


>So, if I understood correctly I need to make all of them point to the same .lck file. That could be stored on the database folder all together?

That's exactly what should happen. If you have the time I'd be fascinated to know how you managed to get multiple lock files.

Roy Lambert

On 11/29/2014 8:23 AM, Roy Lambert wrote:
>> So, if I understood correctly I need to make all of them point to the same .lck file. That could be stored on the database folder all together?
> That's exactly what should happen. If you have the time I'd be fascinated to know how you managed to get multiple lock files.
>

Me too.

AFAIK the only path one can change on per session basis is the
PrivateDir - this is not where the lck files will be stored but is just
for temp resultsets (i.e. numbered dbisam tables where intermediate
results are stored when you run non sensitive queries etc).

This path should be local to the user/application and you don't want to
point it to shared network location since you'd be transferring data
back and forth all the time making the app super slow.

LCK file should always be in the database folder and is shared by all
sessions. In fact i don't know of any way of redirecting them to
anywhere else. Only thing you can control is the lck extension itself so
make sure all your apps use same extension.

All of the above applies to fs only - in case of c/s the dbsrvr settings
are used anyways.

Eduardo :
- can you confirm what you're seeing in terms of lck files ?
- check your lock file extension settings between different apps (rest
server vs the windows apps)
- check the LargeFileSupport setting between rest server and windows apps

Raul

Thanks Raul,

I will check these things and report here soon.

Eventually my confusion is even bigger  but seems to see the right moment to clarify all these things and make it work.

Eduardo

Raul wrote:

On 11/29/2014 8:23 AM, Roy Lambert wrote:
>> So, if I understood correctly I need to make all of them point to the same .lck file. That could be stored on the database folder all together?
> That's exactly what should happen. If you have the time I'd be fascinated to know how you managed to get multiple lock files.
>

Me too.

AFAIK the only path one can change on per session basis is the
PrivateDir - this is not where the lck files will be stored but is just
for temp resultsets (i.e. numbered dbisam tables where intermediate
results are stored when you run non sensitive queries etc).

This path should be local to the user/application and you don't want to
point it to shared network location since you'd be transferring data
back and forth all the time making the app super slow.

LCK file should always be in the database folder and is shared by all
sessions. In fact i don't know of any way of redirecting them to
anywhere else. Only thing you can control is the lck extension itself so
make sure all your apps use same extension.

All of the above applies to fs only - in case of c/s the dbsrvr settings
are used anyways.

Eduardo :
- can you confirm what you're seeing in terms of lck files ?
- check your lock file extension settings between different apps (rest
server vs the windows apps)
- check the LargeFileSupport setting between rest server and windows apps

Raul