<Richard Schoen>
FWIW: I was able to lock up a STRSQL job when I tested ArdGate previously by killing the server in the middle of an SQL select command. May want to add that to the QA testing.
</Richard Schoen>
... thank you for the bug report, we will fix it (with low priority). BTW: killing a File Server might lock up EXCEL too!
Using embedded SQL (especialy going the ArdPgm way) has advantages and disadvantages, its easier to use, but has some limitations, a proprietary call level interface (maybe) doesn't have. The java usage is not so important, because ArdGate uses one prestarted JVM serving multiple clients in a multithreaded environment (and this workload could be moved to a Wintel or Linux Box). If the target database has only an ODBC and no JDBC driver available, I would recommend a ODBC based tool anyway and if there is none of both it would not work with any of the mentioned tools anyway.
D*B
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
