ODBC import from INterbase with intersolv driver

[DoctorC]

Hi, probably it's not a EA topic, anyway I'll give a try here and see if I can get any help.
I followed the instructions on your site and managed to configure the import from odbc setup.
When the operation starts I get the following error during the details retriving action:
[INTERSOLV][ODBC Interbase Driver] Number of bound columns exeeds the number of result columns.
Is it a mistake of the ODBC driver or should I configure something else in the import setup?

Thanks,
Enrico

[«Midnight»]

Hi Enrico,

Your question is perfectly valid, and this is a reasonable place to ask it.

NOTE: Before you set out on this quest you should set the Notify option on this thread. It is possible some other user has gone through this before and can provide a solution.

As to the error message it could be from either of your suspected causes. Since you are using a custom (i.e. provided by neither Windows or EA) driver and database you will have to play around on your own. I suggest you look up any options that might affect how the your ODBC driver retrieves tables. My first guess (and it is only a guess) would be to see if there are any security parameters). Also look at whether there are options governing whether system tables are retrieved. [And look for combinations of the two; perhaps EA can 'see' the system tables but not read them.]

Also make sure you have the most recent stable version of your driver. Check whether the driver and database versions are compatible as well.

If all else fails, try creating a new database with only a single table. The table should have only a single field, of a 'simple' data type (perhaps a 32-bit integer or a small fixed-length string). See if you can import the schema from this database. If you can get something like that working then add bits and pieces until you isolate the failure. Perhaps it is a specific data type that is failing.

As soon as you hit a brick wall send a bug report to Sparx. If at all possible generate an empty copy of your database (or the SQL to create it) and attach the file to your bug report. [NB: To attach a file you must either use the Registered Users version of the bug report - use the link above the 'normal' version or go to the Registered Users page of the Sparx site - or you should send an email to Sparx Support via the address on the About Us page of the Sparx site.]

Please post back to tell us what you learn either way.

David

[DoctorC]

David,
thanks for your help.

Indeed EA sees the tables and the mistake is after I select al the tables and I run the import. It's at the first table. I tried selecting just one table but the result is the same. I tried with diffrenet tables one by one and it doesn't work.

On the interbase forum someone suggested to install the Easysoft ODBC interbase driver.

Now I get another mistake:
Unable to obtain table information
So it even doesn't see the tables...

Could you please let me know if there is a way I could use SQL code (metadata file snippets) in EA to design the new database structure (any DDL import?) ? As I have to redesign parts of the db I could create the new db and copy and paste from the metadata txt file the tables I'll keep.

Thanks,
Enrico

[hd]

The Firebird/InterBase(r) from IBPhoenix Inc works fine for me. You can download it from...
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_60_odbc

[DoctorC]

The IBPhoenix driver worked correctly.
Thanks for your help

Enrico