Greetings, Looking at the BDS file directly is one way. For a more human readable approach, you also can do this using a DataStation Report but you need to do a bit of setup first.
If your d.Open command looks like: D.open file.xls,ftExcel - This to me indicates your script reads the same excel file every time (or well the spreadsheet data may change, but the file name and column headings do not) What you will want to do is first, open your file in the DataStation like you did when you first built your script. Then select Configure a Report. The instructions are pretty self explanatory on that screen. After you have done that. Anytime that file is open by the DataStation you can select the Generate Report and you'd see a report "appear" - may take some time if it's a large file BTW. Be careful when you do that though because that will build a D.Report command - which is how you have a report generated automatically by the script. So the best thing to do (if you are using Rules) is first before you reopen the file (if you need to) is to click on the label in the Rules Tree that says Steps. So you won't get any commands generated. I cannot stress enough the important clicking the label Steps. You DO NOT want rogue commands in your script! Now if your D.Open command looks like: D.open MyFile & ".xls", ftExcel, "C:\myBDS.bds" - this indicates your script reads from a spreadsheet who's file name may be changing (probably the script itself "creates" this file name in some way. You will need to retrofit the report configuration into "c:\myBDS.bds" - do this by opening your file in the DataStation - but this time use set the Configuration File field using the browse button to select "c:\myBDS.bds". Configure your report as described earlier. After this is done, the next time your script runs. Use the procedure described above for the file that the script processed during that particular run. Regards, Thom Thom C. Blackwell Product Manager Boston Software Systems (866) 653-5105 ex 807 www.bossoft.com <http://www.bossoft.com/> Visit us at MUSE Internationl Booth 629 Sign up for my weekly webinar! <http://www.bostonworkstation.com/customer_center/special_events.aspx> LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash. From: [email protected] [mailto:[email protected]] Sent: Thursday, April 23, 2009 1:45 PM To: Talk Subject: [talkbws] RE: Scripting Recommendations Thom The spreadsheet is the D("Status") field. If I'm understanding you correctly, I would need to look in the .bds file, not the .xls to see where the processing stopped. Is that correct? In a "Runtime License" mode, the user would be able to work outside of the script with nothing additional? Amy Sobczak St. Michael's Hospital, 900 Illinois Avenue, Stevens Point WI 54481 | phone: 715.342.7629 | email: [email protected] ________________________________ From: [email protected] [mailto:[email protected]] Sent: Thursday, April 23, 2009 11:11 AM To: [email protected] Subject: [talkbws] RE: Scripting Recommendations Greetings, Well... technically the Status field - at least the D("Status") that we provide (not one that is in a file) is updated in real time. It is stored in the .BDS file. And if this is what you are using - I can show you how to see this info using DataStation Reports. Or does your spreadsheet actually have a field named Status and you selected the "update Excel" option when you configured reading the file? If that's the case, I have a trick as well to update these "on the fly" too. Saw the comment about excel "displaying" You don't need to worry about that when you're using the DataStation. To turn a script over there is nothing you need to "add". First thing that's needed is to install a (most likely) runtime license on the PC itself. Since you're reading from files - be sure the way the script reads the file matches up with where the file will reside! The Runtime does have a UI to play the scripts - or you can create an icon to run it. Since I didn't see who you are - I don't get the email address anymore when folks post so folks please add a signature or something! I don't have a way to reach out and chat about your specifics. Regards, Thom Thom C. Blackwell Product Manager Boston Software Systems (866) 653-5105 ex 807 www.bossoft.com <http://www.bossoft.com/> Visit us at MUSE Internationl Booth 629 Sign up for my weekly webinar! <http://www.bostonworkstation.com/customer_center/special_events.aspx> LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash. From: [email protected] [mailto:[email protected]] Sent: Thursday, April 23, 2009 11:53 AM To: Talk Subject: [talkbws] Scripting Recommendations I am new to BWS scripting and have written a few scripts that remain in IT. I am in the process of turning a script over to non-IT end-users and am wondering if some things are possible 1. This script reads an excel file and executes a process in Meditech. When each record is processed, it updates the status field as "Processed". My problem - if the script bombs half way thru the spreadsheet the excel spreadsheet doesn't update that status fields until the "Wrap Up" step in the script so I don't know which records are processed and which need to be processed. How can I have the script update the status field "realtime" so if something happens we can see what row is causing the issue? 2. When I turn the script over to the end-users, is there something that needs to be included in the script that will allow them to continue working on non-script related tasks? When I run the script, I watch the process to make sure all errors, issues are resolved. I don't want to turn this over to the end-users and tell them that their computer cannot be used during the execution of the script. I'd would prefer them to be able to continue on with their daily tasks. Is there a recommendation for turning over scripts to end-users? Any help you are able to provide is appreciated. Thanks! ________________________________ CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipient(s) named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please notify the sender at the electronic mail address noted above and destroy all copies of this communication and any attachments. Thank you for your cooperation. --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk .aspx --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk .aspx ________________________________ CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipient(s) named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please notify the sender at the electronic mail address noted above and destroy all copies of this communication and any attachments. Thank you for your cooperation. --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk .aspx --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk.aspx
