Fixed: ODBC Driver created for v2.

I have upgrade to version 2.0.
Now i have a problem with the ODBC driver with Crystal Reports.
I can view the field at the database.
When i will retrieve data from the database i get the error: "Query Engine Error: ‘42500:[Lantica, Inc][Sesame ODBC driver][ISAM]Unknown field type found. Type: 19’"

What can be the problem?

Yes it's very important we have about 25 crystal reports for daily use.

Thanks for the proxy vote, Erika.

Although important, I did find that the inability to use it with subforms reduced its capability tremendously, for my needs.

I actually had a request last week to use ACT! with Sesame and ODBC for data sharing.  But it looks like we will be doing import/export instead.  Hmmm, didn't you once do a beta2 demo using SQL data retrievals?  I seem to recall that, but have forgotten the technique.  That may be an alternative to ODBC.

Bob_Hansen wrote on Aug 13^th, 2007 at 6:53pm:


Hello Bob,

The ODBC link in 1.X works with subforms. The Parent Record ID's and the Child Record ID's are grabbed by the driver and all that needs to be created is a Left Outer Join To include all Parent Records and then only the children parented to the record, assuming the subform is a natural link, and remove the Inner Join on _RECORDID_ if MSQuery creates it for you. The Parent/Child join is not automatic as it would differ between relational and natural linking methods.

-Ray

The new ODBC driver works fine for me Thanks.!

Both ODBC drivers can not be installed on the same system as the new sesodbc.dll overwrites the old one.

-Ray

The Version 2 ODBC driver can only correctly connect to a Sesame Version 2 server, so the files would be converted when you tried to open them with ODBC.

Renaming them and then swapping them back and forth would be your best bet or rerunning the setup when you need to switch back and forth.

You can not rename one of the dll files before you define the ODBC connections, It won't work.

-Ray