![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 4 of 4 total |
![]() |
Wed, Jul 11 2007 3:24 PM | Permanent Link |
Michael Fullerton | I had a DBISAM table that was encypted. After converting it to EDB
when I try to open it in EDB I get a #100 error. Why would that be? |
Wed, Jul 11 2007 8:22 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Michael,
<< I had a DBISAM table that was encypted. After converting it to EDB when I try to open it in EDB I get a #100 error. Why would that be? >> What is the actual error message ? -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Jul 12 2007 1:37 AM | Permanent Link |
Michael Fullerton | On Wed, 11 Jul 2007 20:22:57 -0500, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote: >Michael, > ><< I had a DBISAM table that was encypted. After converting it to EDB when I >try to open it in EDB I get a #100 error. Why would that be? >> > >What is the actual error message ? ElevateDB Error #100 There is an error in the metadata for the table X (Signature, password or character set (ANSI/Unicode) mismatch) |
Thu, Jul 12 2007 4:39 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Michael,
<< ElevateDB Error #100 There is an error in the metadata for the table X (Signature, password or character set (ANSI/Unicode) mismatch) >> Did you actually perform the migration using the EDB Manager ? If so, then if you use a different encryption password in your application (TEDBEngine.EncryptionPassword), then you'll need to make sure that you do the same with the EDB Manager, which will require modification and re-compilation of the EDB Manager. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |