Hi Tim.

Congratulations with the finished v. 1.00 of EWB. It surely is a
wonderful product

Anyway I have a question about the DataSetManager in EWB.

When I add a DBISAM dataset there are no problems, but when I try to
add an EDB dataset I get Error #100 when I test the connection. There
seems to be an error with the encryption password, but the dataset in
question is not encrypted, and I get the same error whatever I put in
the LocalEncryptionPassword field.

Please help me on the right track here
(Sorry for my poor English)

Kind regards
TorB.

Tor,

> When I add a DBISAM dataset there are no problems, but when I try to add
> an EDB dataset I get Error #100 when I test the connection. There seems
> to be an error with the encryption password, but the dataset in question
> is not encrypted, and I get the same error whatever I put in the
> LocalEncryptionPassword field.

I don't know if that has been changed in the final release, but the
dataset manager of the last prerelease version supported only Unicode
databases.
Maybe that's still the case.

Uli

Tor,

<< When I add a DBISAM dataset there are no problems, but when I try to add
an EDB dataset I get Error #100 when I test the connection. There seems to
be an error with the encryption password, but the dataset in question is not
encrypted, and I get the same error whatever I put in the
LocalEncryptionPassword field. >>

Uli is correct - this is due to the fact that EWB only supports Unicode EDB
databases in the Dataset Manager right now.  I'm busy on a fix for this
right now that will enable EDB to operate in either mode within the same
application, and that will resolve this issue.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Sorry to put any pressure on you  When do you expect this enhancement will be in place to support ANSI tables.  Do you think it will be within weeks, or more than month? I need to do some planning on my part. In my case Unicode is not an option for me, well not this year anyway.

I still work with D7 as well, and would like my D7 and XE apps to access the same ANSI tables if possible. I also have have applications that access and import DBISAM data into EDB tables as part of daily routines. I am not sure if I should even be looking at any Unicode databases at the moment, or if that would effect my daily imports, or EDB catalog, or files in any way with having the need to access data from other application types, and is why I have been scared to move to Unicode because of this, which I also will need to research more, or maybe someone else can comment.

John Postnikoff



"Tim Young [Elevate Software]" wrote:

Tor,

<< When I add a DBISAM dataset there are no problems, but when I try to add
an EDB dataset I get Error #100 when I test the connection. There seems to
be an error with the encryption password, but the dataset in question is not
encrypted, and I get the same error whatever I put in the
LocalEncryptionPassword field. >>

Uli is correct - this is due to the fact that EWB only supports Unicode EDB
databases in the Dataset Manager right now.  I'm busy on a fix for this
right now that will enable EDB to operate in either mode within the same
application, and that will resolve this issue.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

John,

<< Sorry to put any pressure on you  When do you expect this enhancement
will be in place to support ANSI tables.  Do you think it will be within
weeks, or more than month? >>

Actually, I had to abort the effort last week due to design issues with
trying to mix the two in the same application.  So, the next step will be to
get the plugin database engine support done in the EWB IDE so that the
ANSI<--->Unicode issue can be isolated in separate engine DLLs for EDB.
I'm guessing that this will be done by end of February, at the latest.
Between now and then I'll be releasing an EDB version with better migration
facilities between ANSI and Unicode, and that should at least help with
development between the two under EWB.

<< I still work with D7 as well, and would like my D7 and XE apps to access
the same ANSI tables if possible. I also have have applications that access
and import DBISAM data into EDB tables as part of daily routines. I am not
sure if I should even be looking at any Unicode databases at the moment, or
if that would effect my daily imports, or EDB catalog, or files in any way
with having the need to access data from other application types, and is why
I have been scared to move to Unicode because of this, which I also will
need to research more, or maybe someone else can comment. >>

If you're already only using ANSI (US English) for everything, then moving
to Unicode is easy and simple because you're using the lower 256 Unicode
characters for everything, and that is effectively the same as the Windows
1252 ANSI character set used for ANSI strings under Windows (1252 is a
superset of the ISO-8859-1 character set).

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com