Chris Baxter, writing as TJ Systems <[log in to unmask]>, writes:

> We have been using VB to access Image/SQL DBEs on HP3000 via ODBCLink/SE
for
> some time, both for in-house use and in customer applications.
>
> Last Thursday a client who makes significant use of these applications
> installed MPE/iX 5.5 power patch 7.

<snip>

> Additional findings are that the problems seem to arise on SQL queries
that
> should return more than 100 rows.  We retrieve the data via RDO, and the
> response to the "OpenResultset" statement appears to be swift in each
case.
> However, as soon as the code tries to reference the resultset in any way
by
> checking RowCount, using MoveFirst, MoveLast etc. (or in debug mode using
> any "watch" functionality), the application "waits" for several minutes
> (usually more than 5 and sometimes more than 10).
> When the application does respond it has always only retrieved the first
100
> rows of what was expected to be retrieved.

<snip>

> Can anyone help?

Disclaimer:  I do not say the following in order to berate anyone, it's just
my life's experience.

You get what you pay for.

You probably should upgrade to one of the full-featured ODBC products
instead of relying on a deliberately crippled version of a commercial
product, especially for mission-critical systems.  We use the Linkway
product for a 24x7 shop floor automation application and are quite happy
with it.  If what happened to Chris happened to us, I would not be as
tolerant as Chris seems to be in dealing with HP or CSL or whoever the
vendor was.

Jim Phillips                            Manager of Information Systems
E-Mail: [log in to unmask]     Therm-O-Link, Inc.
Phone: (330) 527-2124                   P. O. Box 285
  Fax: (330) 527-2123                   Garrettsville, Ohio  44231