I am using D6 and DBISAM ver.4.25.
How should I specify the directory property when I have "only" a network path like
\\server\dTime ?
please, advice

"andrej" <andrej.bivic@abitrade.si> wrote in message
news:C94FA2C8-FA48-45AE-96BD-53A10ECCAFF4@news.elevatesoft.com...
>I am using D6 and DBISAM ver.4.25.
> How should I specify the directory property when I have "only" a network
> path like
> \\server\dTime ?
> please, advice
>

Just like that.

Robert

what if I leave it blank? And I run app from the same spot where tables are...
andrej

"Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote:


"andrej" <andrej.bivic@abitrade.si> wrote in message
news:C94FA2C8-FA48-45AE-96BD-53A10ECCAFF4@news.elevatesoft.com...
>I am using D6 and DBISAM ver.4.25.
> How should I specify the directory property when I have "only" a network
> path like
> \\server\dTime ?
> please, advice
>

Just like that.

Robert

"andrej" <andrej.bivic@abitrade.si> wrote in message
news:7FE05E32-A07C-461E-9DC5-7F67DAFBC8F9@news.elevatesoft.com...
> what if I leave it blank? And I run app from the same spot where tables
> are...

I don't know what happens if you leave it blank. Probably nothing good. Just
use ExtractFilePath(ParamStr(0)) to use the same directory as the EXE.

I think mixing the EXE with data tables is not a good idea, for a number of
reasons. But of course it depends on you app.

Robert

Thank you for your reply.
Can you be, please, more specific about not mixing exe and tables?

andrej

"Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote:


"andrej" <andrej.bivic@abitrade.si> wrote in message
news:7FE05E32-A07C-461E-9DC5-7F67DAFBC8F9@news.elevatesoft.com...
> what if I leave it blank? And I run app from the same spot where tables
> are...

I don't know what happens if you leave it blank. Probably nothing good. Just
use ExtractFilePath(ParamStr(0)) to use the same directory as the EXE.

I think mixing the EXE with data tables is not a good idea, for a number of
reasons. But of course it depends on you app.

Robert

andrej


I believe that if you leave the databasename blank the engine will use the current active directory as the path to the tables. This means that you're subject to the vagaries of Windows and its selection of which is the current active directory. If you open all the tables when you start the app, never close them and reopen during the running of the app you should be OK otherwise you may find that your app can't find the tables because the current active directory has moved.

Mixing the .exe with the tables is a matter of personal preference. Many (myself amongst them) prefer to keep the two separate but I know of no physical reason for the separation, and whilst I consider it good practice I have no idea why, or if I ever knew I've forgotten.

Roy Lambert [Team Elevate]

"andrej" <andrej.bivic@abitrade.si> wrote in message
news:F52C6EE7-416F-45D6-82F6-659A2806DBFF@news.elevatesoft.com...
> Thank you for your reply.
> Can you be, please, more specific about not mixing exe and tables?
>

Just a matter of security. Operators should be able to modify files in the
data folder, but you don't necessarily want them modifying executasble
files.

Just set some simple standard for your programs, such as making a subfolder
\TABLES under the folder where you have the executable, and that way you
keep them separate.

This also allows you to easily point your app to a different database (say a
test database vs a production database) without having to move the
executable. You can have a TABLES subfolder, a TEST subfolder, etc.

Of course, if you want to release software in strict compliance to M$
standards, you need to have a PhD in Windowsology, but that's another story.

Robert
> andrej
>
> "Robert" <ngsemail2005withoutthis@yahoo.com.ar> wrote:
>
>
> "andrej" <andrej.bivic@abitrade.si> wrote in message
> news:7FE05E32-A07C-461E-9DC5-7F67DAFBC8F9@news.elevatesoft.com...
>> what if I leave it blank? And I run app from the same spot where tables
>> are...
>
> I don't know what happens if you leave it blank. Probably nothing good.
> Just
> use ExtractFilePath(ParamStr(0)) to use the same directory as the EXE.
>
> I think mixing the EXE with data tables is not a good idea, for a number
> of
> reasons. But of course it depends on you app.
>
> Robert
>

Just make sure that if you keep them together, you don't put them under
Program Files in Vista.. I am pretty sure those directories get
virtualized and you can lose your changes to the data.

Sean

Roy Lambert wrote:

>
> Mixing the .exe with the tables is a matter of personal preference.
> Many (myself amongst them) prefer to keep the two separate but I know
> of no physical reason for the separation, and whilst I consider it
> good practice I have no idea why, or if I ever knew I've forgotten.
>
> Roy Lambert [Team Elevate]
>