ODBC issue with Progress 9.0B, Merant 3.5, and Micr o

My first experience with Progress ODBC is with vantage patch 811, so I don't
have a comparison. However, I am getting the exact same error. I don't
have any programs tied to the ODBC (yet), so I have just been browsing the
tables and writing a few reports over the last couple of days. What I have
found, is that if I have a table open, and I page down rapidly, the error
occurs. I can then immediately reopen the table and can still see the data,
without redefining the link. If I page slowly, and allow each screen to
finish painting before paging again, I can get to the end of the file
without the error.

This obviously won't help your programs, but I thought it might be a clue to
the source of the problem. I had assumed that there must be some setting or
parameter that could be tweaked to make it perform better.

If you find anything, I would appreciate knowing the answer. If I find
something, I'll let you know...B

-----Original Message-----
From: H. Dale Puls [mailto:DPuls@...]
Sent: Thursday, July 20, 2000 4:16 PM
To: vantage@egroups.com
Subject: [Vantage] ODBC issue with Progress 9.0B, Merant 3.5, and
Microsof t Access (2000 & 97)

I have been using the Merant ODBC drivers with Microsoft Access to query
Vantage since November 1999 and have experienced no problems until now.
Recently I have been getting an "ODBC -call failed" message when I try to
load a Vantage table I have loaded multiple times before. (This problem did
not occur until after I upgraded to patch 811 but I'm not sure that has
anything to do with it.) Even when the error occurs with one Vantage table,
other tables are still accessible from the same Access database so I know
the ODBC link is still alive. I have been successful in deleting the link
and then re-establishing it but this is a poor "fix" and doesn't always

I already have one application that passes shipment information from Vantage
into UPS's Worldship product. The application uses Access to extract the
shipment information from Vantage and then put the information in a form
compatible to UPS. The loss of ODBC connectivity to the shipment tables
could cause us to not be able to ship.

I talked with tech-support and they could only say that Progress isn't very
friendly with Microsoft Access and that I'm not the only one experiencing an
ODBC problem. Any suggestions?

H. Dale Puls
Pacesetter Electronics

[Non-text portions of this message have been removed]

Still looking for the complete Application Server solution?
Find answers and a $75 gift certificate at the Intraware App Server
Webinar. Sign up at:

We no longer allow attachments to files. To access/share Report Files,
please go to the following link: http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)