I am a newbie to the product.  I recently downloaded 2.01 build 5 Eval.  I have fired up
the ElevateDB Server, and then the ElevateDB Manager to create a new database, etc...  I
have had my eye on ElevateDB for some time, so I know that the product is long standing
(including DBISAM), and Tim Young's commitment to the product over the years has been
pretty impressive.  However, I do find the ElevateDB Manager to be a little buggy - am I
mistaken?  From my initial playing around with this utility (first half hour), I have had
the following problems:

1.  For some reason, when trying to use the Default connection, "Session Name is missing"
error message pops up from time to time, it loses its Session name of "default".  This
also happens when I setup a new session - the session name property seems to "disappear"
from time to time so that when I try to connect, I get the error.  Then if I edit the
session and enter a name, click O.K., then try to connect, the name didn't save and I get
error again???

2.  The migrator .dll's have to manually be moved to the server folder in order to show up
in the picklist.  The BDE migrator appears O.K., but when the ADO migrator .dll is moved
to the server folder, I get Elevate DBError #202 An error occurred with the module
edbmigrateado (An error occurred with the module call OpenEDBModule (OS Error: The
operation completed successfully)).

3.  When performing a BDE migration, and the migration process begins, there is no status,
no nothing - just a screen that appears like it is frozen.  It is if you have to "hope for
the best".  If I click the mouse anywhere - the script aborts with an error message.  If
there is a datatype error, or anything - the migration simply aborts with no mention of
the table that caused the error, etc....  You have to go look at the folder through
Windows explorer to see what was done!

Am I missing something, or is it safe to say that the ElevateDB Manager isn't quite ready
for prime-time???  If I am mistaken, someone please set me straight ...

David B.

> 1.  For some reason, when trying to use the Default connection, "Session
> Name is missing"
> error message pops up from time to time, it loses its Session name of
> "default".  This
> also happens when I setup a new session - the session name property seems
> to "disappear"
> from time to time so that when I try to connect, I get the error.  Then if
> I edit the
> session and enter a name, click O.K., then try to connect, the name didn't
> save and I get
> error again???

can you download 2.01 Build 4 ? ( for not to have this problem )

David,

<< 1.  For some reason, when trying to use the Default connection, "Session
Name is missing" error message pops up from time to time, it loses its
Session name of "default".  This also happens when I setup a new session -
the session name property seems to "disappear" from time to time so that
when I try to connect, I get the error.  Then if I edit the session and
enter a name, click O.K., then try to connect, the name didn't save and I
get error again??? >>

This is a known issue that was introduced in B5.

<< 2.  The migrator .dll's have to manually be moved to the server folder in
order to show up in the picklist. >>

This is intentional.  During installation, we have no idea what
configuration path will be used by the developer, and the migrator DLLs must
be put in the configuration path for EDB to pick them up.

<< The BDE migrator appears O.K., but when the ADO migrator .dll is moved to
the server folder, I get Elevate DBError #202 An error occurred with the
module edbmigrateado (An error occurred with the module call OpenEDBModule
(OS Error: The operation completed successfully)). >>

This usually indicates an issue with loading the MDAC components, or a
mismatch between an ANSI migrator and a Unicode EDB Manager, or vice-versa.

<< 3.  When performing a BDE migration, and the migration process begins,
there is no status, no nothing - just a screen that appears like it is
frozen.  It is if you have to "hope for the best".  If I click the mouse
anywhere - the script aborts with an error message.  If there is a datatype
error, or anything - the migration simply aborts with no mention of
the table that caused the error, etc....  You have to go look at the folder
through Windows explorer to see what was done! >>

The progress and status message issue was introduced in B5, and is due to
the status and progress messages not getting processed in the main message
loop.  We switched to a message pump in the EDB Manager in order to allow
for threaded debugging, and it caused this issue.  This and the session
issue will be fixed shortly.

As for the "script" aborting - which "script" are you referring to ?  And as
far as error messages are concerned, you should see any error messages just
fine while doing the migration - the migration simply uses EDB DDL and DML
statements to do the migration.

--
Tim Young
Elevate Software
www.elevatesoft.com

1.  O.K. - so I guess I am sane after all.

2.  <<This usually indicates an issue with loading the MDAC components, or a
mismatch between an ANSI migrator and a Unicode EDB Manager, or vice-versa.>>

What should I look for?  What minimum version of MDAC?  I am running XP SP2 ...  I would
assume that I have fairly recent MDAC components ...  Also, just because the ADO migrator
.dll is in the folder and may have an issue, should it bring down the entire migration
module down to its knees?  Shouldn't you be able to select another migrator (that works),
rather than being prevented from even being able to select another one from the picklist
or even able to use the migrator at all? (Just a suggestion...)  As of now, you have to
manually remove the faulty migrator out of the folder to be able to use the migration
module again ...., which I just had to figure out.  I don't know, it just doesn't seem to
be all that intuitive ...

3.  << As for the "script" aborting - which "script" are you referring to ?  And as
far as error messages are concerned, you should see any error messages just
fine while doing the migration >>

If the BDE migration begins processing, and you click on the tree view (because you don't
know if you were just launched into a "processing black hole" and want to see if the PC is
not hung, you get the message "ElevateDB Error #1103 An invalid or unknown request was
sent to the server."  Your migration then terminates as well.  You then have to start all
over.  It would seem to make sense to not allow any clicking during a migration that would
jeopardize the migration itself, or to handle it with a message or something to inform the
user that a migration is in progress with a choice to terminate or something.

I realize that the ElevateDB Manager is simply a utility to use for manipulating
databases, etc...  I also can appreciate the technical feat underneath the GUI.  But is
just seems that casual use "unveils" some inconvenient and/or inconsistent behaviors.


... A Little Background

I have been using the Advantage Local Server v6.2 for our software product for the past
five years, even in multi-user context.  It has been stellar and rock-solid, and one of
the best software products I have used in 20 years.  Prior to that, I was using the
BDE/Paradox nightmare, and our software product support issues were primarily supporting
the data engine, and hardly the business logic part of the program.  My confidence is "off
the charts" with Advantage.  Not one single issue or corruption report in 5 years.  And no
- I have no affiliation with the company.

However, since some years back when Sybase took over, I didn't have interest in Advantage
for the future.  I am looking for a "solid" reason to leave Advantage behind - and need a
product to provide that same confidence level.  So I am comparing DBManager to something
like Advantage Architect utility, which like their data engine, has been nothing but rock
solid and intuitive as well.  I don't need to be convinced of feature set comparisons -
ElevateDB is full of features.  I just need "real life" usability, stability, and
scalability to take our product to the next level, with as little of data support issues
as possible.

This is where I am coming from ...

David B.

David,

<< What should I look for?  What minimum version of MDAC?  I am running XP
SP2 ...  I would
assume that I have fairly recent MDAC components ... >>

If you're running XP SP2, then you have an adequate version of the MDAC
components.  However, that doesn't mean that there isn't a possible issue
with loading them.  The EDB migrator simply uses the ADO components from
Delphi, so you should try to see if you can use something like the
TADOConnection component in a test application to see what the issue may be.
If you can use the TADOConnection component okay, then the issue is most
likely down to a Unicode/Ansi mismatch.  From which installation directory
did you copy the ADO migrator ?

<< Also, just because the ADO migrator dll is in the folder and may have an
issue, should it bring down the entire migration module down to its knees?
Shouldn't you be able to select another migrator (that works), rather than
being prevented from even being able to select another one from the picklist
or even able to use the migrator at all? (Just a suggestion...)  As of now,
you have to manually remove the faulty migrator out of the folder to be able
to use the migration module again ...., which I just had to figure out.  I
don't know, it just doesn't seem to be all that intuitive ... >>

I've never seen this issue, so I'm not sure of the effects.  I'll have to
try some tests to see what I can find out about the behavior that you're
seeing.

<< If the BDE migration begins processing, and you click on the tree view
(because you don't know if you were just launched into a "processing black
hole" and want to see if the PC is not hung, you get the message "ElevateDB
Error #1103 An invalid or unknown request was sent to the server."  >>

This is due to the same issue as the progress and will be fixed in the next
release.  It's due to the message pump allowing other messages to be
processed when it shouldn't be allowing this.

<< However, since some years back when Sybase took over, I didn't have
interest in Advantage for the future.  I am looking for a "solid" reason to
leave Advantage behind - and need a product to provide that same confidence
level.  So I am comparing DBManager to something like Advantage Architect
utility, which like their data engine, has been nothing but rock solid and
intuitive as well.  I don't need to be convinced of feature set
comparisons - ElevateDB is full of features.  I just need "real life"
usability, stability, and scalability to take our product to the next level,
with as little of data support issues as possible. >>

Just to clarify - the issues that you're seeing with the EDB Manager have
absolutely no bearing on your application at all, and are simply issues with
an application that is written to use EDB.  IOW, one (EDB Manager) is not a
reflection of the stability of the other (the engine).

I might also point out that EDB is still constantly being improved and
changed, and it is these changes that sometimes cause issues in the EDB
Manager.  If you look at our release schedule, I assure you that Advantage
does not maintain anywhere near the pace that you see with our releases and
builds.  It is a fact of life when you're talking about a product that is
not even two years old yet.  So, keep in mind that you're comparing a
20-year old product with a 1 1/2 year old product.  We have not yet gotten
to the point with EDB where we are allowed to slow down and take things a
bit more slowly and allows things to completely stabilize without
introducing more major changes.  For example, all of the issues that you're
seeing are related to quite a major change in the EDB Manager - the script
debugger.

--
Tim Young
Elevate Software
www.elevatesoft.com

David,

<< If you can use the TADOConnection component okay, then the issue is most
likely down to a Unicode/Ansi mismatch.  From which installation directory
did you copy the ADO migrator ? >>

Scratch that - using the Unicode migrator by accident will simply result in
a parameter error.

I just tried a migration with the ADO migrator from 2.01 B5, and it works
fine here for me.  So, I suspect that something is amiss with the MDAC
components, but I'm at a loss to tell you what it might be.

--
Tim Young
Elevate Software
www.elevatesoft.com