just as an info for you.
Last I had an error caused by switching Database Compatibility Level from 80 to 90. After this action some RecordSet.DoQuery() calls where throwing the exception, that FOR BROWSE is not valid. My problem: I didn't used "For Browse " in my query, SBO was adding it!
Here an older SDN-Link to this topic:
[When should I use "FOR BROWSE |when-should-i-use-for-browse]
And in the SAP Notes maybe I found why it happens:
[809384 - END statement in queries|https://service.sap.com/sap/support/notes/809384]
(The described solution didn't work in my case.)
Do anyone think, there is a hidden great problem, because a lot of addons-developer do use "FOR BROWSE" in SQL-statements frequently?
Do you think, SBO adds FOR BROWSE automatically only when using MSSQL-connection instead of MSSQL_2005?