Sorin,

Are you saying you are still getting an error? It's really quite
simple. I'll go through it step-by-step:

The "Create Module" statement should look like this:

CREATE MODULE "edbmigratedbe"

The "Path" statement should simply be the entire path, including the
complete file name, of the location of the edbmigrate library. For
example, I keep mine on a separate server in a folder which only has
the edbsrvr.exe application and the migration files. So *MY* path
statement looks like this:

PATH 'C:\Program Files\ElevateDB\edbmigratebde.dll'
(*Note*: Yours will be different based on where you place the migration
file.)

The "Description" statement is optional but it helps to understand
which module has been installed. I myself use the description of "BDE
Migrator". Sop *MY* description statement looks like this:

DESCRIPTION 'BDE Migrator'

Pull them all together (again...allowing for your *OWN* path and
description statements) and it will look like this:

CREATE MODULE "edbmigratedbe"
PATH 'C:\Program Files\ElevateDB\edbmigratebde.dll'
DESCRIPTION 'BDE Migrator'

Run the SQL statement and it should install with no issues.

Hope this helps...

--
Jan Ferguson [Team Elevate]


Sorin H wrote:

> I use this statement following the example given on the manual and on
> the previous Tim answer.
>
> I try your example on diferent version '...\libs\edbmigratebde.dll'
> or '... \libs\edbmigratebde\edbmigratebde.dll' and both return the
> #202 error

"J.B. Ferguson" <jnobspamfergnospamusonatgnospammaildotcom> wrote in message
> Are you saying you are still getting an error? It's really quite
> simple. I'll go through it step-by-step:
>
> The "Create Module" statement should look like this:
>
> CREATE MODULE "edbmigratedbe"
>
> The "Path" statement should simply be the entire path, including the
> complete file name, of the location of the edbmigrate library. For
> example, I keep mine on a separate server in a folder which only has
> the edbsrvr.exe application and the migration files. So *MY* path
> statement looks like this:
>
> PATH 'C:\Program Files\ElevateDB\edbmigratebde.dll'
> (*Note*: Yours will be different based on where you place the migration
> file.)
>
> The "Description" statement is optional but it helps to understand
> which module has been installed. I myself use the description of "BDE
> Migrator". Sop *MY* description statement looks like this:
>
> DESCRIPTION 'BDE Migrator'
>
> Pull them all together (again...allowing for your *OWN* path and
> description statements) and it will look like this:
>
> CREATE MODULE "edbmigratedbe"
> PATH 'C:\Program Files\ElevateDB\edbmigratebde.dll'
> DESCRIPTION 'BDE Migrator'
>
> Run the SQL statement and it should install with no issues.
>
> Hope this helps...

Thanks for the effort

The command I use is:

CREATE MODULE "edbmigratebde"
PATH 'C:\Program Files\ElevateDB Additional\Version
2\libs\edbmigratebde\edbmigratebde.dll'
DESCRIPTION 'BDE Migrator'

and yes it raise an error.

The path is correct it is the default from the installation and I check, the
dll file exist on this directory.
Something else strange is the fact that after I run the "Create Database
Migrators" all the migrators
appears on the Installed Modules and only the bde migrator doesn't.

Thanks
Sorin

Sorin,

Have you tried running the CREATE MODULE set of statements for the BDE
separately, via a SQL statement, within the EDB Manager?

--
Jan Ferguson [Team Elevate]


Sorin H wrote:

> The command I use is:
>
> CREATE MODULE "edbmigratebde"
> PATH 'C:\Program Files\ElevateDB Additional\Version
> 2\libs\edbmigratebde\edbmigratebde.dll' DESCRIPTION 'BDE Migrator'
>
> and yes it raise an error.
>
> The path is correct it is the default from the installation and I
> check, the dll file exist on this directory.  Something else strange
> is the fact that after I run the "Create Database Migrators" all the
> migrators appears on the Installed Modules and only the bde migrator
> doesn't.

OK Stop

The probem was on the path "Version 2" has a space I didn't notice.
Now it's ok.

Thanks
Sorin

Glad you found the problem. Looking at your previous post, it appeared
you had it correct with the spae between the "Version" and the "2", so
I couldn't figure out what the issue could have been:

> PATH 'C:\Program Files\ElevateDB Additional\Version
2\libs\edbmigratebde\edbmigratebde.dll'

--
Jan Ferguson [Team Elevate]


Sorin H wrote:

> OK Stop
>
> The probem was on the path "Version 2" has a space I didn't notice.
> Now it's ok.
>
> Thanks
> Sorin

Sorin,

<< The probem was on the path "Version 2" has a space I didn't notice. Now
it's ok. >>

These types of issues are the worst - you can sit and stare at them for days
and not notice the error.

--
Tim Young
Elevate Software
www.elevatesoft.com

"J.B. Ferguson" <jnobspamfergnospamusonatgnospammaildotcom> wrote in message
> Glad you found the problem. Looking at your previous post, it appeared
> you had it correct with the spae between the "Version" and the "2", so
> I couldn't figure out what the issue could have been:
>
>> PATH 'C:\Program Files\ElevateDB Additional\Version
> 2\libs\edbmigratebde\edbmigratebde.dll'
>

I think that here is a CR sign and on the edb menager I used to change this
to one line
maybe this cause the problem.

In any case thanks again to you and Tim for the support
Sorin

You're very welcome.

--
Jan Ferguson


Sorin H wrote:

> In any case thanks again to you and Tim for the support