We did a full reload last Friday after installing some new disk.  Today I
received a report that our ODBC clients can no longer update, but "they can
still read just fine".  Being the compleat idiot when in comes to Allbase
and ODBC, I'm grabbing at straws.  Today's ODBCJOB $stdlist says...
!JOB ODBCJOB,MANAGER.SYS,ODBCSE
!PRINT ODBCVER
<mostly snipped but>

@(#)HP36216-03A.G1.12     ALLBASE/PC API 900       ALLBASE/SQL
 ***** WARNING:  Version incompatibility found.

which has appeared there every day since at least 10/1998 but our DBAdmin
guy doesn't seem to care, so that may not be the trouble.  .


Today's ODBCLOG.ODBCSE.SYS says...
100/12/13 02:18:46 233 ODBC listener started
100/12/13 07:13:50 233 Listener created new connection as SYS1 (PIN 82),
IP=10.1
0.3.117
100/12/13 07:13:51 082 ODBCLNSE E.55.02 started from sockets
100/12/13 07:14:00 082 User MGR.MCBA connected to MCBADBE.DATABASE.MCBA,
ClientV
er=E.55.02
100/12/13 07:14:00 082 Cant open odbcver to get DBMS Version
<lots of these snipped, no idea how often this occurs>
100/12/13 07:15:51 082 [Allbase]IMAGE/SQL error 154; TurboIMAGE error -14;
Turbo
IMAGE intrinsic 407, & Auxiliary error 0.  (DBERR 13552)

...Intr 407 is DBPUT, error -14 == "illegal intrinsic in current access
mode".  Seems easy enough, but can anyone point me in the right direction?

K Tracy Pierce, Systems Programmer
Golden Gate Bridge, Hwy & Trnsp Dist
PO Box 9000, Presidio Station
San Francisco, CA  94129-0601
mailto:[log in to unmask]
415-923-2266