At 10:00 PM 4/25/96 GMT, you wrote:
>I have all but given up on this interface. I am running MPE 5.0, have the
>latest Allbase and ODBC, and am trying to do the following:
>
>Run MSAccess to link via ODBC to an Allbase database which is linked to an
>Image database. The application connects and I can pull up the sets in
>table view(which is rather slow and doesn't seem to continue pulling up all
>records unless you keep hitting the scroll bar),but after the first
>transaction within the application, an ODBC error occurs. Within the trace
>file, it is reporting a DBLOCK failure(intrinsic 409, error 22) stating the
>database is locked by another process yet the MSAccess program is the only
>write program accessing the database. The error is also listed as mode 4 or 6
>access when in Image/SQL the user is defined as using mode 1. The ODBC is
>setup using WSOCKETS and CS; the login is the creator, and the network is
>LanManager 2.2B. Any help you could provide would be greatly appreciated.
>
>Gary Weeks
>[log in to unmask]
>
 
Gary,
 
We at M.B. Foster have heard of this problem but so far, we think, only in
connection with Allbase/Net setups where you are really accessing an Image
dataset on one system (hp3000) together with a "real" Allbase table on
another system (hp9000?).  If this is your case, you might try to define two
"data sources" for the two unique databases.
 
If you are simply trying to access a single Image database via Image/SQL
then you should really try
<PLUG>
the ODBCLink option of DataExpress which doesn't require all of the baggage
of Image/SQL and/or Allbase and gets you many additional benefits such as
KSAM, flat files, serial (modem) connections and Cognos PDL support, to name
a few.
call 1-800-ANSWERS or 1-613-448-2333 for more info
</PLUG>
 
 
 
Brian Duncombe ([log in to unmask]) - M.B. Foster Software Labs
"Inside every large program is a small one struggling to get out."
          C. A. R. Hoare