Exporting Word document without quote marks

[Bruce Easton]

Also, Rick, one way that using export for this purpose differs from 
using jsfile command is that when using export via Request Output, you 
execute across both the export command and the assignments for each 
record selected for output.  When using jsfile via Request Output, you 
only want to open the output file in output processing just before 
processing the first record selected for output.  Subsequent records 
will just perform the assignment (i.e., "jsfile :tx [something]"); and 
the closing of the output file should only occur when all records have 
been processed:

'(output processing)

            If:
       Then: jsfile :tx 1<2<3
             If:
       Then: jsfile :tx  4<5
            If:
       Then: end
@once If:     '(only open just before 1st record output)
       Then: jsfile :cr  "/tmp/outfile"
            If:
      Then: end
@done If:    '(close after all records have been processed)
       Then:  jsfile :cr-
            If:
      Then: end


On 6/1/15 6:15 PM, Bruce Easton via Filepro-list wrote:
> Rick, there are a few easy ways to "export" where the fields are not 
> quoted in the output.
>
> Let's say you're running this on Unix/Linux and  want to export a 
> series of fields to be separated by a space and where each filepro 
> input record should be separated in the output by a newline.  This 
> could be done in at least a couple of ways:
>
> 1.  export ascii  outfile=/tmp/outfile.txt  r=\n f=32
>   then your export assignment lines would be simply outfile(1)=xx 
> outfile(2)=xy......etc.
>   in this case we are saying to use decimal 32, a space character, as 
> the field delimiter
>
> You could also embed your space in the assignment
>
> 2.  export ascii  outfile=/tmp/outfile.txt  f=\n
>   in this case assign like this: outfile(1)=xx<xy<xz......... etc.
>   same result
>
> Another way that would work for my example is to use filepro's jsfile 
> commands in processing instead of export:
>
> jsfile :cr /tmp/outfile.txt           'open the output file
> jsfile :tx xx<xy<xz  ....... etc.   'write to it
> jsfile :cr-                                  'close the output file
>
> And another way would be to use filepro's OPEN, WRITELINE and CLOSE 
> file commands.
> One advantage of these commands is they allow you to test things like 
> successful open, number of bytes written, so your program, if it 
> doesn't actually bomb out, can include some validation on what is 
> output, perhaps even compared against the source data.
>
> Bruce
>
>
> On 6/1/15 5:05 PM, Richard Hane via Filepro-list wrote:
>> Hi List.
>> I am in the process of installing our new ERP software.  The updated 
>> version now has a field to keep collection notes in by customer.  For 
>> the last 17 years we have done this in a filepro file.  Since not all 
>> notes are current (some back 17 yrs), I want to give the credit dept 
>> the option to select (copy and paste) the note they want in to the 
>> ERP software.
>> What I designed was a series of txt files (one for each customer 
>> code) generated by fp using export word.  No problem.
>> However, the file produces quotes around each field.  Any one have a 
>> suggestion as how to do this with out the quotation marks?
>> Thank you in advanceRick Hane
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: 
>> <http://mailman.celestial.com/pipermail/filepro-list/attachments/20150601/df90695a/attachment.html>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>