Greetings, There is not a way to override the new configuration(BDS) file from being created - and if the FileName and FileTime is the same - then the created BDS from the first run, would indeed be used (to retain the Status information). If the FileTime is different, then a "fresh file" would be created (Status information removed). You could use a Kill command: Kill "C:\myCreatedBDS.BDS" BEFORE your open command if you are running the same file / save Filetime. Regards, Thom
Thom C. Blackwell Product Manager Boston Software Systems (866) 653-5105 ex 807 www.bossoft.com Sign up for my weekly webinar! 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. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bennett, Brian Sent: Friday, January 11, 2008 11:14 AM To: '[email protected]' Subject: [Talk] Runtime Configuration Files Is it possible to override the creation or saving of the runtime configuration file? I notice in the help section, that even if you designate a configuration file when opening a data station file a run time file is also created. Not a problem, but when the same file is opened again, the runtime file is loaded as well and negates the config file specified at the time of opening. I'm not totally sure, but doesn't this hinder the ability to use data station entries as conditions in rules? Is the only option to manually remove the runtime config file? Thanks. Brian Bennett Affinity Health Systems PBS\Clinic Billing (920)628-9055 [EMAIL PROTECTED]
