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. Initially all attempts to run the applications failed on "establish connection", because, it emerged, a new version of ODBCLink/SE needed to be installed on each client PC (old version 5.55.02 new version 5.56.12). However even after installation of the new driver on each PC, significant performance problems were experienced. Some functions that previously took few (if any) seconds, now took 5 to 10 minutes! Our client has raised this problem with HP but as of yesterday had not had the situation resolved. Yesterday we decided to try reproduce the problem. We installed MPE/iX 5.5 power patch 7 on our own HP3000, installed the new ODBCLink/SE driver on each potential client PC, and tried our luck. We had exactly the same experience as our client. 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. We have been through everything we know to try and find out what is going wrong. We also now have a call logged with HP, as of lunchtime today, but have had no response. Our client has now been unable to use some "production" applications for a whole week and is getting extremely anxious. Can anyone help? Please. Chris Baxter TJ Systems