Richard - I followed this suggestion of your's: 'Added the extension to the name?'
And, it seems it DID fix the problem. What I noticed - was that the system was trying to generate that Excel file in a Folder called "PayMapToday" - while the file it was trying to generate was also called "PayMapToday". I think a User made a mistake - and created that folder inadvertently. Then, the Putfile function gets 'confused' between the XLS file name and the Folder name. So, by using the Extension - it stopped the confusion - and now properly displays the File name in the Save As! So - all is well that Ends well. -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Richard Kaye Sent: Wednesday, May 27, 2015 11:43 AM To: [email protected] Subject: RE: A Quirk w/the PUTFILE Function? To be honest I never had a 100% clear picture in my head of what your oddity is. :-) If you can reproduce this issue in the dev environment and can test a logical condition then ASSERTS are way better than SET STEP ON, imo. For example, let's say you are expecting to be in a certain location before your PUTFILE runs. You can do something like this: <untested pseudo-code> ASSERT CURDIR()=[my expected location] MESSAGE [You're not where you think you are! Debug now?] PUTFILE(...) This will give you the option to invoke the debugger and then evaluate the environment as it is at that point in time. Have you tried concatenating the full path with the file name as the 2nd PUTFILE param instead of just the file name? Added the extension to the name? Use a memvar for the output file name instead of a literal string? Have you investigated using Windows APIs instead of PUTFILE? -- rk -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Kurt Wendt Sent: Wednesday, May 27, 2015 11:25 AM To: [email protected] Subject: RE: A Quirk w/the PUTFILE Function? I never used an ASSERT before. So - I looked at the online help - and I don't think it will help in this situation. Also - I don't think the TRY would work either - since the TRY is used to handle trapping of an error. And, although a strange behavior occurs with regards to my issue - it doesn't actually throw an error of any kind... -K- -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Richard Kaye Sent: Wednesday, May 27, 2015 11:15 AM To: [email protected] Subject: RE: A Quirk w/the PUTFILE Function? ASSERTs and TRY..CATCH may help you hunt this down. -- rk [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/80838f1ca795b14ea1af48659f35166f1b9...@drexch02.corp.globetax.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
