Running WinXP SP2, D2007, EDB 1.06B1

I would like to migrate non-BDE databases which are defined under
Microsoft ODBC Administrator System Data Sources (SystemDSN) but cannot
seem to do so as I used to be able to with DBISAM's BDE Database
Transfer Utility. I have tried it since EDB first allowed for database
migration with no success.

As an example, I have a number of Advantage databases (v6, v7 and v8)
which I would like to migrate to EDB. I create a SystemDSN using the
Advantage ODBC driver and try to use the EDB BDE migrator as I
previously did with DBISAM. When I try to perform the migration I get
ElevateDB Error #202, "An error occurred with the module edbmigratebde
(An error occurred while attempting to initialize the Borland Database
Engine (error$2108))"

I include the "DatabaseName" parameter as well as the "TablePasswords"
parameter, but where I think an error might be occurring is that there
is no allowance for a username parameter.

What I can do as a work-around (but prefer not to) is migrate from
Advantage to DBISAM v4.25 and then migrate once again from DBISAM to
EDB. I wouldn't think this should be necessary however.

Am I missing something or are we not able to migrate ODBC source
SystemDSN databases as we can in DBISAM?

Thanks for any information...

-------------
Regards,
Jan Ferguson

Jan,

<< As an example, I have a number of Advantage databases (v6, v7 and v8)
which I would like to migrate to EDB. I create a SystemDSN using the
Advantage ODBC driver and try to use the EDB BDE migrator as I previously
did with DBISAM. When I try to perform the migration I get ElevateDB Error
#202, "An error occurred with the module edbmigratebde (An error occurred
while attempting to initialize the Borland Database Engine (error$2108))" >>

It's a BDE issue - see here:

http://groups.google.com/group/borland.public.delphi.database.desktop/browse_frm/thread/3d29ef2a6a41c6a3/6aff00c04a7e3dfc?lnk=st&q=bde+error+2108#6aff00c04a7e3dfc

<< I include the "DatabaseName" parameter as well as the "TablePasswords"
parameter, but where I think an error might be occurring is that there is no
allowance for a username parameter. >>

I don't think it has anything to do with that - the ODBC data source's alias
configuration is where you would put that information.

<< Am I missing something or are we not able to migrate ODBC source
SystemDSN databases as we can in DBISAM? >>

No, it should still work just fine, and does so here with the BDE.  In
addition, there is a new ADO migrator in 1.06 that will migrate ODBC data
sources also.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks for the info Tim. I'll check into it further.

<<<<"An error occurred with the
<<<<module edbmigratebde (An error occurred while attempting to
<<<<initialize the Borland Database Engine (error$2108))" >>

<<It's a BDE issue - see here:

The funny thing is that I don't get a "2108" error in DBISAM but from
reading the Borland explanation of what a 2108 code is, I should have a
problem with DBISAM and other databases yet I don't.

<<In addition, there is a new ADO migrator in 1.06 that will migrate
<<ODBC data sources also.

I initially got an error with the ADO migrator so I removed it. I don't
remember what the error was (probably something I didn't do right
I'll check into that as well.

Jan

Jan,

<< The funny thing is that I don't get a "2108" error in DBISAM but from
reading the Borland explanation of what a 2108 code is, I should have a
problem with DBISAM and other databases yet I don't. >>

It could be the version of the BDE that the migrator is built with.  If
you're using the ANSI BDE migrator, then it is built with Delphi 7 and would
require the compatible BDE version for that version of Delphi.

<< I initially got an error with the ADO migrator so I removed it. I don't
remember what the error was (probably something I didn't do right I'll
check into that as well. >>

If you need further help, just let me know.  I tested the ADO migrator with
an Access database, but it should work equally as well with other databases.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim...I will check it out next week. I am heading out of town
until Sunday but will check it next week. I appreciate the assistance.

--
Regards,
Jan Ferguson


Tim Young [Elevate Software] wrote:

<<Jan,
<<
<<<< The funny thing is that I don't get a "2108" error in DBISAM but
<<<<from reading the Borland explanation of what a 2108 code is, I
<<<<should have a problem with DBISAM and other databases yet I don't.
<<<<>>
<<
<<It could be the version of the BDE that the migrator is built with.
<<If you're using the ANSI BDE migrator, then it is built with Delphi 7
<<and would require the compatible BDE version for that version of
<<Delphi.
<<
<<<< I initially got an error with the ADO migrator so I removed it. I
<<<<don't remember what the error was (probably something I didn't do
<<<<right I'll check into that as well. >>
<<
<<If you need further help, just let me know.  I tested the ADO
<<migrator with an Access database, but it should work equally as well
<<with other databases.
<<
<<--
<<Tim Young
<<Elevate Software
<<www.elevatesoft.com
>>

Tim