Just got started with EDB, so far sooo good. I am bound to be asking a few questions in
the next few days though!

First tiny request.

When migrating from DBISAM -> EDB it would be great if there was a choice over which
tables to migrate, i.e. pull up a pick list to tick off which tables you want.

I realise most people just want all of them, but I have some multi-gig databases & only
want to transfer some parts, as other parts are historical.

Adam

adam


Nice idea - as a temporary workround rename the table extensions to something the migrator doesn't recognise - that should stop it. Just remember to rename them afterwards

Roy Lambert [Team Elevate]

Adam,

<< When migrating from DBISAM -> EDB it would be great if there was a choice
over which tables to migrate, i.e. pull up a pick list to tick off which
tables you want.

I realise most people just want all of them, but I have some multi-gig
databases & only want to transfer some parts, as other parts are historical.
>>

I'll see about getting table selection added.  I've got to change around
some of the migration code anyways.

--
Tim Young
Elevate Software
www.elevatesoft.com

That's a great workaround. Thanks.

Having transferred several DBs yesterday I encountered 1 more niggle of my own making.

1 older DB I transferred had a corrupted table in it, the migration process simply stopped
at the corrupt table, fair enough really but better behaviour would have been either to
just skip a corrupt table and hold a message in a log about it or (perhaps) attempt to
repair the table & then migrate it?

Adam

adam


>That's a great workaround. Thanks.

Old family motto - If at first you don't succeed CHEAT!

>Having transferred several DBs yesterday I encountered 1 more niggle of my own making.
>
>1 older DB I transferred had a corrupted table in it, the migration process simply stopped
>at the corrupt table, fair enough really but better behaviour would have been either to
>just skip a corrupt table and hold a message in a log about it or (perhaps) attempt to
>repair the table & then migrate it?

The second option makes sense but not the first with the new concept of database rather than a collection of tables. I keep coming up against some of these concepts and having to send my brain through another rinse cycle to try and get them straight.

Roy Lambert [Team Elevate]