Tim

I presume that altering some of the Engines properties and then creating a database in an app will essentially render it invisible from EDBMan.

The properties I'm thinking of are:

CatalogExtension
CatalogName
ConfigName
EncryptionPassword
Signature
TableBlobExtension
TableExtension
TableIndexExtension

I know I can alter some of these in EDBMan but that would then render others invisible.

I'm also guessing that there's no equivalent to the .ini file that DBSys used to use and so no easy way of setting up alternative configurations.

Roy Lambert

Roy,

<< I presume that altering some of the Engines properties and then creating
a database in an app will essentially render it invisible from EDBMan.

The properties I'm thinking of are:

CatalogExtension
CatalogName
ConfigName
EncryptionPassword
Signature
TableBlobExtension
TableExtension
TableIndexExtension

I know I can alter some of these in EDBMan but that would then render
others invisible. >>

Make sure that the two match and there's no issue.  This is no different
than DBISAM.  DBISAM didn't let you modify the engine signature dynamically.
I might be able to do something about the EncryptionPassword, but I have to
think very carefully about how it should be stored.

<< I'm also guessing that there's no equivalent to the .ini file that DBSys
used to use and so no easy way of setting up alternative configurations. >>

Sure, it's stored in the current user's private application data folder:

C:\Documents and Settings\<UserName>\Local Settings\Application Data\Elevate
Software\ElevateDB Manager

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>Make sure that the two match and there's no issue. This is no different
>than DBISAM. DBISAM didn't let you modify the engine signature dynamically.

And who's telling me to forget the way DBISAM worked <vbg>

>I might be able to do something about the EncryptionPassword, but I have to
>think very carefully about how it should be stored.

Don't store it but allow it to be altered - same for the signature. If I want to have all my apps using the same password and signature its easy to change and recompile EDBMan, if I want to constantly vary them its just part of the hassle of that approach, or possibly I'd create several variants of EDBMan and use them. But it would be convenient to be able to type them in. I also appreciate that this would mean a block of work with EDBMan would be restricted to a specific set of conditions and I wouldn't be able to see all databases.

><< I'm also guessing that there's no equivalent to the .ini file that DBSys
>used to use and so no easy way of setting up alternative configurations. >>
>
>Sure, it's stored in the current user's private application data folder:
>
>C:\Documents and Settings\<UserName>\Local Settings\Application Data\Elevate
>Software\ElevateDB Manager

Ooooooo all M$ correct then. What's wrong with storing it with EDBMan eh?

Roy Lambert

Roy,

<< Don't store it but allow it to be altered - same for the signature. If I
want to have all my apps using the same password and signature its easy to
change and recompile EDBMan, if I want to constantly vary them its just part
of the hassle of that approach, or possibly I'd create several variants of
EDBMan and use them. But it would be convenient to be able to type them in.
I also appreciate that this would mean a block of work with EDBMan would be
restricted to a specific set of conditions and I wouldn't be able to see all
databases. >>

You mean type them in in the Edit Options dialog, but don't actually store
them in the .ini ?

<< Ooooooo all M$ correct then. What's wrong with storing it with EDBMan eh?
>>

Customers complained about that.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>You mean type them in in the Edit Options dialog, but don't actually store
>them in the .ini ?

Changed my mind about that, although if that or nothing I'd prefer that.

><< Ooooooo all M$ correct then. What's wrong with storing it with EDBMan eh?
> >>
>
>Customers complained about that.

Some days you just can't win

Roy Lambert