Subject: | |
From: | |
Reply To: | |
Date: | Tue, 26 Nov 1996 11:53:44 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
The Image error your referencing says you tried DBUPDATE with the
data base open in modes 5, 6, 7 or 8. To fix this you'll have to run
IMAGESQL and do an update user to mode = 1, 2, 3 or 4, or add another
user with the correct write mode and change your ODBC.INI file to this
user.
>>> Curt Brimacomb <[log in to unmask]> 11/26/96 11:14am >>>
Dear MS Access users,
I have been playing with ODBC and have it working except for updates,
deletes, etc. I called HP and they told me that it is a Microsoft problem
that occurs because Access does not really understand the image/sql
environment and tries to do something twice?
Does this mean that MS Access can only be used for inquiry purposes?
Has
anyone got a work around?
the error that I am getting is this:
ODBC - update filaed on attached table AP_APMAST
image/sql error 156 turboimage error -14 turboimage intrinsic 406 &
Auxilary
error 0 (DBERR 13352)
Insert/Update/Delete statement had no effect due to exection errors
(DBERR
2292)(#13552)
Any help would be appreciated!
Running MPE 5.0, HPPCAPI a.g1.05, Win3.11, Access 2.0
TIA
**************************************************************************
Curt Brimacomb [log in to unmask]
System Manager
Idaho Computer Services, Inc. 1-208-734-2245
Twin Falls, ID 83303-0446 1-208-733-9663 (fax)
http://www.magiclink.com
|
|
|