Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread lck file does not exist
Tue, Oct 27 2009 7:35 AMPermanent Link

"Al Vas"
H again,
Thanks for previous responses.  Just continuing on with my conversion
testing.  I have made it to a stage of compiling however when it gets to the
point of opening the TDBISAMDatabase it displays an error as follows:

Engine Error @11010 Table or backup file 'D:\.....\dbisam.lck' does not
exist.

In the folder I cannot see any file named dbisam.lck, however it is there
(must be hidden) as when I try and create a file by that name it tells me
that it is there (how cn you make this visible).  I then changed the
TDBISAMEngine to dbiam1.lck and received the same error.

Why would this be?  I cant see anythng in the manual.

Thanks

Alex

Tue, Oct 27 2009 8:29 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Al


Are you setting the PrivateDir property, and does your app have permission to write to the directory you find the .lck file in?

To make hidden files visible in Explorer its Tools | Folder Options | View | Hidden files and folders and check (blob?) Show hidden files and folders

Roy Lambert [Team Elevate]


Tue, Oct 27 2009 9:57 AMPermanent Link

"Al Vas"
Hi Roy,

Yes the PrivateDir is assigned to user's temp folder at run time in the
OnCreate event of the data module.  I tried hard-coding the PriateDir to
another path and it worked.  Bit weird.  Would have thought the temp folder
would be writeable (but it is the dreaded Vista) .  Will have to investigate
a bit more. Guess now with this introduced lock file there are client-side
PC settings we now need to address which wouldnt have been a concern before.

Is there a setting to not make the .lck file hidden?  I think it would be
less confusing for support ect to be able to see this file.

Thanks

Alex

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:1A6C75E1-64A4-47F1-BE07-51F0E0056435@news.elevatesoft.com...
> Al
>
>
> Are you setting the PrivateDir property, and does your app have permission
> to write to the directory you find the .lck file in?
>
> To make hidden files visible in Explorer its Tools | Folder Options | View
> | Hidden files and folders and check (blob?) Show hidden files and folders
>
> Roy Lambert [Team Elevate]
>
>
>
Tue, Oct 27 2009 10:09 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Al


There's nothing I know of in DBISAM, but there's nothing to stop you tweaking the attributes yourself (check out FileSetAttr
), or simply set Explorer's options which is what I do.

Roy Lambert [Team Elevate]
Tue, Oct 27 2009 8:18 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alex,

Which folder was giving you the error message ?  Is it actually the user's
temp folder, or some other folder ?

<< Yes the PrivateDir is assigned to user's temp folder at run time in the
OnCreate event of the data module.  I tried hard-coding the PriateDir to
another path and it worked.  Bit weird.  Would have thought the temp folder
would be writeable (but it is the dreaded Vista) .  Will have to investigate
a bit more. Guess now with this introduced lock file there are client-side
PC settings we now need to address which wouldnt have been a concern before.
>>

Not really - if DBISAM can't write to the dbisam.lck file, then it won't be
able to write to any table files in the same location.  Same goes for
reading, etc.

<< Is there a setting to not make the .lck file hidden? >>

No.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Oct 28 2009 1:40 AMPermanent Link

"Al Vas"

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:3824CB36-1877-4E95-9A31-6DCB83B42F7F@news.elevatesoft.com...
> Alex,
>
> Which folder was giving you the error message ?  Is it actually the user's
> temp folder, or some other folder ?
>
>

Im presuming it was the user temp folder because once I changed this in code
of  to using a hard-coded location instead the error went away.

Thanks

Alex

Wed, Oct 28 2009 7:24 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alex,

<< Im presuming it was the user temp folder because once I changed this in
code of  to using a hard-coded location instead the error went away. >>

Yes, but the problem is that the user's temporary folder should *always* be
read/write for the curent user account, so something else is wrong.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Oct 28 2009 7:35 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

I wonder if the temp file directory is being set correctly


D:\.....\dbisam.lck

means the temp directory is on drive D?


Roy Lambert
Image