This content has been marked as final. Show 3 replies
I suspect this is because when oo4o constructs the UPDATE statement internally it will use the "column name" "myname" which of course does not exist on the table.
oo4o has only the columns in the result set to work from so it has no way of knowing if a particular column is an alias or not.
This check must be done when you open the recordset for the first time. Some kind of parse must take place on the specified SQL and then the recordset is set to not updatable if a column alias is found.
Hope this goes some way to answering your question.
You only get a read-only dynaset if using column aliases...
You will also get a Read-Only recordset if your SQL performs a join across two or more tables.
There are also some more rules that prevent a recordset from being updatable. For example if the DISTINCT clause is used.