Hi

I have started a new project in D2006 with Dbisam V4.23.  Dbisam writes the
lock files and temporary files to the desktop at design time.  How can I
change this?

Thanks
Godfrey

Godfrey


Set the session PrivateDir - either drop a session onto your form and set it there or use the default session and set in code by Session.PrivateDir := 'C:\whatever';


Roy Lambert

Godfrey,

I can't remember if this behavior was fixed:
if the shortcut to your app on your desktop doesn't have a "start in"
directory set, then sometimes the temp files/LCK file appeared on the
desktop. I know for a while the behavior was like that, but like I said,
it may have been fixed.

Regards,

Jason Lee


Godfrey wrote:
> Hi
>
> I have started a new project in D2006 with Dbisam V4.23.  Dbisam writes the
> lock files and temporary files to the desktop at design time.  How can I
> change this?
>
> Thanks
> Godfrey
>
>

D7 - Dbisam 4.23


Hi

Is it possible to define that the temporary files are created in memory and
not in the disk?

Thanks

Gabriel

>
> I have started a new project in D2006 with Dbisam V4.23.  Dbisam writes
> the lock files and temporary files to the desktop at design time.  How can
> I change this?
>
> Thanks
> Godfrey
>

Gabriel,

<< Is it possible to define that the temporary files are created in memory
and not in the disk? >>

Not currently, however version 5 will have this capability.

--
Tim Young
Elevate Software
www.elevatesoft.com

I was using 3.14 and finally upgraded to 4.24 and now everyone is getting a dbisam.lck
file put on their desktop everytime the application is ran.  What is this for and why is this
happening?  Just feels like dbisam.lck file is going to be an anoyance.  Is there a way to stop this.


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Gabriel,

<< Is it possible to define that the temporary files are created in memory
and not in the disk? >>

Not currently, however version 5 will have this capability.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mark,

<< I was using 3.14 and finally upgraded to 4.24 and now everyone is getting
a dbisam.lck file put on their desktop everytime the application is ran.
What is this for and why is this happening?  Just feels like dbisam.lck file
is going to be an anoyance.  Is there a way to stop this. >>

Per email:

The .lck files are explained here in the manual:

http://www.elevatesoft.com/dbisam4d5_dbisam_architecture.htm

under the section "Databases and Directories".

<< A lot of our customers are now calling complaining that dbisam.lck files
is constantly being created on their desktop every time they click on short
cut for our program.  They say the delete the file but it just re-appears.
This did not happen with 3.14 version.  Why the desktop?  Why not the same
location as data files? >>

See this thread for more information:

http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=5&msg=49563&page=1#msg49563

If that is not the cause, then the second most likely explanation is that
you are using a TDBISAMDatabase component with a blank Directory property
(which will then use the current working directory) or a TDBISAMTable or
TDBISAMQuery component with a blank Directory property.  In such a case, the
..lck file will be created in the current working directory.  You should
never set activate a TDBISAMDatabase, TDBISAMTable, or TDBISAMQuery
component with these properties blank because using the current working
directory is not reliable.  A simple file open dialog can change the current
working directory for an application.

--
Tim Young
Elevate Software
www.elevatesoft.com

Is it on the desktop or just in a folder where the tables are located?

Jon

Mark Roach wrote:
> I was using 3.14 and finally upgraded to 4.24 and now everyone is getting a dbisam.lck
> file put on their desktop everytime the application is ran.  What is this for and why is this
> happening?  Just feels like dbisam.lck file is going to be an anoyance.  Is there a way to stop this.
>
>
> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:
>
> Gabriel,
>
> << Is it possible to define that the temporary files are created in memory
> and not in the disk? >>
>
> Not currently, however version 5 will have this capability.
>

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:027AFC29-929F-49C6-B4B4-20BB47A848DF@news.elevatesoft.com...
>
> If that is not the cause, then the second most likely explanation is that
> you are using a TDBISAMDatabase component with a blank Directory property
> (which will then use the current working directory) or a TDBISAMTable or
> TDBISAMQuery component with a blank Directory property.  In such a case,
> the
> .lck file will be created in the current working directory.  You should
> never set activate a TDBISAMDatabase, TDBISAMTable, or TDBISAMQuery
> component with these properties blank because using the current working
> directory is not reliable.  A simple file open dialog can change the
> current
> working directory for an application.
>

Tim, now I'm really confused. Why should I do anything about the database
directory if I'm using Client Server?

Could you please post a summary of what properties need to be set for an
application that can be switched from file server to C/S, depending on
location? I'm of course not asking for all the obvious stuff. Just a
description of properties that overlap, or serve multiple functions. For
example, if I understand your posting, the database directory, table and
query directory properties should ALWAYS be set. Why?

I'm confused.

Robert

If you have a shortcut to your app's .EXE on the user desktops, is the
"Start in" property set for the shortcut? If not, you may get a .lck
file on the desktop.

Mark Roach wrote:
> I was using 3.14 and finally upgraded to 4.24 and now everyone is getting a dbisam.lck
> file put on their desktop everytime the application is ran.  What is this for and why is this
> happening?  Just feels like dbisam.lck file is going to be an anoyance.  Is there a way to stop this.