Paradox 11 and sql links to Informix

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" wrote in message
>
>> Hi Folks,
>>
>> i am trying to port 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 reports
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.
 >> Stay informed about: Paradox 11 and sql links to Informix 

> To get the forms and reports running again would mean to go through every
> form and to fix the behaviour which is too much effort for staying in
> paradox.

to be honest, that much of a re-write should have used a different
front-end, and left paradox for good.. as wonderful as it is/was, it's a
dead platform..

also, bear in mind in your situation that the BDE (the engine driving it
all) has also been dead for five years.. using any internal SQL Link - ODBC
driver will usually be an interface with a very old version of your
platform, with many black holes.. and quite possibly the same result, the
other way around, because ost companies aren't maintaining and updating
their links to the BDE, either..

--
Steven Green - Myrtle Beach, South Carolina USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards
"Dirk Schnorpfeil" wrote in message

> 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" wrote in message
>>
>>> Hi Folks,
>>>
>>> i am trying to port 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 reports
> 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.
 >> Stay informed about: Paradox 11 and sql links to Informix 

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" wrote in message

> 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" wrote in message
>>
>>> Hi Folks,
>>>
>>> i am trying to port 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 reports
> 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.
 >> Stay informed about: Paradox 11 and sql links to Informix 

Am Mon, 18 Feb 2008 13:16:06 -0700 schrieb Rick Rans:

> 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" wrote in message
>
>> 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" wrote in message
>>>
>>>> Hi Folks,
>>>>
>>>> i am trying to port 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 reports
>> 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.

Hi Rick,

i use the version that cam with paradox 11. I used the same alias name for
the odbc driver. The problem with the informix odbc driver is that the odbc
driver sets the user name infront of the informix table name (e.g.
"informix.table1") while the sql link only shows the table name. After
switching to the odbc alias (same name) i lost all relational connections
between the tables. When trying to recreate them it simply did no work. I
needed to delete the tables in the data model and add them again to connect
them. This leads to unbound fields that must be bound again to the newly
inserted table.

If anyone can give me a hint how to simply switch to odbc tables i would be
very very glad. Otherwise the effort for porting the solution from paradox
5 to paradox 13 is too high.

Many thanks in advance,

Dirk.
 >> Stay informed about: Paradox 11 and sql links to Informix 

Am Mon, 18 Feb 2008 08:34:05 -0500 schrieb Steven Green:

>> To get the forms and reports running again would mean to go through every
>> form and to fix the behaviour which is too much effort for staying in
>> paradox.
>
> to be honest, that much of a re-write should have used a different
> front-end, and left paradox for good.. as wonderful as it is/was, it's a
> dead platform..
>
> also, bear in mind in your situation that the BDE (the engine driving it
> all) has also been dead for five years.. using any internal SQL Link - ODBC
> driver will usually be an interface with a very old version of your
> platform, with many black holes.. and quite possibly the same result, the
> other way around, because ost companies aren't maintaining and updating
> their links to the BDE, either..

Hi Steve,

i think you are right. In the moment i am just checking the options to make
offers to my customer. If i can keep it on paradox for 10 more years i will
save him the money for porting to e.g. .NET. But i must make sure that the
application will continue to run for that timespan.

Ciao, Dirk.
 >> Stay informed about: Paradox 11 and sql links to Informix 

> If i can keep it on paradox for 10 more years i will save him the money
> for porting to e.g. .NET. But i must make sure that the application will
> continue to run for that timespan.

that is a VERY FOOLISH theory.. if your client accepts it, he's more foolish
than you are.. and the real word I want to place in that spot isn't
"foolish"..

--
Steven Green - Myrtle Beach, South Carolina USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards
"Dirk Schnorpfeil" wrote in message

> Am Mon, 18 Feb 2008 08:34:05 -0500 schrieb Steven Green:
>
>>> To get the forms and reports running again would mean to go through
>>> every
>>> form and to fix the behaviour which is too much effort for staying in
>>> paradox.
>>
>> to be honest, that much of a re-write should have used a different
>> front-end, and left paradox for good.. as wonderful as it is/was, it's a
>> dead platform..
>>
>> also, bear in mind in your situation that the BDE (the engine driving it
>> all) has also been dead for five years.. using any internal SQL Link -
>> ODBC
>> driver will usually be an interface with a very old version of your
>> platform, with many black holes.. and quite possibly the same result, the
>> other way around, because ost companies aren't maintaining and updating
>> their links to the BDE, either..
>
> Hi Steve,
>
> i think you are right. In the moment i am just checking the options to
> make
> offers to my customer. If i can keep it on paradox for 10 more years i
> will
> save him the money for porting to e.g. .NET. But i must make sure that the
> application will continue to run for that timespan.
>
> Ciao, Dirk.
 >> Stay informed about: Paradox 11 and sql links to Informix