I am running LabVIEW 14 on a Windows 7 box here in my office. I develop and test here, then build an EXE and deploy that EXE to a remote Win7 PC via TeamViewer. It has worked for a number of intermediate VIs that do not involve writing to disk. The latest EXE works exactly like I want it to work on my local box, but when I deploy it to the remote box...
...it seems to have trouble creating the output file that is generated by the "Write Spreadsheet File" subVI. To emphasize: it works on my local PC.
I have assumed the problem is a permissions issue, so after trying a number of different paths, both hard-coded into the VI as a PATH variable and generated dynamically by a PATH dialog box, I have hard-coded the path as
C:\Users\Public\
and have changed the permissions on that folder to the most "permissive" possible.
Now, the VI successfully generates the next daughter folder, e. g.,
C:\Users\Public\20140902144410\
in which the folder name is simply the YYYYMMDDhhmmss of the current time stamp at VI execution. Every time the VI runs, I want it to create this unique folder and put the multiple spreadsheet files in it. THAT FOLDER APPEARS, but no files are created inside it. While troubleshooting, I created an indicator to show the initial output path that is created during the startup phase of the VI, and it returns the correct value as shown in the attached JPG screen shot. Again, the folder successfully appears in the right place in the directory structure.
Am I wrong to suppose that the likely problem here is a permissions issue?
Thanks for any help...and solutions!
Brent Auvermann
Professor of Agricultural Engineering, TAMU