Waters Empower Software Build 1154 Toolkit Service Pack Release Notes

Transcription

1 Waters Empower Software Build 1154 Toolkit Service Pack Release Notes These release notes are intended as supplemental information and should be used in conjunction with the Empower Software Release Notes. All release note information for Empower also pertains to this Service Pack. In order to maintain consistency, Waters recommends that you install the same level of service packs on all of your workstations or, in an Enterprise environment, on all of your clients, LAC/E 32 modules, and servers. Installation of the Toolkit Service Pack also includes and requires all changes noted in the following Empower follow-on projects: Service Packs A, B, C, D, ApexTrack, Light Scattering, Instrument Support Service Pack and Instrument Support 2 Service Pack. PCS numbers are defined throughout this document. These numbers are internal numbers used to track the status of problems associated with the Empower software. Features Implemented with the Toolkit Service Pack Empower Toolkit Service Pack fixes several defects in Empower Toolkit. These defects are listed on page 3 of this document. Additionally, this service pack provides newly added features to Empower Toolkit, which are listed on page 6 of this document. Installation Notes Waters recommends that you backup all of your Empower projects (and library information) and/or Empower database before installing any Empower service pack. The installation of any service pack is documented in the checksum.txt file on your Empower computer. This file indicates which service pack(s) is installed and verifies the integrity of disk files by comparing their current CRC s and sizes with original values recorded during installation of the base software and any installed service pack. This file is created when you perform a Verify Files routine by choosing Start > Programs > Empower > Verify Files. The checksum.txt file automatically displays at the end of this routine. You can display this file by choosing Start > Programs > Empower > File Verification Results. The installed service packs are listed in the Help About dialog in the Installed Service Packs list. The Verify Files utility, the Advanced Qualification Technology (AQT), and the Installation Log also indicate what service packs are installed. Installation The service pack is contained in a self-extracting zip file. Extracting will launch the installation and you will be presented with a dialog box giving an option to install (choosing Yes) or not install (choosing No) this service pack. More than one service pack is contained on this CD. The following service packs will be installed along with the Empower Toolkit service pack: Service Pack A Service Pack B Service Pack C Apex Track Light Scattering Support Service Pack D Empower Instrument Support Empower Instrument Support 2 Part # , Rev A Waters is a trademark of Waters Corporation. All other trademarks are the sole property of their respective owners. Copyright 2004 Waters Corporation

2 When the service packs included in this release are installed, only the files required by these service packs are installed in the appropriate order. The registry is updated to reflect the correct list of installed service packs. No Oracle or system files are affected. To install the Toolkit Service Pack: 1. From the Windows menu, choose Start > Run. 2. Do one of the following: Enter X:\ Empower Updates exe (excluding quotation marks) in the Run dialog (where X is the drive letter of your CD-ROM. OR Browse to the appropriate CD drive; double click the Empower Updates exe file. 1. Follow all prompts. Uninstall You must backup all of your Empower projects (and library information) and/or Empower database before uninstalling any service pack. To remove the Toolkit service pack from your system, run the service pack installation program. You will be presented with a dialog box giving an option to reinstall (choosing Yes) or uninstall (choosing No) the Toolkit service pack. When the Toolkit service pack is uninstalled, a full reload of the Empower executable files is made to ensure the validity of the installation and the registry is updated to reflect this change. No Oracle or system files are affected. After an uninstall has been performed, full qualification of Empower should be performed in a GXP regulated environment. Program Files Affected The following files are updated when the Toolkit Service Pack is installed: Empower\Bin\Mil0.dll Empower\Bin\Mil3.dll Empower\Bin\MilTK.dll Empower\Bin\MilTKEx1.dll Empower\Bin\Quickset.exe Empower\Bin\Quickstart.exe Empower\Bin\Verifyopt.exe Empower\Bin\OpenAccess.exe Empower\Bin\ProcSrvr.exe Note: The Verify Files utility is designed to show whether the current installation is valid and will not show differences between the current and previous installations (before and after the service pack application). While these specific files are replaced during the service pack installation, it is expected that Verify files will not show those files as changed. If your laboratory standards require that you can demonstrate that the files listed above have been updated, you can compare the output of the Verify Files utility done after the installation of the service pack(s), with the output of the Verify Files utility done before the service packs(s) were installed. Problems Fixed with Empower Toolkit Service Pack 2

3 Fix defect PCS #28591 (Toolkit Memory Leak) Fixes a Memory leak surrounding the ResultViewer object. When calling and releasing the ResultViewer and associated objects, system memory will be appropriately released. Fix defect PCS #28480 (Quick Start Interface) Allow full functionality of the Quick Start Interface via Toolkit. When a user logs in to Empower via the Toolkit Project object Login method, Toolkit should check what allowed interfaces the user has and open the appropriate interface based on their Default User Interface setting. This also caused problems when fetching result id information based on the mtkselected option of the ResultViewer. Through further investigation of this defect, changes were also made to the Project Object LaunchMilApp Method. Detail changes on this fix: A fourth optional parameter was added to the Project Object s LaunchMilApp method, mtkuserinterface ui. The Method now is: LaunchMilApp(mtkMillenniumApp milapp, mtkconnectoptions connectoption, VARIANT varargs, mtkuserinterface ui), Where mtkuserinterface is an enumeration of (mtkdefault = 0, mtkquickstart = 1, mtkpro = 2, mtkopenaccess = 3, mtkweb = 4). This allows the ToolKit user to specify which interface they wish to launch, with some caveats. - If the optional argument isn t supplied, Toolkit will look at the supplied User s default interface and use that (and if that selection is set to use the system default, it will use the System Policy Default UI setting). - If the optional argument supplied is mtkdefault, Toolkit will launch via the System Policy Default UI setting. - If the optional argument supplied is mtkpro or mtkquickstart, Toolkit will check to see if the given user has the appropriate privileges for that, if not it will return an error. - In the case where mtkopenaccess or mtkweb is specified or defaulted to, an error will be returned as these are not supported interfaces via ToolKit. Note: There are timing issues with launching applications ( i.e. Project, Review) with the QuickStart interface, whereas the behavior is not consistent when launching with a particular view, i.e. Launching Project/QuickStart/Channels may display Find Data/Samplesets view. In these cases the user will have to make an additional selection manually to the appropriate tab view. Fix defect PCS #28474 (Apex Track) When Apex Track is enabled there are different Integration Parameters and Events in Empower. However, the Visual Basic object browser will only show fields corresponding to Traditional Integration. In Empower there are two sets of integration parameters, Apex Track and Traditional. When editing a processing method with Apex Track integration parameters the ToolKit will load the Apex Track fields for the IntegrationParameters object, when editing a processing method with Traditional integration the ToolKit will load those fields. This is seamless to the ToolKit user, you will simply see the appropriate fields based on which kind of processing method you are editing. Fix defect PCS #29096 (LaunchMillApp Method) The Project object LaunchMillApp method has an mtkcreateifnecessary connect option. If this option is used, the application is only started if it is not already running based on the Login parameters. Currently Toolkit will ignore the mtkcreateifnecessary option and create a new application window. 3

4 Using this mtkcreateifnecessary connect option will now operate correctly and not create a new application window. Fix defect PCS #29563 (Enforce Unique User Account Names) If attempting to create a user through the Toolkit User object and the system policy Enforce Unique User Account Names is set, the Toolkit will not display the appropriate message box stating User name x already in use. The system creates the account by appending a number 1 to the end of the duplicate name attempting to be created. Toolkit will now return an error if that user name is already in use. Toolkit will also check to ensure the account name meet s the minimum length requirements, if not, an error will be returned. Fix defect PCS #29565 (Project Object Login) If attempting to login via the Toolkit Project object, the Toolkit will not display the appropriate errors for the different login conditions. The following list details these conditions and the revised Toolkit action: 1. A new user account is created via Empower or Toolkit and Password Required was enabled. When attempting to log into Empower via Toolkit for the first time using this new account, the Toolkit did not display a message box stating Your Password has Expired. Toolkit will now display an error that the password has expired. The user must log in through the Empower Software to correct this. By design, the Toolkit can not create or modify passwords. This must be done through the Empower Software. 2. If the System Policy Enforce Minimum Password Length of: x characters is enabled and a user logs into Empower via Toolkit with a password not meeting this policy, Toolkit did not display a message box stating, The password for this account no longer meets current system policies for length. Toolkit will now display this message box and direct the user to change their password by logging in through Empower Software. By design, the Toolkit can not create or modify passwords. This must be done through the Empower Software. 3. If the System Policy Passwords Expire every: x days is enabled and a user logs into Empower via Toolkit with a password not meeting this policy, Toolkit did not display a message box stating, Your password will expire in x day(s). Toolkit will now display an error when the password has expired. The user must log in through the Empower Software to correct this. By design, the Toolkit can not create or modify passwords. This must be done through the Empower Software. Fix defect PCS #29594 (Result and Sample Information Changes) The New Project Policies tab for Empower System Polices has a "Result Changes" and "Sample Information Changes" check box under 'Default Full Audit Trail Settings' - 'Full Audit Trail Support'. When these are checked and Result or Sample Information changes are made via the Toolkit the user is not prompted to enter a reason for these changes as they are in the base application. If the Sample Information Changes System Policies is enabled, sample information changes made via Toolkit will now prompt the user to enter a reason for these changes. Toolkit programmers may automate this response in code using the Toolkit RevisionComment Property. Setting this Property will automatically enter the comment and not prompt the user for an entry. Note: Results cannot be changed via Toolkit therefore checking this has no effect on Toolkit. Fix defect PCS #29675 (Copy From Non-FAT to FAT Projects) When the System Policy, "Don t allow user to copy from non-fat projects into FAT projects" is checked, any Toolkit object that allows the user to copy between projects should be checked. Currently if this is enabled Toolkit users can still copy between non-fat and FAT projects. 4

5 When an inappropriate copy is now performed, Toolkit displays the message Can t copy from non-fat projects into FAT projects. Fix defect PCS #28711 (User Object) When creating a user via the Toolkit User object, you are restricted from starting the name with a numeric character. This is allowed within the base Empower application and should function the same within Toolkit. Users now created via the Toolkit User object are not restricted from starting the name with a numeric character. Fix defect PCS #30959 (KPRIME) When the System Suitability and GPC/LS (Light Scattering) options are enabled, both options contain a KPRIME field which causes a conflict in Toolkit. Due to the conflict, Toolkit does not return any KPRIME value. However, Toolkit works fine when only one of the options is enabled. The following list details the Peak field name mappings from Empower Software to Toolkit when the GPC/LS Option is enabled: - Empower Software Toolkit K(LS) Alpha(LS) Linear K(LS) Linear Alpha(LS) Mz(LS) Mz+1(LS) KLS AlphaLS LinearKLS LinearAlphaLS MzLS MzPlus1LS Note: There was no change made to the System Suitability mappings. Fix defect PCS #31170 (Data Acquisition Privileges) User accounts that do not have the Data Acquisition Privilege are able to perform data acquisition via a Toolkit application. With the Data Acquisition Privilege enabled, User accounts will not be able to perform data acquisition (i.e. run a single injection or sample set). Fix defect PCS #31242 (Copy Preferences) When you create a new Project through Empower, You can 'copy preferences' from another project. In Toolkit, there is no property to set for copying preferences. A new Boolean Property was added to the DBProject Object called CopyPreferences, and works the same as other DBProject Copy Methods such as CopyMethods, CopyViewFilters, etc. If CopyPreferences is set to True when creating a new project using the DBProject.Copy method, Toolkit will copy the existing options and preferences from the specified source project. Note: Existing options includes the following options built into the base Empower Software: Photo Diode Array, Mass Spectrometry and CE/CIA. New Features Added with Empower Toolkit Service Pack 5

6 PCS #28590 (Summarize Function) The Empower feature Summarize Custom Fields was not implemented via Toolkit. The Constant information is as follows: Identifier Value Used By mtksummarizecustom 39 Static Fields Type Custom Menu Item Argument Toolkit Custom Menu Items were created to provide users access to any application from within the Empower Software. The last parameter is a space-delimited list of command line arguments that are passed to the executable upon startup. These arguments are placed in the registry key for the custom menu item and would expand during program runtime. As an example %p expands to the current project name, expand meaning the current project name is added to the command line during runtime in place of the %p parameter. A new Custom Menu command line parameter of %a has been created. This would expand to the current acquisition server node when launched from Run Samples (Pro Interface) or Quick Start Interface. Com Instrument XML Interface A new object InstSetupCom will be added to InstSetups family. This object is unlike other InstSetup objects in that it will handle multiple instrument setups defined as COM instruments. COM instruments that save their instrument setup data as XML will be handled by this new object. The InstSetupCOM object will be a general purpose object designed to expose Empower instrument setups that are stored as XML (i.e. new COM instruments) to Toolkit users. Unlike existing InstSetup objects that are tailored to the individual instrument, (InstSetup600, InstSetup2790, etc.) this object will handle multiple types of instruments via a simple set of commands. The InstSetupCOM object will allow a Toolkit user to fetch and store the XML blob that contains the instrument method parameters for a particular COM instrument. The XML data will be fetched and stored as a single entity. The Toolkit Programmer is responsible for validating any and all modifications made to the XML prior to setting the XML property. There will be little or NO error checking and/or range validation done on the XML being sent down to the database. The Toolkit Programmer should parse through the XML schema capturing each field s minimum and maximum parameter, which can then be validated in your code prior to modification. The XML schema (whose extension is.xsd) for each COM instrument is supplied by Waters and can be found in the appropriate directory for that instrument under the Empower/Instruments/HTML subdirectory. The InstSetupCOM object derives from the base class InstSetup in order to allow polymorphic handling of all types of InstSetups in any Instrument Method. The InstSetupCom object has all the properties and methods of the InstSetup object and the following additional property. NOTE: The Type property will always return mtkcom for any and all COM based instruments. XML() as String Set: Sets the XML method data for the instrument Get: Returns the XML method data for the instrument Default: N/A IEEE Instrument Setup for Waters 486, 410, 2410, 2414, 2790/5 and Agilent 5890/7673, 5890S/7673S, 6890 GC s - InstSetup486 6

7 The InstSetup486 encapsulates the setup information for the Waters Corporation 486 instrument. The InstSetup486 object has all the properties and methods as described by InstSetup. It's dynamic fields are specific to the 486 instrument setup. It also has the following additional properties. EventLines as EventLine486S Set: Sets the value for this event lines collection. Get: Returns the current collection of event lines. Default: An EventLine486S collection containing the event line information for this InstSetup InstSetup410 The InstSetup410 encapsulates the setup information for the 410 instrument. The InstSetup410 object has all the properties and methods as described by InstSetup. It's dynamic fields are specific to the 410 instrument setup. Note: The 2410 and 2414 show up as a 410 instrument in Empower. - InstSetup2790 The InstSetup2790 encapsulates the setup information for the 2790/5 instrument. The InstSetup2790 object has all the properties and methods as described by InstSetup. It's dynamic fields are specific to the 2790 instrument setup. It also has the following additional properties. EventLines as EventLine2790S Set: Sets the value for this event lines collection. Get: Returns the current collection of event lines. Default: An EventLine2790S collection containing the event line information for this InstSetup2790. GradientLines as GradientLines Set: Sets the value for this gradient lines collection. Get: Returns the current collection of gradient lines. Default: A GradientLines collection containing the gradient line information for this InstSetup InstSetup5890 The InstSetup5890 encapsulates the setup information for the HP 5890 and 5890S series instruments. The InstSetup5890 object has all the properties and methods as described by InstSetup. It's dynamic fields are specific to the 5890 and 5890S instrument setups. It also has the following additional properties and sub objects. RampLines as RampLine5890S Set: Sets the value for this ramp lines collection. Get: Returns the current collection of ramp lines. Default: An RampLine5890S collection containing the ramp line information for this InstSetup5890. Channels as Channel5890S Get: Returns the current collection of channels. Default: A Channel5890S collection containing the channels information for this InstSetup5890. RampLine5890S Dynamic collection of RampLine5890 objects. Used by InstSetup5890 object to manipulate the ramp lines of a HP 5890 series instrument setup. There are no additional properties or methods. RampLine5890 7

8 The RampLine5890 object encapsulates a HP 5890 series ramp line object. It contains the fields specific to a HP 5890 series ramp line. Fields() as Fields Default: A Fields collection containing all the RampLine5890 fields, FieldType is mtkeventline. fields in the Fields property can be used. All RampLine5890 dynamic properties can use both Set() and Get() functions. After a property is set, it s get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be a formatted string using the Empower width and precision specifications. Set(FieldName, Value) Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default value - False. property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives Channel5890S Dynamic collection of Channel5890 objects. Used by InstSetup5890 object to manipulate the channels of a HP 5890 series instrument setup. There are no additional properties or methods. Channel5890 The Channel5890 object encapsulates a HP 5890 series channel object. It contains the fields specific to a HP 5890 series channel. Fields() as Fields Default: A Fields collection containing all the Channel5890 fields, FieldType is mtkischannel. fields in the Fields property can be used. All Channel5890 dynamic properties can use both Set() and Get() functions. After a property is set, it s get will reflect the current setting; yet, it will only be officially stored in the 8

9 database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be a formatted string using the Empower width and precision specifications. Set(FieldName, Value) Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default - False. property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives - InstSetup6890 The InstSetup6890 encapsulates the setup information for the HP 6890 series instrument. The InstSetup6890 object has all the properties and methods as described by InstSetup. It's dynamic fields are specific to the 6890 instrument setup. It also has the following additional properties. FrontDetector as HP6890Detector Get: Returns the current FrontDetector object. Default: A HP6890Detector object containing the front detector information for this InstSetup6890. BackDetector as HP6890Detector Get: Returns the current BackDetector object. Default: An HP6890Detector object containing the back detector information for this InstSetup6890. FrontInjector as HPInjector Get: Returns the current FrontInjector object. Default: An HPInjector object containing the front Injector information for this InstSetup6890. BackInjector as HPInjector Get: Returns the current BackInjector object. Default: An HPInjector object containing the back Injector information for this InstSetup6890. FrontInlet as HP6890Inlet Get: Returns the current FrontInlet object. Default: An HP6890Inlet object containing the front Inlet information for this InstSetup6890. BackInlet as HP6890Inlet Get: Returns the current BackInlet object. 9

10 Default: An HP6890Inlet object containing the back Inlet information for this InstSetup6890. Column1 as HP6890Column Get: Returns the current Column1 object. Default: An HP6890Column object containing the column information for this InstSetup6890. Column2 as HP6890Column Get: Returns the current Column2 object. Default: An HP6890Column object containing the column information for this InstSetup6890. RampLines as RampLine6890S Set: Sets the value for this ramp lines collection. Get: Returns the current collection of ramp lines. Default: An RampLine6890S collection containing the ramp line information for this InstSetup6890. Channels as Channel6890S Get: Returns the current collection of channels. Default: A Channel6890S collection containing the channels information for this InstSetup6890. RampLine6890S Dynamic collection of RampLine6890 objects. Used by InstSetup6890 object to manipulate the ramp lines of a HP 6890 series instrument setup. There are no additional properties or methods. RampLine6890 The RampLine6890 object encapsulates a HP 6890 series ramp line object. It contains the fields specific to a HP 6890 series ramp line. Fields() as Fields Default: A Fields collection containing all the RampLine6890 fields, FieldType is mtkeventline. fields in the Fields property can be used. All RampLine6890 dynamic properties can use both Set() and Get() functions. After a property is set, it s get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be a formatted string using the Empower width and precision specifications. Set(FieldName, Value) 10

11 Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved.. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default value - False. property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives Channel6890S Dynamic collection of Channel6890 objects. Used by InstSetup6890 object to manipulate the channels of a HP 6890 series instrument setup. There are no additional properties or methods. Channel 6890 The Channel6890 object encapsulates a HP 6890 series channel object. It contains the fields specific to a HP 6890 series channel. Fields() as Fields Default: A Fields collection containing all the Channel6890 fields, FieldType is mtkischannel. fields in the Fields property can be used. All Channel6890 dynamic properties can use both Set() and Get() functions. After a property is set, it s get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be formatted string using the Empower width and precision specifications. Set(FieldName, Value) Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved.. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default value - False. property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives HP6890Inlet The HP6890Inlet object encapsulates a HP 6890 series inlet object. It contains the fields specific to a HP 6890 series inlet. 11

12 Fields() as Fields Default: A Fields collection containing all the HP6890Inlet fields, FieldType is mtkhp6890inlet. RampLines as RampLine6890S Set: Sets the value for this ramp lines collection. Get: Returns the current collection of ramp lines. Default: An RampLine6890S collection containing the ramp line information for this HP6890Inlet. fields in the Fields property can be used. All HP6890Inlet dynamic properties can use both Set() and Get() functions. After a property is set, it s get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be a formatted string using the Empower width and precision specifications. Set(FieldName, Value) Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved.. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default value - False. property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives HP6890Column The HP6890Column object encapsulates a HP 6890 series column object. It contains the fields specific to a HP 6890 series column. Fields() as Fields Default: A Fields collection containing all the HP6890Column fields, FieldType is mtkhp6890column. RampLines as RampLine6890S Set: Sets the value for this ramp lines collection. Get: Returns the current collection of ramp lines. Default: An RampLine6890S collection containing the ramp line information for this HP6890Column. fields in the Fields property can be used. All HP6890Column dynamic properties can use both Set() and Get() functions. 12

13 After a property is set, it s get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be a formatted string using the Empower width and precision specifications. Set(FieldName, Value) Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default value - False. property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives HP6890Detector The HP6890Detector object encapsulates a HP 6890 series detector object. It contains the fields specific to a HP 6890 series detector. Fields() as Fields Default: A Fields collection containing all the HP6890Detector fields, FieldType is mtkhp6890detector. fields in the Fields property can be used. All HP6890Detector dynamic properties can use both Set() and Get() functions. After a property is set, it s get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be a formatted string using the Empower width and precision specifications. Set(FieldName, Value) Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set( xxx, val). The Set gives Get(FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved.. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default value - False. 13

14 property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get( xxx ). The Get gives HP6890Injector The HPInjector object encapsulates a HP series injector object. It contains the fields specific to a HP series injector. Fields() as Fields Default: A Fields collection containing all the HPInjector fields, FieldType is mtkhpinjector. fields in the Fields property can be used. All HPInjector dynamic properties can use both Set() and Get() functions. After a property is set, it s get will reflect the current setting; yet, it will only be officially stored in the database at the InstrumentMethod Store(). If the optional FormatData parameter is set to non-zero, then the returned data will be a formatted string using the Empower width and precision specifications. Set (FieldName, Value) Action: This provides another way to set a dynamic property. Using object.xxx = val in Visual Basic is equivalent to doing object.set ( xxx, val). The Set gives Get (FieldName, [FormatData]) as Variant FieldName as string: Contains name of the dynamic field whose value is to be retrieved. FormatData as BOOLEAN: Set True if data is to be returned as a Empower formatted string. Default value - False. property. Using val = object.xxx in Visual Basic is equivalent to doing val = object.get ( xxx ). The Get gives - InstSetup7673 The InstSetup7673 encapsulates the setup information for the HP 7673 instrument. The InstSetup7673 object has all the properties and methods as described by InstSetup. It's dynamic fields are specific to the HP 7673 instrument setup. - InstSetup7673S The InstSetup7673S encapsulates the setup information for the HP 7673S series instrument. The InstSetup7673S object has all the properties and methods as described by InstSetup. It's dynamic fields are specific to the HP 7673S instrument setup. It also has the following additional properties (HPInjector object described in InstSetup6890 section above). InjectorA as HPInjector 14

15 Get: Returns the current FrontInjector object. Default: An HPInjector object containing the InjectorA information for this InstSetup7673 InjectorB as HPInjector Get: Returns the current BackInjector object. Default: An HPInjector object containing the InjectorB information for this InstSetup7673 Plate Layout Position Property A new property has been added to the PlateLayout object that allows specification of the Plate Layout Position so that Plate Layouts can be added to the PlateLayouts collection. PlateLayoutPosition () as Integer Set: Sets the PlateLayoutPosition for the current PlateLayout object. Get: Returns the current PlateLayoutPosition for the PlateLayout object. Default: N/A ConnectionsAQT Product Information It is recommended that the Empower Toolkit Service Pack is not installed, if either or both of the following two ConnectionsAQT products are installed: ConnectionsAQT for Waters Alliance Systems v2.10 and ConnectionsAQT for Waters SAT/IN Module Qualification v2.00, this is due to a fixed defect PCS#29594 (detailed above)-which results in continuous manual intervention by the user in order to proceed. It is recommended that the Empower Toolkit service pack be installed only on ConnectionsAQT for Empower Software, ConnectionsAQT for Waters Alliance Systems v2.20 and ConnectionsAQT for Waters SAT/IN Module Qualification v2.10. Validation Information If this is an initial installation or an uninstall has been performed, Waters recommends full qualification of Empower be performed in a GXP regulated environment. When the service packs included in this release are installed, only the files required by these service packs are installed in the appropriate order. The registry is updated to reflect the correct list of installed service packs. No Oracle or system files are affected. After the installation you should re-qualify your system according to your laboratory standards. Waters recommends that customers run the Verify Files utility or the ConnectionsAQT for Empower IQ and review the resulting file (File Verification Results) for an entry that indicates which service packs were installed. The installation log also indicates which service packs have been installed and states: Installed Empower Toolkit Service Pack on mm-dd-yyyy hh:mm:ss". Note: The information displayed in the File Verification Results (IQ) always reflects the last installation. You must refer to the Installation Log to see the complete history. 15