|
From: David Cawthon However, I have discovered an odd twist to this issue: This only happens on my first interactive SQL session. The second and subsequent concurrent interactive SQL sessions work as I would expect.
Just for giggles, try the following as the first instruction in the first session and see if it fixes things: SET CURRENT SCHEMA = DEFAULT On MY machine, that sets the current schema to *LIBL (which, oddly enough, is not a valid option for the SET SCHEMA instruction). Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.