>Delta's db support is much more robust, given that it was actually not an >afterthought....
Amazing how that is true of so much software. Oh, you were looking for some real ideas... > I would really like some mechanism to get a detailed error message returned > from the SQL SP back into Delta to display & log to > users so they don't have to >perform SQL queries to find what errors have > occurred. I assume you are looking for 'DBMS' error messages (e.g "invalid tablename in SELECT " or "constraint violation on INSERT") as contrasted to "A DBMS action succeeded at the DBMS level but Delta had a problem?" I don't know Delta (although I may have to learn quickly and soon), but if there is no 'native' facility for this you could look at creating your own "exit" type code which will. return what you want. Or, maybe you could code up your stored procedure as a FUNCTION and have it return an error message. That's what I just did using Mercator with Oracle; works good. Michael C. Mattias Tal Systems Inc. Racine WI [email protected] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
