Sage 100

Client is running SAGE 100 STD v2015PU2. Trying to add perform logic to an existing VI job to Export Column/Data Headers from the legacy PR.EMPL file. Attached is some perform logic written by Slade Hornick in 2006. Will this logic still work in the current version of VI? I tried the perform logic and I'm getting ""Error 12 - File does not exist (or already exists)"" for my .CSV file. Can one of our VI gurus look at this? THANKS

Instead of the print (1)mid... it should be print (EXP_CH) mid....

Does the options button not work for this?? This was THE reason that I learned Excel Queries. They changed the export functionality subsequently.

I am in v5.2.3 and the options button is no longer there. I was working on a similar export and manually adding header line in my file

Yikes, the legacy crap strikes again........ Looks like the headers only work in the BF modules. @MichaelMcDonald if the @LeeGraham fix doesn't work, it might be time to show them an Excel Query. Very easy to learn and do...

Thanks @LeeGraham for your input. I made the change you suggested but no Joy. Here are screen shots the error, perform logic and VI job.

The error makes me think VI is not finding your perform logic file If you temporarily remove the call to your perform logic, does it execute correctly, albeit sans headers? I do not know what your conventions are for such things, but I usually create a folder under .../Mas90 then make my perform calls something like ""../perform_logic/export_headers.pl

@RandyMarion Yes, if I remove the call to ""export_headers.pl"" the VI job runs smoothly and creates the SampVac.csv file without the headers. I moved the ""export_headers.pl"" file to a new folder ../perform_logic under ../Mas90 and I received the same error.

Well, have you verified that the file ../vi/viijob.soa exists? Can you read it with DFDM?

Yes, the file ../vi/viijob.soa does exist and here is what it looks like. Notice field 02 references LAST_NAME, however that field is NOT in my VI job.

Notice that the key to that file is OCEAEMPMASTER..... your records should start w/ OCEAVACAVAIL probably later in the file. Important thing is that the file exists and has data. Can you post a screen shot of the perform logic entry screen? Not the job listing, but the dialogue where you designate the perform logic.

Here is the setup of the perform logic on the first data field PR.EMPL:DEPARTMENT_NO

Looks good - I am beginning to wonder if the output file is open when you are attempting to write the headers... lets test this ... create a new perform logic file named ../perform_logic/export_hdr_test.pl open notepad and type the following... LET Out_file$=""C:\Temp\Tester.csv"" ERASE Out_file$,ERR=*NEXT SERIAL Out_file$ OPEN LOCK (HFN)Out_file$ LET Out_filech=LFO R$=""Test,Test2,Test3"" Print (Out_filech)R$ Close (Out_filech) if ct then exit print (exp_ch)R$ ct++ exit save the file as '../perform_logic/export_hdr_test.pl' change your script to call this logic file instead - If all works well, you should get a new file with just the test headers in it and I expect the same error we have been seeing...

@RandyMarion Followed your instructions. The ""C:\Temp\SampVac"" file was created with 0 KB and no records in it. The file type is 'FILE"" not "".CSV"" Then received the same error message. Attached are screen shots of my work and resulting messages.

How about the C:\Temp\Tester.csv - was it created? Did it have data?

No the C:\Temp\Tester.csv file was NOT created.

Your earlier error was an error 12 (missing file) on the C:\Temp\SampVac file - what is that file?

The C:\Temp\SampVac file is the output file name specified in my VI job. It is supposed to be the .CSV output file.

I wonder if your perform is executing before the output file gets created.

Sorry about falling out of the loop on this... I got distracted... probably never happens to any of you. @MichaelMcDonald since the Tester.csv file was NOT created, it appears to me that for whatever reason, your call to your perform script is not being found and that is the error 12 we are getting .... this is supported by the last error message in your screen shot where Program is blank and line number is 64999 If you are still working on this, click 'Debug' and type Print lwd It should print the path, something like 'V:\Apps\Acct\Version4\Mas90\Soa' ... whatever is appropriate for you type cwdir ""../perform_logic"" print lwd your path should be in your perform_logic folder at this point. if it is, then type call ""export_hdr_test.pl"" and check your files for headers.

@RandyMarion - Look in the sky, is that an airplane???

No ... It must be Super Schwenk!!!!

Thank you @RandyMarion with sticking with me on this. Here is the results of the Debugging of the VI program with the ""export_hdr_test"" perform logic.

This is telling us the ""export_hdr_test.pl"" script file does not exist in this folder.... I presume it does.... a permissions issue?

Yes the perform logic script file does exist in the ../perform_logic folder. However I'm wondering if I am not saving the file type correctly? I used NotePad to create the script file and then saved it as ""export_hdr_test.pl"" as a text file. Here is what file explorer is showing. Is this correct?

That would do it... can you remove the '.txt' extension? I guess, as an alternative, you could change the call in the VI job to export_hdr_test.pl.txt ... no reason that would not work. But given this info, I would probably revert back to the 'non-test' version of your perform logic, however you want to resolve the name issue.