RE: Upgrading to 7.1 -- 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.

Everything worked fine without any real reconfiguration changes.

Thanks,
Tommy Holden
Direct: 615-259-5814
Main Line: 615.256.2424 ext. 5814
Toll-Free: 1.800.228.3644 ext.5814
fax: 615-793-7617

From: Jerry Adams <Jerry@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 11/05/2010 02:36 PM
Subject: RE: Upgrading to 7.1
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Thanks, Tommy. That's something I had not thought of. When we went from
V5R3 to V5R4, I remember that we upgraded Access for Windows to V5R4. I
just checked an "old" PC, and it is at Access V5R4. Mine is at V6R1, but
I always put the new stuff on my PC first to test it and then only put it
on client PCs when there is a "need".

After installing Access 7.1 on the client PCs, did you have to do any
reconfiguration on the PC for the ODBC problem or did installing the new
release simply replace the ODBC driver and everything worked without any
other changes? This is, as I said, the kind of thing that I frequently
overlook.

Jerry C. Adams
IBM System i Programmer/Analyst
Reporter: Yogi, have you made up your mind yet?
Yogi Berra: Not that I know of.

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.