I really need some help linking to a progress database using Microsoft Access 2002 (xp).
Server: Win2K
Progress: 9.1CODBC: Merant 3.7
App: Microsoft Access 97/2000/2002
We have gone through all the channels. First our software supplier. They are still working on the problem (6 months later).
Second we spoke with Frontstep. They supply support for Syteline and apparently want nothing to do with ODBC issues.
Finally I spoke with Datadirect. They suggested every driver from the Intersolv driver, to the latest 3.7 driver.
We have tried all these drivers, we have opened (honestly) hundreds of support cases. We have given these guys every bit of information possible.
And on top of all that, techs have been out to look at the problems, but have left... never to be heard from again.
This is extremely frustrating!
Problems: Two tables ARTRAN and MATLTRAN have values higher than the field definition, this blows us up every time.
We open a table and it displays a bit, then after a few seconds crashes access.
If we jump to the end of a table it crashes access.
We open a table and it opens with #name in every field.
We open a table and it opens with #deleted in every field.
But yet the test connection works every time.
Also, dumping the data into a table with VB code works every time.
Finally, using a .UDL connection to the database works every time with every table when importing data into a program such as Excel.
The broker is running the ports are correct. All environment variables that need to be set are set... the system has been analyzed by outside "progress" techs from the company that sold us the software.
Opening a linked table in access blows up more than 50% of the time.
Initially it seemed to be a user issue... during mid day when alot of users are working in the system crashes happen more often. Later in the afternoon when everyone has gone home connections work about 75% of the time.
All we need / want is a stable connection. To rewrite the access application using code would be slow and ALOT of work (hundreds of queries).
Can anyone help? I am willing to pick up the cost of a call... email, sample code, anything?
I'm frustrated, our company is frustrated. We have exhausted our support with the three mentioned companies.
If you need any further information, please email me.
Also interested in getting a connection using .ASP... I get a very odd error that seems to be discussed often on the web. (extra parameter not allowed). No solution.
nehe@connect.ab.ca
Server: Win2K
Progress: 9.1CODBC: Merant 3.7
App: Microsoft Access 97/2000/2002
We have gone through all the channels. First our software supplier. They are still working on the problem (6 months later).
Second we spoke with Frontstep. They supply support for Syteline and apparently want nothing to do with ODBC issues.
Finally I spoke with Datadirect. They suggested every driver from the Intersolv driver, to the latest 3.7 driver.
We have tried all these drivers, we have opened (honestly) hundreds of support cases. We have given these guys every bit of information possible.
And on top of all that, techs have been out to look at the problems, but have left... never to be heard from again.
This is extremely frustrating!
Problems: Two tables ARTRAN and MATLTRAN have values higher than the field definition, this blows us up every time.
We open a table and it displays a bit, then after a few seconds crashes access.
If we jump to the end of a table it crashes access.
We open a table and it opens with #name in every field.
We open a table and it opens with #deleted in every field.
But yet the test connection works every time.
Also, dumping the data into a table with VB code works every time.
Finally, using a .UDL connection to the database works every time with every table when importing data into a program such as Excel.
The broker is running the ports are correct. All environment variables that need to be set are set... the system has been analyzed by outside "progress" techs from the company that sold us the software.
Opening a linked table in access blows up more than 50% of the time.
Initially it seemed to be a user issue... during mid day when alot of users are working in the system crashes happen more often. Later in the afternoon when everyone has gone home connections work about 75% of the time.
All we need / want is a stable connection. To rewrite the access application using code would be slow and ALOT of work (hundreds of queries).
Can anyone help? I am willing to pick up the cost of a call... email, sample code, anything?
I'm frustrated, our company is frustrated. We have exhausted our support with the three mentioned companies.
If you need any further information, please email me.
Also interested in getting a connection using .ASP... I get a very odd error that seems to be discussed often on the web. (extra parameter not allowed). No solution.
nehe@connect.ab.ca
