EDBMan and the engine dropped onto a form pick up different config paths.


Roy Lambert

Roy,

<< EDBMan and the engine dropped onto a form pick up different config paths.
>>

I don't know what you mean - the EDB Manager can't be "dropped onto a form".
It's config path comes from the .INI file.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Sorry. To explain more fully.

If I open EDBMan the congig path it uses by default is C:\3rdParty\EDBMan\utils\edbmgr

If I drop an engine component on a form the config path it uses by default is C:\Documents and Settings\Roy Lambert\Desktop

And I've just realised why I had the lock file etc turn up on my desktop.

Roy Lambert

Roy,

<< If I open EDBMan the congig path it uses by default is
C:\3rdParty\EDBMan\utils\edbmgr

If I drop an engine component on a form the config path it uses by default
is C:\Documents and Settings\Roy Lambert\Desktop >>

It uses the current working directory, by default, so that is why you're
seeing this difference.  There really is no "ideal" directory choice, so the
current working directory is about as good as it gets.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

><< If I open EDBMan the congig path it uses by default is
>C:\3rdParty\EDBMan\utils\edbmgr
>
> If I drop an engine component on a form the config path it uses by default
>is C:\Documents and Settings\Roy Lambert\Desktop >>
>
>It uses the current working directory, by default, so that is why you're
>seeing this difference. There really is no "ideal" directory choice, so the
>current working directory is about as good as it gets.

I presume you're referring to the engine dropped on the form case. If so I don't know about others but I'd prefer to see it left blank and have to fill it in myself since the definition of "current working directory" seems to differ depending on OS/Application (eg D6 -> D2006).

I can just see myself at some point not realising that this has been helpfully set to totally the wrong place and going round and round for hours trying to find out what the problem is. And the reason I can see this happening is I've done similar things several times

Roy Lambert

Roy,

<< I can just see myself at some point not realising that this has been
helpfully set to totally the wrong place and going round and round for hours
trying to find out what the problem is. And the reason I can see this
happening is I've done similar things several times >>

Better for it to be wrong and issue an error than to have it left blank and
be using a completely different directory than you think on the target
machine and not issuing an error.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>Better for it to be wrong and issue an error than to have it left blank and
>be using a completely different directory than you think on the target
>machine and not issuing an error.

So why not have it blank and get it to issue an error as soon as set active at run time if there's no config path?

This would be annoying but safer.

Roy Lambert

Roy,

<< So why not have it blank and get it to issue an error as soon as set
active at run time if there's no config path?

This would be annoying but safer. >>

That's a good idea.  I'll see what I can do.

--
Tim Young
Elevate Software
www.elevatesoft.com