Report Generation in Executable​s

Using LabVIEW 2012 SP1, I created a vi that opens an Excel file and puts a string of data (time stamp and a data bit).  It iterates once a second and appends the file just fine on my laptop.  My problem is that when I create an executable, the Report Generation does work.  The while loop works fine collecting the data but Excel does not open.  Can someone tell me what the trick is?
Thanks,
Brad
Solved!
Go to Solution.

Hi Brad,
I had a similar problem. The fix was to include "NIReport.llb" in the build.
The Report Generator uses dynamic calls to sub vis so they don't automatically get included as dependencies.
However, I seem to recall that errors were generated in my case which you did not mention seeing.
You might want to make sure error handling is working in your code.
steve
Help the forum when you get help. Click the "Solution?" icon on the reply that answers your
question. Give "Kudos" to replies that help.

Similar Messages

  • Report Generation Toolkit Excel Vi's do not run after creating an executable​. What am I missing?

    I have labview 8.5 and Report Generation Toolkit version 1.1.2.   My vi works fine during development. When I make an executable or an installer the excel vi's do not work. I have seen this question posted before but it has always been for earlier revisions and the answers do not seem to apply with 8.5 and 1.1.2. 

    Hello ajh,
    You will have to include Dynamic VIs in the executable you build. The following link has more information:
    http://digital.ni.com/public.nsf/allkb/C38CE3F3054​2D65B86256F0E00740DD8
    Prashant.

  • MS Office Report (Report Generation toolkit) is not executable​, Xnode broken?

    Hi, I am trying to generate an excel report, and I figured it would be easier to use the MS Office report VI, but I am getting the broken arrow saying the SubVI is not executable and that the library that defines the xnode is broken... here is a screensot attached, I already uninstall and reinstall the report generation toolkit and still the same... this is what I found on NI: "This error occurs when the library that defines the XNode you used is broken. To correct this error, reconfigure the XNode." but no idea how to reconfigure xnode
    Attachments:
    Error.png ‏67 KB

    What version of LabVIEW are you using?
    What is the nature of your Report?  What should it look like?  What kind of data should it contain?
    Can you show us some code that you've tried to use?  If so, include the code as either a Snippet or as a VI attachment (so we can plug it into our own LabVIEW installations and experiment with it).
    I generally find that the Report Generation Toolkit is a very easy way to generate Excel Workbooks.  I work primarily with LabVIEW 2012 and LabVIEW 2014.
    Bob Schor

  • Report generation toolkit and signal express user step : problem of closing reference in "Stop" event

    Hi all,
    I'm trying to make a package of Vis to easily make Excel reports with Signal Express. I'm working on LabVIEW 8.2.1.
    I'm using the report generation toolkit, so I build a .llb from my project which contains all the hierarchy of my steps, but also the hierarchy of dynamic VIs called.
    I have made some steps, like "Open Workbook", "Write Data", etc.
    My steps run well, excepts one step : "Close Workbook".
    If my "Close Workbook" step is firing on "Run" Signal Express event, I have no error, so my reference is properly closed.
    But if my "Close Workbook" step is firing on "Stop" Signal Express event, I have an error "1", from "Generate Report Objectrepository.vi".
    I feel that I'm trying to use a reference which has been killed in the "Stop" step...
    I would like to know what exactly do Signal Express on "Stop" event and why my close function does'nt run well.
    Thanks,
    Callahan

    Hi Callahan,
    SignalExpress (SE for short) does the following on the Stop event:
    1. Takes the list of parameters that SE found on your VI's connector pane, and sets the values that the user set from the "Run LabVIEW VI" configuration page, if any.
    2. Then tells the VI that SE is running the Stop event by setting the Enum found on your VI's front panel. This in turn should produce some boolean values telling your VI to execute the Stop case.
    3. The VI is then run, with those values and states.
    4. SE checks to see if any errors where returned.
    5. Since this is the Stop event, SE releases the reference to the VI which it possesses.
    Questions for you would be, is the reference to your Workbook linked to a control on your connector pane, or held in a uninitialized Shift Register. If it's held in a Shift Register, SE would not be aware of it, and would not be able to affect that reference.
    Hope that helps. Feel free to post your LLB if it doesn't.
    Phil

  • Error 7 report generation

    Good Day,
    I seem to be having a little trouble with the report generation tool.  I'm running Labview 7.1, have the MS Report Toolkit.  I have a construct that creates and formats an Excel Report.  It works fine when running it from the developement environment, but when I create an executable and run from the runtime environment, it errors right at the first stage of this sequence, at "New Report.vi".  To this VI I have an "Excel" constant tied to input "Report Type" with no other inputs.  The error that is caught is code 7 "Open VI Reference in New Report.vi->filename.vi" replacing filename with the name of my file (not to state the obvious).
    Is there a seperate runtime toolkit that needs to be installed?
    Any ideas?  Thanks a bunch.

    Hello,
    Please read the section in the User Guide for the Report Generation Toolkit on building an executable out of your VI.  There are many VIs that are called dynamically by the toolkit that must be handled in a special way (specifically, added as Dynamic VIs to your application) when you build your VI into an executable.
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Report generation fails with below error

    Hi Friends,
    This is an extarct from "ccat /var/opt/SUNWsymon/PRM/log/prm.log"
    Report generation fails for individual host but succeeds for all hosts.
    prmlog September 13, 2010 12:52:14 PM Thread-287: Begin loading files
    prmlog September 13, 2010 12:53:51 PM HandlerThread-0: Got trap: 2
    prmlog September 13, 2010 12:53:51 PM HandlerThread-2: Got trap: 2
    prmlog September 13, 2010 12:54:51 PM HandlerThread-1: Got trap: 2
    prmlog September 13, 2010 12:54:51 PM HandlerThread-2: Got trap: 2
    prmlog September 13, 2010 12:56:01 PM HandlerThread-0: Got trap: 2
    prmlog September 13, 2010 12:58:51 PM HandlerThread-0: Got trap: 2
    prmlog September 13, 2010 12:58:51 PM HandlerThread-2: Got trap: 2
    prmlog September 13, 2010 12:59:51 PM HandlerThread-1: Got trap: 2
    prmlog September 13, 2010 12:59:51 PM HandlerThread-2: Got trap: 2
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Call CrScheduledRequestBroker.
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Call CrScheduledRequestBroker.
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Call CrScheduledRequestBroker.
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Call CrScheduledRequestBroker.
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Call CrScheduledRequestBroker.
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Database Error occurs!
    prmlog September 13, 2010 1:00:00 PM Parallel:0: ERROR: relation "detail_temp_host" does not exist
    prmlog September 13, 2010 1:00:00 PM Parallel:0: SchedOP: Exception: scp-2: Report request generation failed.
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Call CrScheduledRequestBroker.
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Database Error occurs!
    prmlog September 13, 2010 1:00:00 PM Parallel:0: ERROR: relation "detail_temp_host" does not exist
    prmlog September 13, 2010 1:00:00 PM Parallel:0: SchedOP: Exception: creature-t1000-08: Report request generation failed.
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Database Error occurs!
    prmlog September 13, 2010 1:00:00 PM Parallel:0: ERROR: relation "detail_temp_host" does not exist
    prmlog September 13, 2010 1:00:00 PM Parallel:0: SchedOP: Exception: sdp-1-region2: Report request generation failed.
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Database Error occurs!
    prmlog September 13, 2010 1:00:00 PM Parallel:0: ERROR: relation "detail_temp_host" does not exist
    prmlog September 13, 2010 1:00:00 PM Parallel:0: SchedOP: Exception: psp-1-region2: Report request generation failed.
    prmlog September 13, 2010 1:00:00 PM Parallel:0: Database Error occurs!
    prmlog September 13, 2010 1:00:00 PM Parallel:0: ERROR: relation "detail_temp_host" does not exist
    prmlog September 13, 2010 1:00:00 PM Parallel:0: SchedOP: Exception: shissun1: Report request generation failed.
    prmlog September 13, 2010 1:00:05 PM Thread-294: Report successfully posted to web server.
    prmlog September 13, 2010 1:01:01 PM HandlerThread-0: Got trap: 2
    prmlog September 13, 2010 1:03:54 PM HandlerThread-0: Got trap: 2
    In /tmp directory I could see database logs directory (/tmp/SunMCDBLogFiles)
    Below is an extarct from "db-start-sql.log"
    ERROR: table "summ_temp_events" does not exist
    LOG: autovacuum: processing database "postgres"
    LOG: autovacuum: processing database "sunmc"
    LOG: autovacuum: processing database "postgres"
    LOG: autovacuum: processing database "sunmc"
    LOG: autovacuum: processing database "postgres"
    LOG: autovacuum: processing database "sunmc"
    LOG: autovacuum: processing database "postgres"
    LOG: autovacuum: processing database "sunmc"
    LOG: autovacuum: processing database "postgres"
    LOG: autovacuum: processing database "sunmc"
    LOG: autovacuum: processing database "postgres"
    LOG: autovacuum: processing database "sunmc"
    LOG: autovacuum: processing database "postgres"
    LOG: autovacuum: processing database "sunmc"
    WARNING: there is already a transaction in progress
    ERROR: relation "detail_temp_host" does not exist
    CONTEXT: SQL statement "INSERT INTO detail_temp_host (host_id) VALUES (21)"
    PL/pgSQL function "get_alarm_data_ids" line 203 at execute statement
    PL/pgSQL function "sp_get_nonperf_summary_data" line 92 at assignment
    WARNING: there is already a transaction in progress
    WARNING: there is already a transaction in progress
    ERROR: table "summ_temp_events" does not exist
    ERROR: relation "detail_temp_host" does not exist
    CONTEXT: SQL statement "INSERT INTO detail_temp_host (host_id) VALUES (26)"
    PL/pgSQL function "get_alarm_data_ids" line 203 at execute statement
    PL/pgSQL function "sp_get_nonperf_summary_data" line 92 at assignment
    ERROR: relation "detail_temp_host" does not exist
    CONTEXT: SQL statement "INSERT INTO detail_temp_host (host_id) VALUES (25)"
    PL/pgSQL function "get_alarm_data_ids" line 203 at execute statement
    PL/pgSQL function "sp_get_nonperf_summary_data" line 92 at assignment
    WARNING: there is already a transaction in progress
    ERROR: table "summ_temp_events" does not exist
    WARNING: there is already a transaction in progress
    ERROR: table "summ_temp_events" does not exist
    ERROR: relation "detail_temp_host" does not exist
    CONTEXT: SQL statement "INSERT INTO detail_temp_host (host_id) VALUES (42)"
    PL/pgSQL function "get_alarm_data_ids" line 203 at execute statement
    PL/pgSQL function "sp_get_nonperf_summary_data" line 92 at assignment
    ERROR: relation "detail_temp_host" does not exist
    CONTEXT: SQL statement "INSERT INTO detail_temp_host (host_id) VALUES (1)"
    PL/pgSQL function "get_alarm_data_ids" line 203 at execute statement
    Kindly suggest me.. This SUNMC is doing more than killing.
    Thanks
    Srini

    I just received instructions from the TMG software company to uninstall and install the PDF driver they use. This fixed the problem. Apparently upgrading to v7.01 damages the driver but reinstalling it corrects the problem.
    Thanks for the advice.
    Mike

  • Report Generation Toolkit missing VI

    LabVIEW version 8.6.1
    Report Generation Toolkit 1.13
    I have just started work on an ongoing project that others have been contributing to for some time.  (Hence the project being in older versions of LabVIEW) 
    On my PC, I am apparently missing the VI "Word Get ActiveX References.vi" 
    I do have the version 1.13 of the toolkit installed, just as every other machine that runs this code does.  But my word.llb does not contain that VI
    I have tried simply copying that VI into the .llb   The VI is then found by the application.  But is not executable due to this error:  This VI is connected with a library that does not include the VI. The VI might have been deleted from the library. Add the VI to the library again or select File»Disconnect from Library.
    I have also tried replacing my entire  C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\addons\_office\  directory with files from a PC that was working.  Again, I get the same error as above. 
    I did attempt to do a repair on my installation of the toolkit.  But as far as I can tell, this didn't do anything.
    I also tried simply reinstalling the toolkit.  But since it was already installed, it did nothing.  I am hesitant to uninstall and reinstall the toolkit for fear of breaking all of my 8.6 projects, as well as possibly my 2009 projects.  I wouldn't think it mess with my 2009 installation.  But I do know that the order in which things are installed can be critical in system with multiple versions.  I'm not sure if this applies to toolkits or not. 
    This PC also has an installation of LV 2009 SP1, and that version also has the Report Generation Toolkit installed. (although it is a different revision of the toolkit than 1.13) 
    I know that in the past, multiple versions of this toolkit were not compatible, meaning only one installed version of LabVIEW could have a working Report Generation Toolkit installed.  But I was of the understanding that this was no longer a problem.  Although it may not be a coincidence that neither of the other development boxes running this code do not have LV 2009 installed.  
    Has anyone else ever run into a similar problem and found a solution? 
    Thanks. 
    Patrick Allen
    Solved!
    Go to Solution.

    Darren wrote:
    Back before we unified the LabVIEW and toolkit version numbers (in 2009), there were cases where we didn't change the version number in the registry for one reason or another on a minor upgrade.
    Ah.  This makes sense then.  
    I just reinstalled said toolkit from said SSP DVD and although it did tell me that I was about to install 1.1.4, MAX still thinks it's 1.1.3
    ...except that now I do have the missing VI.  This is a good thingTM
    I still wonder how it ended up missing, because I'm really sure this is where I installed the toolkit from in the first place.   I'll probably never know for sure.  But that's a lot easier to take when the code is working.  
    Thanks! 
    Message Edited by pallen on 04-15-2010 04:52 PM
    Patrick Allen

  • Report Generation Toolkit Error

    I  have an application that generates multiple excel spreadsheets each containing a table and four graphs.  This has been working fine for three months but I am now getting error when generating the reports.  The source of the error is in the Excel_create_workbook as indicated on the attached picture.  I am passing in a template name for my excel reports.  The error code (-2147352571) states a type mismatch.  The file path to my template is a constant so I can't see how sometimes I get a type mismatch and other times I don't.
    Any help on this would be greatly appreciated.
    Thank you,
    AJL
    Attachments:
    create_Workbook error.JPG ‏269 KB

    Thanks for the reply, however, this VI is part of the Report Generation Toolkit so I don't want to have to modified NI's code if possible.  I did try your suggestion without saving the VI and I still got the same error. 
    Any other ideas? 
    BTW - I encountered this problem first in an executable but have since seen the error in the development code.
    Does anyone know if there is a limit to how many times you can create an excel document from LabVIEW?  I wouldn't think so but the error seems to happen if I try to create several (more then five usually) documents at a time. 
    Thanks in advance
    AJL

  • Report Generation Toolkit and Office 10 - build errors

    Using LabView 2011 and Report Generation Toolkit 2011.
    After installing Office 10, I would get build error for Excel-Print.Vi and Excel-SetCell.vi and build is then aborted.
    2011/vi.lib/addons/_office/_excelsub.llb/Excel-Print.vi.
    Says it is unable to save a vi without a block diagram.
    Uninstalled Office 10 and reinstalled Office 2003 and build went thru just fine.
    I can program using Excel 2003 and the compiled executable will work on another computer with Excel 2011 but once I install Office 10 on my LabVIEW computer I cannot build.
    Can't believe I could be the only one to experience this. Any workarounds?

    Duplicate Post

  • Report generation tool kit not printing

    I had the report generation tool kit version 1.01 for some time but never used it. I was comfortable with printing front panel vi 's.
    But now I installed it on my computer with a windows 2000 and LabView 6.02 .
    I created an application (executable) that will print (using the report
    genartion tool kit). The application works fine in my development computer
    (win 2000).
    When I installed it on another computer with a win 2000, it prints as
    expected
    but when I try to exit I get a message from windows that the application is not responding (I have to go to task manager and terminate the application).
    Both computers have word and Excell installed
    I installed the application on a third computer (win 2000), but this com
    puter does not have word or excell installed. The application does not print the
    portion of the software that uses the report generation tool kit, but it can print the front panel of vi's (set to print an end of excution).
    In all 3 computers, I have runtime engine 6.02 installed. My vi is simply
    the example vi ""Sample test report.vi"", but customized to my application, printing standard report.
    What is happening ?

    Based on what you sent, the version of Excel and Windows that are being used is a non issue since none of the code makes any calls to either one. They all refer to the older version of the report generation VIs that use NI's proprietary report generator.
    I can think of two explainations. First, you aren't using what you think you are. Second, NI retained the same VI names when they went to the Word/Excel version of the generator, and I am linked into the old version.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Report generation question

    Hi,
    With regards to BI Discoverer and BI Publisher, is a report/workbook re-generated from the underlying data source every time someone requests it or does the BI server serve up an existing copy of the report?
    The context: we will have some 600 reports being accessed by 2000 odd people. I'm trying to get some understanding of the load on the server and the performance of the report generation.
    Appreciate any help you can provide.
    Cheers,
    Nim

    BI Publisher will execute your query each time you access the report, by default BI Discoverer will do also. But BI Discoverer has the possibility to schedule reports, each time the report is accessed, the scheduled (saved) result will be shown on the report. An other possibility is to use snapshots on the DB to schedule your queries and base your reports on those snopshots.
    Michaek

  • Report Generation Performance

    Hi!
    I am currently implementing a report generation module because I have to add some features (for example: 'Additional results'). Especially I want it to be fast(!). Apart from my new implementation which is done in LabVIEW I have an implementation in C++ (cosed source) and an implementation in VB.NET (self written). All three implementation produce the same output format (one text line per measurement)
    For 500 steps to process (no deep nesting) the report body generation duration takes:
    Implementation A (c++ DLL; closed source): 240ms
    Implementation B (VB.NET; rekursive result tree traversal): 260ms
    Implementation C (LabVIEW; rekursive result tree traversal): 460ms
    Using the LV profiler it seems to me that the Teststand API is the bottleneck - the more TS property nodes I execute per step the longer the duration.
    My questions (to CTAs :-)
    - Can I speed up the report generation by using parallel loops to process the TS Property nodes; or does the TS API not support parallel (read) requests? (like a web server does)
    - Can the recursive (reentrant VIs) approach be the reason why the performance is not so good (for performance better to process the result tree in iterative manner)? Remark: no deep nesting!
    Versions used: TS2010 & LV2010
    Remark: I know that TS2012 has implemented async report generation possibility!
    w.

    Are you using the LabVIEW runtime or the development environment when running your VIs?
    -Doug

  • Report Generation Toolkit - Prints data from a previous report in Word

    I am running an executable from the "system exec.vi" created with Labview 6.1. I am using the Report Generation toolkit vi's to create a report in Word that prints simple Title with test header and then appends a Table with measurement data. The problem is the measurement data in the table is from a previously printed report. This problem only exists when I Run the Report.exe from the "System Exec.vi". If I manually start the Report.exe in Windows or open in the Windows Commandline the correct data measurement data is printed in the report table. Any suggestions are appreciated. Thank You

    Hi,
    So far I havent been able to reproduce this on my computer. Could you post your code so that I can try and reproduce this issue?
    Feroz P
    National Instruments

  • Report Generation Toolkit 1.01 and broken arrow

    Hi,
    I desperately need help because I need to build my application tomorrow morning for our production department and have trouble with the report toolkit.
    I am aware of your knowledge base entry regarding this problem. I already deinstalled and reinstalled the toolkit (version 1.0.1 for LV 6), and I checked the windows registry entries. Still, after mass-compile, the report generation toolkit VIs are not executable (broken arrow, invalid property node). I have LabVIEW 6.02, 7.0 and 7.1 on my computer and I am using the report generation toolkit version 1.0.1 with LabVIEW 6.02 and version 1.1 with LabVIEW 7.1. The application that I need to build is written in LabVIEW 6.02. What else can I do to get rid of the broken arro
    ws?
    Thanks in advance for your fast answer....
    Gabs

    Hi,
    the problem is the following: during the build error 1003 occures at ....\internal.llb\Word_New_Page.vi. Possible Reasons: LabVIEW: The VI is not executable. When I open my main VI, I see no broken arrow. When I force a mass-compile (Strg+Shift+Run button), the broken arrow appears suddenly. I can then see the following error message: Word Easy Text.vi is broken because Word Format Text.vi is broken because the Property Node Range\Style calls an invalid property. Actually, the property nodes in these VIs have NO properties and the invoke nodes NO methods.
    I know now that this is due to the fact that I need to build this application for a computer on which Word97 is running, so I installed the Report Generation Toolkit for Word97. But - on my developme
    nt computer where LabVIEW is installed Office XP is running, not Office97. If I install the Report Generation Toolkit for OfficeXP, no error occurs during the build, but the executable does not run properly on the target computer (when calling Word97).
    Question for NI: How am I supposed to build an executable using Microsoft Word Report Generation Functions if the target computer has Word97 installed but the development computer has WordXP installed???
    Please help,
    thanks,
    Gabs

  • Problem building applicatio​n using Report Generation Toolkit, LV 2011

    I'm using LabVIEW 2011 under Windows 7.
    I tried to use Application Builder to create an executable from a large body of code. One thing the application does is load VIs into a subpanel and run them.
    Application Builder created the executable and gave no error message. The built application ran except that it couldn't run any of the dynamic VIs.
    I finally succeeded in doing a screen grab on a transient dialog (about 1/10 sec. appearance). The dialog showed an attempt to load <vilib>:\Utility\NIReport.llb\NI_report.lvclass.
    In one dynamic VI I commented out the call to the only VI that uses the Report Generation Toolkit (called only from dynamic VIs, all of which call it). Sure enough, when I built the application with that change and ran it, the dynamic VI that didn't invoke the Report Generation Toolkit did successfully load into the subpanel and run.
    So, trying to prove to myself that that was the only problem, I wrote a VI that does nothing but load a VI into a subpanel and run it. User can choose one of two VIs: one that doesn't call the Report Generation Toolkit (or do much of anything), and one that does. Both VIs run fine standalone.
    The not-much-of-anything VI loaded and ran in the subpanel. The other VI didn't--the same dialog, mentioned above, popped up for 1/10 second or less. Screen grab is attached.
    When I included LVClass and NIReport.llb folders in the project (from vi.lib\Utility: Snapshot folders), and "Always Included" those folders (per a suggestion on this forum from a few years ago), the result was the same. The result was also the same when I included either one of those folders but not the other. Likewise it doesn't matter whether I add the dynamic VIs as "Always Included" or not.
    Another piece of information that may be pertinent: when adding the NIReport.llb folder, I got a message that it was impossible to add a certain VI that's part of some report-type class, because a VI of that name already existed in the project. Screenshot of that dialog is also attached.
    VIs and project file are also attached along with the two screenshots. I hardcoded VI paths, so put everything into C:\Testing if you want to see what the code does--or hack as desired, etc.
    I will be deeply grateful for any help! And I apologize in advance if there's already some exact or close-enough solution posted--but I doubt there is. I looked around.
    Thanks very much,
    mws
    Attachments:
    Test-App-Build.zip ‏336 KB

    Hi again,
    If you extract all files in the original zip attachment to a folder called C:\Testing on a Windows 7 machine running LV 2011, and then use the build script within the project file to build the application, you can run the application and see what happens. You can also play around with the build parameters, rebuild, run, and see what happens then. You can also open my VIs and see what I'm doing.
    The application lets you pick one of two dynamic VIs to run in a subpanel. One VI contains calls both to Report Generation VIs and some functions from the Advanced File Functions palette. The other VI does not.
    When you pick the first VI to load and run (the one with the Report Generation and Advanced File Functions calls), it loads into the subpanel but is not executable.
    When you pick the second VI to load and run, it does load into the subpanel and execute. So there's nothing wrong with the way I load and run a VI in the subpanel.
    In the development environment, the whole thing runs with no problems.
    Evidently the built application has problems resolving paths of something called by Report Generation VIs and by the Advanced File Functions I use.
    I've done a lot of experimenting and no luck. I've looked in forum archives, etc. etc., for possible solutions. I'm hoping there's some simple solution I've missed.
    Thanks very much for any help!

Maybe you are looking for