Re: Data Transfer

[Gary Feinstein <gfeinste@xxxxxxxxxxxxxxxxxxx>]

Thanx guys...that was it exactly.  I appreciate the help.  Give
yoursleves
a pat on the back from me and Client Access users everywhere!!!

Neil Palmer wrote:
> 
> Gary Feinstein wrote:
> >
> > I am running a query that outputs data to a file.  I have one field in
> > the query that is a Constant, value 'A'.  Real simple.  I run the query
> > and it looks fine on the display and in the file.  However, when I do a
> > data transfer from the 400 to my PC using Client Access, all fields come
> > out okay other than that one.  I think it outputs as the hex equivalent
> > - C2.  What could be causing this?  Is there something in a data option
> > that I am missing?  I am transferring the file as ASCII text.
> 
  This conversion will be controlled by creating an INI file named
  CWBTFR.INI in the directory Windows was installed to.  The .INI
  file must contain ONE of following lines:
 
  ForceTranslation=0; for no translation of 65535 data
    OR
  ForceTranslation=1; for translation of 65535 data The line you
  chose from above must be within a section named Client Access
  Data Transfer.  Remember, section names are contained within
  open and close brackets.
root
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *