Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread dbisam.lck on my desktop, why ?
Wed, Aug 8 2012 1:03 PMPermanent Link

John Taylor

Using dbisam 4 (not client server) why would I have the lock file showing on
my desktop ?

I'm not doing it intentionally , of course.

Thanks
JT
Wed, Aug 8 2012 4:48 PMPermanent Link

Malcolm Taylor

John Taylor wrote:

> Using dbisam 4 (not client server) why would I have the lock file
> showing on my desktop ?
>
> I'm not doing it intentionally , of course.
>
> Thanks
> JT

Because you created a table/query result (probably temporary) there.
If you make sure you specify a folder for temp tables/query results,
the lock files will be in that folder.
Wed, Aug 8 2012 7:54 PMPermanent Link

John Taylor

As in dbisamsession.privatedir ?

JT

"Malcolm" <malcolm@spam.will.bounce> wrote in message
news:27E37794-417A-431F-948C-9A02D182B83C@news.elevatesoft.com...
> John Taylor wrote:
>
>> Using dbisam 4 (not client server) why would I have the lock file
>> showing on my desktop ?
>>
>> I'm not doing it intentionally , of course.
>>
>> Thanks
>> JT
>
> Because you created a table/query result (probably temporary) there.
> If you make sure you specify a folder for temp tables/query results,
> the lock files will be in that folder.
Thu, Aug 9 2012 6:54 AMPermanent Link

Malcolm Taylor

Hi John

It is so long since I actually used dbisam that I searched this group
for the 'correct' answer.  Surprised

I quote the following extract (one of several):
---------------
<snip>
The LCK files will turn up in any directory/folder that DBISAM is
accessing data files in. If they appear to be randomly infesting your
disk then I would guess that you are using canned queries but are not
controlling the location of Session.PrivateDir thus causing it to
default to whatever the OS regards as the 'current' directory at app
startup.
<snip>
Place all data files in one location and the LCK file (there will only
be one) will be in that location too.
<snip>
---------------
Thu, Aug 9 2012 8:34 AMPermanent Link

John Taylor

I did find one instance where I forgot to set the privatedir of the
session, I'm sure this is the culprit

JT

"Malcolm" <malcolm@spam.will.bounce> wrote in message
news:5CE701E7-AE9E-4EB4-BA4F-3D75AC530A11@news.elevatesoft.com...
> Hi John
>
> It is so long since I actually used dbisam that I searched this group
> for the 'correct' answer.  Surprised
>
> I quote the following extract (one of several):
> ---------------
> <snip>
> The LCK files will turn up in any directory/folder that DBISAM is
> accessing data files in. If they appear to be randomly infesting your
> disk then I would guess that you are using canned queries but are not
> controlling the location of Session.PrivateDir thus causing it to
> default to whatever the OS regards as the 'current' directory at app
> startup.
> <snip>
> Place all data files in one location and the LCK file (there will only
> be one) will be in that location too.
> <snip>
> ---------------
>
Image