Dirk
Did you give the ODBC driver the same alias name as the SQL Links driver?
If you did give it the same name, do the table names show up differently
via
the ODBC driver?
I would have thought that using the same alias for the ODBC driver
wouldn't
break the data model, unless the table names change to
"Something.TableName", with the "Something" being a schema name. I would
have though that would also be the case in SQL Links.
As an aside, what version of the BDE and SQL Links did you try?
Rick
"Dirk Schnorpfeil" <D.Schnorpfeil@[EMAIL PROTECTED]
> wrote in message
news:onycz9wg1s2j.npic9c4aa9ju$.dlg@[EMAIL PROTECTED]
> Am Sun, 17 Feb 2008 17:11:20 -0700 schrieb Rick Rans:
>
>> Are you trying to use SQL links or an Informix ODBC driver?
>>
>> Can you use an Informix ODBC driver? I've had compatiblility problems
>> with
>> SQL links using Oracle and have found the ODBC driver the way to go to
>> get
>> around a number of anomolies.
>>
>> Just a WAG
>>
>> "Dirk Schnorpfeil" <D.Schnorpfeil@[EMAIL PROTECTED]
> wrote in message
>> news:cua3qjhuxdcl$.1cm7ewvqmanw2.dlg@[EMAIL PROTECTED]
>>> Hi Folks,
>>>
>>> i am trying to ****t an application from paradox 5 to paradox 11 with
sql
>>> links to informix. My problem:
>>>
>>> Whenever i get an informix error paradox crashes immediate. Informix
>>> ilogin
>>> works and connects to the database. I attached a debugger to paradox
and
>>> found out that the crash is in the informix connection library at
>>> _issek64.
>>> But this crash is only with paradox.
>>>
>>> Any help desperatly needed!
>>>
>>> Thanks, Dirk.
>
> Yes, i tried using the ODBC driver. That one works but all the data
models
> are lost when switching to the odbc driver. Also the programs do not
> behave
> the same way as with informix sql links. To get the forms and re****ts
> running again would mean to go through every form and to fix the
behaviour
> which is too much effort for staying in paradox.
>
> Ciao, Dirk.
|
