RE: UPS ODBC Gone Wild!

Thanks for the help...

I found two things:
1) The WorldShip 6.0 software seemed to corrupt the SQLPKG objects on the 400.  
This may have actually been our fault...the user updated one machine to version 
6, but others were left at 5.

2) When nothing worked using our normal user/pass/library I tried using 
alternate user ids which introduced the problem you described below:  It 
scanned every file in my libl...ugh.


Resolution:
1) Take ver 6 machine back to ver 5.  I probably could have taken others up, 
but I *know* ver 5 works.
2) Delete all SQLPKG objects created by UPS WorldShip.
3) Logon with original ID which only has a single small library in its libl. 

Thanks again,
Dave