No, these are not executables. These are rules-based scripting projects that are scheduled on virtual servers to run jobs specific to each region.
The whole enchilada is under my direct control. Thank you, Mitch Lawrence Lead Applications Analyst Technical Support - NPR/Automation CHRISTUS Information Management *: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Send a "thank you <http://intranet.christushealth.org/spiritBuck/Default.asp> " to someone! ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of TIMOTHY B. FRANCE Sent: Tuesday, January 15, 2008 11:06 AM To: [email protected] Subject: RE: [Talk] Scripting shared resource Hi, I am assuming that the staff at these various locations are responsible for compiling their own executables? If so, you may be able to simply store the VB module (.bas) file out on a network share that they all have access to. This module could contain all the common sub-routines and global references for your projects. In each of their projects, they can add that shared module to their program and compile it. This way if you make a change to the shared .bas file and tell them all to recompile, your changes should be reflected in each application. However, with 9 different applications using your shared module you would certainly need to be extra careful with your changes to ensure that they are compatible with all of them. Furthermore, if for some reason the shared resource is unavailable the 9 locations would be unable to load or compile their projects properly. Thanks, Tim From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence, Mitchell Sent: Tuesday, January 15, 2008 8:48 AM To: [email protected] Subject: [Talk] Scripting shared resource Call me a total vb noob, but I've pretty much taught myself what I know. I know there has to be a way to share a resource among projects. Let me give you our basic topology: We have 9 different regions, each with their own scripting project. Each project contains some background functions and subroutines as well as global variable definitions, etc. This "resource" is the same from project to project. Is there a way I can remove the resource from each individual project and maybe store it in a central location that is instead referenced by each project? This way I only need to update a single thing instead of multiple projects when I update/add functionality to the resource. Stupid noob question I know, but help anyway, mkay? :-) Thank you, Mitch Lawrence Lead Applications Analyst Technical Support - NPR/Automation CHRISTUS Information Management *: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Send a "thank you <http://intranet.christushealth.org/spiritBuck/Default.asp> " to someone! ________________________________ CONFIDENTIALITY NOTICE: This message and any included attachments are from Salinas Valley Memorial Hospital and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Salinas Valley Memorial Healthcare System's Privacy Officer in Salinas, California, U.S.A at (+1) (831) 755-0751.
<<image002.jpg>>
