Hi,

The edbmanager of the addtools build 14 reports an error when you try to open the preferences.
So I tried solve this error myself by recompiling the manager. But it doesn't compile. I use the Source elevatedb of build 14 in D2007.

It reports something about EDB_BEGINBLOCK_KEYWORDS which were in edbconsts in Build 13 but now there gone.

Also, if I want the edbmngr.ini file to be located in de same path as exe. Do I have to recompile the manager with a change in getinifilename function, or is there another way to do this?

Kick,

> The edbmanager of the addtools build 14 reports an error when you try to open the preferences.

Same here:

---------------------------
ElevateDB Manager
---------------------------
Error reading SampleSyntaxMemo.StatementSeparator: Property
StatementSeparator does not exist.
---------------------------
OK
---------------------------

Just let Tim fix the bug.

Uli

Kick,

> Also, if I want the edbmngr.ini file to be located in de same path as exe. Do I have to recompile the manager with a change in getinifilename function, or is there another way to do this?

I don't know if that's a good idea. You would have to change and
recompile the exe each time a new build is released.

What's the problem with the location of the ini-file?

Uli

Uli

>What's the problem with the location of the ini-file?

Finding it

I use XYplorer and have it on a right click menu so 1 right click, 1 slide and 1 left click, but before that

C:\Documents and Settings\Roy Lambert\AppData\Local\Elevate Software\ElevateDB Manager\

is pretty deep.

The Microsoft people who come up with things like this should be inverted into a large pile of the end product of the digestive process. Preferably dogs because its smellier.

Roy Lambert

Roy,

> Finding it

Good point.

I use a custom application that stores all kinds of links together with
user-friendly names.

<< The Microsoft people who come up with things like this should be
inverted into a large pile of the end product of the digestive process.
Preferably dogs because its smellier. >>

I second that!

Uli

Uli Becker wrote:
<I don't know if that's a good idea. You would have to change and
recompile the exe each time a new build is released.
What's the problem with the location of the ini-file?>

Not only is the location very hard to find sometimes. But I seem to be unable to write to these locations on some systems. Although I am a domain administrator on a server, starting the edbmngr it's saying "cannot create directory" followed by a crash of the edbmngr. I suspect it's due to rights on this appdata folder. On my Win7 machine I cannot seem to open this path at all although I am logged in as a user with administrator rights, seems some kind of setting because some folders have a special folder icon with a lock on it (probably something with UAC). Even my own user folder is locked.

Besides that, I think it's way better to have a ini next to the exe. It's easier to find, and you can have multiple instances of the edbmngr with different settings! Also distributing settings is also easier because you don't have to query the appdata folder (which is different on may OS versions).

To conclude: what's wrong with a ini next to exe?

Kick,

I use Win7 and XP and never had problems accessing the file or folder.

> To conclude: what's wrong with a ini next to exe?

Nothing. It's a good idea indeed if you want to use multiple
instances of edbmngr!.

Tim has to say, what he can do.

Uli

Kick


The problem with an ini next to the exe is where the exe is. Microsoft in their infinite wisdom have decreed that its a no no for a program to write to a folder in Program Files. Probably why for any "interesting" program I install outside of Program Files.

Roy Lambert

<I use Win7 and XP and never had problems accessing the file or folder.>

found the ini under win7, turns out that the "Documents and settings" folder is actualy a shortcut to the new "users" folder, and for some reason this shortcut is unable to open (even for administrator). In the users folder its the samen with "Application Data" which is a shortcut for AppData.

Roy Lambert wrote:

<<The problem with an ini next to the exe is where the exe is. Microsoft in their infinite wisdom have decreed that its a no no for a program to write to a folder in Program Files. Probably why for any "interesting" program I install outside of Program Files>>

Oke, thats clear. Putting it next to the exe is not an option for the standard edbmanager. Could you make the code for the edbManager compilable again in build14 (see my first post) so I can make my own adjustments?

Kick