Subject: | |
From: | |
Reply To: | |
Date: | Fri, 23 Apr 1999 09:54:10 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
James Byrne responds,
> You are most likely going throuh the Jet engine (probably 3.5 or
> 3.51) and this requires that the row have a unique index to permit
> updates. There is a way to fake out VB to make it believe that
> this is the case. I will try and locate a code example for you
> later this morning.
While true that JET requires a unique key for INSERT and UPDATE, the
original poster indicated that they were using ADO. ADO uses OLE DB and
probably the standard ODBC Provider for Image/SQL - which does not load the
JET database engine.
RDO and ADO, as well as using DAO methods under ODBCDirect load other
engines than JET. RDO and ODBCDirect both load the RDO engine, and ADO
loads the OLE DB engine - both of which bypass the JET overhead and work
directly with the server. ADO is more apt to perform PassThrough queries.
One thing that should be looked at is IMAGESQL.PUB.SYS. Perform a DI USER
on the user@account, and ensure that the proper open mode is being used
and/or the password is logged. The default is Class 64 and MODE=5. UPDATE
USER is required to use one of MODE1 through 4 is required for UPDATE or
INSERT to work, and if not the database Creator, a Password or Class is
required.
Regards,
Joe Geiser
====================================================
Joe Geiser, President and Senior Partner
CSI Business Solutions, LLC
Phone: +1(215) 945.8100 Fax: +1(215) 943.8408
Toll Free (US/Canada): (877) 945.8100
====================================================
|
|
|