× 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.


  1.  Home
  2. MIDRANGE-L
  3. December 2005

Re: Client Access and Terminal Server ODBC-Update

Network tech removed the CA & service pack, then reinstalled CA (without svc pack) and the VB program now works. Put the service pack back on and again VB pgm fails (same msg listed below). Have removed Svc Pack again so users can work with pgm, but now having a File Transfer license issue (and assume Svc Pack was fixing that). When I have free time, will open a ticket with support. 
jim franz
----- Original Message ----- From: "Tom Jedrzejewicz" <tomjedrz@xxxxxxxxx> 
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, November 30, 2005 12:55 PM
Subject: Re: Client Access and Terminal Server ODBC



Assuming that CAE is the only thing that changed (did the iSeries OS
version change), then the upgrade is probably the culprit.  I suggest
getting the VB programmer's PC to the same CAE version and service
pack, and having the programmer make the application work there.

On 11/30/05, Jim Franz <franz400@xxxxxxxxxxxx> wrote:
On our MS Terminal Server, we just "upgraded" the Client Access Express V5R1 to V5R3 and applied service pack to it. Next morning VB program accessing data on iSeries gets a "Provider not found" error msg. I asked the VB pgmr & he says he is not using a named provider and accessing the iSeries by its ip address. I'm not a VB or Term Server person, but since CA involved they are asking me "what happened". When we looked in Term Server, in ODBC Data Sources, there is no user DSN for CA (and according to VB person, there never was). This same last weekend did load (on i5 V5R3 ) the c5298 cume and hipers, but then some pc's have same vb pgm loaded on their C: drive (not using Term Server) and they are working fine (and have no specific DSN setup). btw- VB pgm calls AS400 pgm to create data, gets AS400 data, then merges into MS Word docs). 
jim franz
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





--
Tom Jedrzejewicz
tomjedrz@xxxxxxxxx

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.