RE: [Talk] "Dynamic" filenames - Suggestions?

[Rodgers Chase]

I just usually use “*.txt”. Comma delimited files are nice, but sometimes description fields (or any other fields) may also have commas and mess up any data imports into Excel, Access, etc. Quotes, when the data might have commas, will keep Excel and Access from importing the data incorrectly.  If there are quotes, it imports the entire field together, without incorrectly breaking it apart. I’ve always been partial to “tab” delimited data.  That way, if you have commas in your original data, it will still import correctly. The extension doesn’t have to be *.tab, it can be *.txt.  File extension doesn’t matter. Thanks, Chase Rodgers Financial Reporting Manager Medical Center of Plano (214-473-7490 /[EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thom C. Blackwell Sent: Tuesday, January 24, 2006 07:10 AM To: Talk@BOSTONWORKSTATION.COM Subject: [Talk] "Dynamic" filenames - Suggestions?   Greetings, Hope this message finds all doing well. A quick question for the group…   We’re working on a new <Top Secret> J product feature and need some feedback regarding file naming conventions.   I know many of you have scripts that cause a system to run and then download some sort of report. Typically part of the script is to name the report file. Some scripts I’ve seen use a static name, others the name is generated by the script and is therefore different each time the script runs.   For those of you generating file names “on the fly” in your script – what sort of naming conventions are you using – or would like to use? Using the system date somehow? Using something else?   And what file formats / extensions are you using?   Any feedback you can provide will be greatly appreciated!   Regards, Thom   Thom C. Blackwell Product Manager Boston Software Systems Visit us at HIMSS Booth 1850 www.BostonWorkStation.com 866 653-5105 - ex 807 [EMAIL PROTECTED]