Export Command

[Rodgers Hemer]

On Oct 4, 2011, at 8:59 AM, Kenneth Brody wrote:

> On 10/4/2011 11:17 AM, Rodgers Hemer wrote:
>> fp5.6.10D4/CentOS5.3
>> 
>> Perhaps someone can explain the odd behavior I have recently noticed in
>> use of the "export" command.  Despite the definitions and instructions
>> in the help file and the filePro manual,  I cannot use the command in
>> the prescribed manner.
> 
> Can you give a specific example that "doesn't work"?
> 
>> While using "export word" I am not able to provide an alternative suffix
>> such as ".xls" or ".doc",
> 
> Can you give a specific example you have tried, along with the filename that ends up being created?
> 
>> and it insists that the "fpmerge" directory be used to receive the output.
> 
> You can give a full path to the filename, and it will go to that directory instead.  It only goes to the fpmerge directory if you don't specify any path.
> 
>> If I try any other combination, a filePro error appears when checking the
>> syntax.
> 
> Please give some specific examples, along with the actual error message you get for each.
> 
>> The syntax checker seems to require that only the output file name be
>> given, with no quotation marks.  If quotation marks are used for the file
>> name, the file is created with the quotation marks as a part of the name
>> with all of the obvious problems that entails when trying to use or modify
>> the file.
> 
> If you specify that the filename should include quotes, then filePro will include quotes in the filename.
> 
> [...]
> 
> This works just fine for me:
> 
>    export word foo=/tmp/export.csv
> 
Ken:

After further study, I found a path definition error that must have caused the problem.  It is working fine now.  Thanks,

Rodgers Hemer