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

Client Access File Transfer Problem

  • Subject: Client Access File Transfer Problem
  • From: Cyndi Bradberry <CyndiB@xxxxxxxx>
  • Date: Fri, 31 Jul 1998 15:57:07 -0600
 
I have a problem with Client Access.
I am at Client Access V3R1M2 SF39220. I have the cwbtfr.ini with
the ForceTranslation=1  and I can transfer files from the AS/400
with no problem.
On July 25th, we put on the latest cum for V3R7. 
I now have two pc's (at least) that say Client Access V3R1M2
SF41904.  We have replaced the .ini file on their drives (it was
there before cum) but when they d/l a file, they still get hex
instead of ASCII. 
What do I need to get them back to file translation?
TIA
Cyndi Bradberry
IHFA, Boise Idaho
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.