I'm posting this on behalf of a co-worker.  Followups please to
comp.lang.basic.visual.database or by e-mail.  This problem involves
an internally developed MS Visual Basic 3.0 application and MS Access 2.0 running
in a Win-OS/2 session under OS/2 Warp.

Forwarded Message:

    I am working on an application using OS/2 Warp as the operating system.
The Application uses DB2/2 Version 2.1 tables with attached Tables to an ACCESS
Database using ODBC.

    The problem I have occurs when I am connecting to the Access Table:

    The First time I run my Application, I connect fine, and the application
runs as designed.

    I then create a separate WinOS2 session, and run a second copy of my
application. The second (simultaneous) copy fails to connect to the ACCESS table.
If I close the application, and then try to run it a second time, the ACCESS
connection fails. The third time I attempt to run the Application in this WinOS2
session, it connects normally, and the application runs correctly.

    I then Create a third separate WinOS2 session, and attempt to run my
application. The same thing happens as described above except it fails to
connect until the fifth attempt.

    The fourth session fails until the 7th attempt.

    I have succeeded in getting 9 simultaneous applications running, however,
the last one took me 17 attempts.

I am unfamiliar with this type of problem, and I fear that Microsoft will simply
blame IBM's OS/2, so I hope somebody has some sort of insight.

--
Jeffrey Lanter       |