SQL/ODBC can easily be abused by developer's who don't think thru the consequences of their SQL statements - that's true of any platform, not just the HPe3000.  For example, when I started using ODBC on the HPe3000 I used some VB wizards, which,  whilst they demonstrated connectivity, paid no attention to efficiency and resulted in my first SQL query taking 5 minutes to execute - simply because I had asked for all fields for all records from a particular dataset.  I didn't know that's what I had asked for, because I didn't know the SQL that the wizard had generated. 

My advice is tread carefully, change one thing at a time and work out what works best for you.   Some 3rd party ODBC drivers have oddities that you may have to accomodate in your overall strategy (we had a performance problem with one supplier, which they refused to acknowledge  - after we had made the decision to switch suppliers, they announced, alas a few weeks too late, that they had patched and fixed that particular problem). 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *