RE: *SQLPKG question -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Steve McKay wrote:

> I ask this because I have SQLPKG objects in QGPL *and* I have SQLPKG
> objects with identical names to those in QGPL in the data library of a
> vendor package.  I believe this is causing a problem that we
> are having
> with the vendor package.

I know that you can specify, on the Client Access ODBC driver, the
library to use for packages.  It defaults to QGPL.  This will be why you
have them in more than one library.  I don't think deleting them will do
any harm: they'll just be recreated the first time they're needed.

The possible problem is that, if you still have different users' drivers
pointing at different libraries, you'll get them created in the
different libraries again.

Cheers,

Martin.

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

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.