export ascii - default file target

Jose Lerebours fpgroups at gmail.com
Thu Apr 11 22:43:30 UTC 2024


Richard,

PFDSK=C

and

PFPROG=C:\appl


I thought of permissions but if filePro cannot write, it should push an 
error and I created the sub-directory I am targeting.

The process goes through like normal; if I step it through using debug 
on, I can see each record going through the exp(##) assignments and 
reach "write" command ...

ONE NOTE: This process gives user option to also print and if user opts 
to do so, a "print" command is executed.  In my case, I am not printing 
so the "print" command is never true, could this be a factor?


Could export not write data if "print" is present in code but it is 
never reached?


Regards,



On 4/11/24 18:16, Richard D. Williams via Filepro-list wrote:
> Also, check your PFSK variable.
> It might not be "C:" if your on a windows network.
> It might be shared drive letter.
>
> Richard
>
>
> On 4/11/2024 5:09 PM, laura.k.brody via Filepro-list wrote:
>> Jose,  I am not near a computer at the moment, but I  believe that 
>> your problem is with the backslash characters. Try forward 
>> slashes.Laura Brody Sent from my Verizon, Samsung Galaxy smartphone
>> -------- Original message --------From: Jose Lerebours via 
>> Filepro-list <filepro-list at aws-01.celestial.com> Date: 4/11/24  5:47 
>> PM  (GMT-05:00) To: filepro-list at aws-01.celestial.com Subject: Re: 
>> export ascii - default file target Mike,I have no idea if the fpmerge 
>> sub-directory ever existed (new client), I just created it to make 
>> sure that, if needed, filePro does not fail.Curious enough, if it 
>> were to fail because the sub-directory did not exist, why did the 
>> process run without error? (I put @ at the beginning of the menu 
>> command to force a pause)I did do what you suggest and still nothing 
>> is created, when I step it through debug, I see the export being 
>> executed, fields populated and "write" command is reached 
>> ...fn="c:\appl\fpmerge\jose.csv"export ascii exp = (fn) -xBesides, 
>> this process has been working just fine for years, it just decided to 
>> stop.Regards,On 4/11/24 17:36, Mike Schwartz via Filepro-list 
>> wrote:>      I always put an explicit full path in my export 
>> processing tables.  For Unix systems, something like:>>   >    If: fa 
>> eq "">>     Then: fa="/tmp/export_csv_"{p{".csv">> 8  -------   -   
>> -   -   -   -   -   -   -   -   -   -   -   - ->> -   ->>     
>> If:>>     Then: export WORD DUMP = (fa)>      Is the path being 
>> overwritten by something like this in the processing tables?>>      
>> You might want to re-write your export commands like this, so that 
>> you're not so dependent on having the fpmerge subdirectory on your 
>> system. On the other hand, I don't know how the fpmerge subdir would 
>> have disappeared, unless somebody deliberately removed it.>> Mike 
>> Schwartz>>> -----Original Message-----> From: Filepro-list 
>> <filepro-list-bounces+mschw=athenet.net at aws-01.celestial.com> On 
>> Behalf Of Jose Lerebours via Filepro-list> Sent: Thursday, April 11, 
>> 2024 2:19 PM> To: filepro <filepro-list at aws-01.celestial.com>> 
>> Subject: export ascii - default file target>> Howdy!>>> RE: filePro  
>> 6.1.00.03D6 running on WIN 2022 Standard>>> A processing which dumps 
>> data to CSV using export ascii decided to stop working.>> Per 
>> documentation, if target file is not an absolute path, the target 
>> file is then created in %PFPROG%/fpmerge, in my case, this would be 
>> c:\appl\fpmerge.>> Couple of observations, fpmerge does not exist - 
>> What happens then? Where does the file go?>>> Is there an fp variable 
>> that would override this?>>> Just for kicks, I changed the export to 
>> target c:\appl\fpmerge\jose.csv (after creating fpmerge of course), 
>> ran the process and nothing ... file is not created and yet, the 
>> export command is executed, data is assigned to columns and the write 
>> command is reached.>>> Where did the export output go?>> I searched 
>> C:\ for jose.csv and nothing came back, which to me would mean that 
>> the file was never created. What gives!?!>>> Regards,>>> --> Jose>>> 
>> _______________________________________________> Filepro-list mailing 
>> list> Filepro-list at mailman.celestial.com> 
>> Subscribe/Unsubscribe/Subscription Changes> 
>> http://mailman.celestial.com/mailman/listinfo/filepro-list>> 
>> _______________________________________________> Filepro-list mailing 
>> list> Filepro-list at mailman.celestial.com> 
>> Subscribe/Unsubscribe/Subscription Changes> 
>> http://mailman.celestial.com/mailman/listinfo/filepro-list_______________________________________________Filepro-list 
>> mailing 
>> listFilepro-list at mailman.celestial.comSubscribe/Unsubscribe/Subscription 
>> Changeshttp://mailman.celestial.com/mailman/listinfo/filepro-list
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: 
>> <http://mailman.celestial.com/pipermail/filepro-list/attachments/20240411/cd851cd8/attachment.html>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at mailman.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at mailman.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list


More information about the Filepro-list mailing list