That sorted it

Roy Lambert

Disregard my last post. It is incorrect that it should get copied to
the EDBManager install directory but rather it (they) needs to be
installed in the same directory which holds the configuration file.
After reading this in the SQL user manual, it now works for me.

--
Regards,
Jan Ferguson


J. B. Ferguson wrote:

<<Gord,
<<
<<When I try that I still get nothing.
<<
<<--
<<Regards,
<<Jan Ferguson
<<
<<
<<gord k wrote:
<<
<<<<Worked ok for me from edb manager, copied bdemigrator dll to
<<<<edbmanager install dir.
<<<<
<<<<--
<<<<Regards
<<<<Gord
<<<<
<<<<"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
<<<<<<
<<<<<<This option doesn't seem to be working. I get nothing in the
<<<<<<migrator drop  down.
<<<<<<
<<<<<<Roy Lambert
>>

J

Now I've run the migrator (DBISAM V4 flavour) I don't know wether its just perception but it seems a fair bit slower than the old one. More robust possibly, and I don't really care since I won't be using it very often. CPU usage stuck c50% for the 6 hours it was running with little disk access.

Roy Lambert

Roy,

<< This option doesn't seem to be working. I get nothing in the migrator
drop down. >>

From the link to the manual in the release notes:

====================================
You can find these migrator modules as part of the ElevateDB Additional
Software and Utilities installation in the \libs subdirectory under the main
installation directory.

Note
These are the ANSI versions of these migrators. ElevateDB also includes
Unicode versions of these migrators, and they have the same names as the
above migrators with 'unicode' appended to the end of the name.

In order to reference these migrator modules from within a migrator in
ElevateDB, you must make sure that the migrator modules (DLLs) are present
in the same folder as the configuration file. You can verify that this is
done by using the following SELECT statement on the special system-defined
Configuration Database:

SELECT * FROM Modules

If the rows returned from the above query include the five migrator modules
listed above, then the migrator modules have been installed successfully in
the same folder as the configuration file. Please see the Architecture topic
for more information on the configuration file.

====================================

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


My problem was that the first installation didn't install the \libs directory. The second one did. Who knows why - computers eh!

Roy Lambert

Roy,

<< My problem was that the first installation didn't install the \libs
directory. The second one did. Who knows why - computers eh! >>

I don't know what was going on in that instance - it should install it every
time.

--
Tim Young
Elevate Software
www.elevatesoft.com