JON wrote: > HTH, That explains a lot. I tried the search by "odbc update > allowed" as > you suggested but it didn't yield anything to helped me solve > my issue. I'm > afraid I don't know enough SQL yet to know how to "change my > cursor model" > though I've spent the day searching through my texts. Here's a better > example of the type of query / code that I talking about: > strQry = "SELECT A.Fld1, B.Fld2, C.Fld3 FROM A LEFT JOIN B > ON A.B_ID = > B.B_ID LEFT JOIN C ON A.C_ID = C.C_ID where A.A_ID = 8329 > Order by A.A_ID" > rs.Open strQry, Cn, adOpenStatic, adLockOptimistic > > with the point being that all records in "A" should appear > that match the > where criteria. > > If anybody can give me an example of how they would "change the cursor > model" on this query so that the resulting table is updateable I'd > appreciate it.
Perhaps this message is what you are looking for http://groups.yahoo.com/group/sapdb-general/message/5468 Quote from Thomas Theodor Koetter: How did you set the SQLSetStmtAttr (SQL_ATTR_CONCURRENCY)? If you set it to SQL_CONCUR_READ_ONLY, the error should not appear, i.e. the "FOR UPDATE" will not be added to the statement. Kind regards, Holger _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
