All:

I'm a long time DBISAM user, but now I working with ElevateDB C/S 1.05 Build
1 (with BDS 2006).  I've rebuilt the narrow (non-Unicode) version of
EDBManager with a custom encryption password (I set
Engine.EncryptionPassword in the TSessionObject.Open method just before
FSession.Connected:=True line in main.pas).  Running this custom version and
with the ConfigPath pointing to an empty folder, I can connect to the
session and login with the default credentials.  I create a few objects.  I
then verify that its encrypted by running the shipping EDBManager binary --  
I cannot make a connection -- error 100.  Good.

I then drop all the typical components on a form and set them up: engine,
session, database and a table.  I set Engine.ConfigPath to the same folder
used in the built EDBManager and of course the EncryptionPassword also to my
custom value.  Upon setting the session's Connected property to true, I get
error 100 (ElevateDB Error #100 There is an error in the metadata for the
object EDBConfig (Signature, password, or character set (ANSI/Unicode)
mismatch).  I know I have the right passwords, tried both the default and
custom credentials, and am not doing anything with Unicode.

If I did not use a custom encryption password and had the config file
created by the shipping version of EDBManager, all would be fine.

Another way to verify this problem is to start with an empty config folder
and start the engine and session components on a form with the default
credentials (not using EDBManager at all).  It works fine, creating a config
file that I can open with EDBManager.  But trying this same thing with the
same empty folder with a custom encryption password also yields the same
error 100.

Am I on the right track here or am I missing something?

I hope we can get support for the encryption password and engine signature
directly in the shipping EDBManager at some point.

Thanks much.




C

Carlton,

<< I then drop all the typical components on a form and set them up: engine,
session, database and a table.  I set Engine.ConfigPath to the same folder
used in the built EDBManager and of course the EncryptionPassword also to my
custom value.  Upon setting the session's Connected property to true, I get
error 100 (ElevateDB Error #100 There is an error in the metadata for the
object EDBConfig (Signature, password, or character set (ANSI/Unicode)
mismatch).  I know I have the right passwords, tried both the default and
custom credentials, and am not doing anything with Unicode.

If I did not use a custom encryption password and had the config file
created by the shipping version of EDBManager, all would be fine. >>

Something is not right, and most likely the ConfigPath is not correct at
some point in the process.

<< Another way to verify this problem is to start with an empty config
folder and start the engine and session components on a form with the
default credentials (not using EDBManager at all).  It works fine, creating
a config
file that I can open with EDBManager.  But trying this same thing with the
same empty folder with a custom encryption password also yields the same
error 100. >>

Are you activating any of the components at design-time during this process
?

--
Tim Young
Elevate Software
www.elevatesoft.com

I only test in design mode, leaving everything off and enabling the
components at runtime.  I assumed that if I could not get a connection at
design time, it would not work at runtime.

To move forward, I'm now just using the default encryption password.  But I
will want to change it before I ship this item.

I think I should at least be able to connect at design time to a database
with a custom encryption setup.  Or am I wrong here?  Thanks.





C





"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:211F0854-9F53-4AF8-AA0B-BC653D265ABA@news.elevatesoft.com...
> Carlton,
>
> << I then drop all the typical components on a form and set them up:
> engine, session, database and a table.  I set Engine.ConfigPath to the
> same folder used in the built EDBManager and of course the
> EncryptionPassword also to my custom value.  Upon setting the session's
> Connected property to true, I get error 100 (ElevateDB Error #100 There is
> an error in the metadata for the object EDBConfig (Signature, password, or
> character set (ANSI/Unicode)
> mismatch).  I know I have the right passwords, tried both the default and
> custom credentials, and am not doing anything with Unicode.
>
> If I did not use a custom encryption password and had the config file
> created by the shipping version of EDBManager, all would be fine. >>
>
> Something is not right, and most likely the ConfigPath is not correct at
> some point in the process.
>
> << Another way to verify this problem is to start with an empty config
> folder and start the engine and session components on a form with the
> default credentials (not using EDBManager at all).  It works fine,
> creating a config
> file that I can open with EDBManager.  But trying this same thing with the
> same empty folder with a custom encryption password also yields the same
> error 100. >>
>
> Are you activating any of the components at design-time during this
> process ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Carlton,

<< I only test in design mode, leaving everything off and enabling the
components at runtime.  I assumed that if I could not get a connection at
design time, it would not work at runtime. >>

Hmm, that configuration worked fine for me here.  It only became an issue
when I accidentally left the engine activated at design-time.

<< I think I should at least be able to connect at design time to a database
with a custom encryption setup.  Or am I wrong here? >>

Sure, EDB makes no distinction regarding this at design-time - it treats it
exactly the same internally as if you were connecting at runtime.

--
Tim Young
Elevate Software
www.elevatesoft.com