Changing a Laptop identifier: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m m
Line 2: Line 2:


==Check List==
==Check List==
'''This is untested,there may well be more to this!'''
* confirm with the [[statistician]] whether there is impact
 
* [[CCMDB.mdb]] which feeds [[CFE]] tables
** table [[S Locations]]
** table ''[[s_locations_allowed_collection]]''
** for medicine, table ''[[s_tmp_er_wait_r_locations]]''
** possibly table ''[[s_varOptions]]'' if new [[Var 1 - Admit-from Ward]]/[[Var 2 - Discharge-to Ward]] are required
** possibly table '''[[s_tmp]]'''
** find/search through all VBA modules for the new name, the current name, possible equivalent unit name
** make sure that the location name is not relevant to any of the queries; I can't think of a nice way to automate this.
 
* batch files
** set [[News and backup]]/[[Batstart.bat]] to new location
** test n&b to make sure new location and directory name don't break anything
** update [[locs.bat]]
 
* directory structures
** add a folder regional_server\programs\<new name> (rather than re-name, to facilitate backing out if we can’t finish)
** add a folder regional server\data\<new name>
 
* local laptop settings
** set [[A_Info]]/[[Settings (CCMBD.mdb)]] to new location
** test sending  to make sure new location and directory name don't break anything
 
* CFE
** '''anything? '''


We’ll need to
* confirm with the [[statistician]] whether there is impact
*Add a folder regional_server\programs\<new name> (rather than re-name, to facilitate backing out if we can’t finish)
*Add a folder regional server\data\<new name>
*Add a folder regional server\output\<hosp>\<new name>
*Update the information in [[S Locations]]
*Consider if any tmp studies will be affected
*Ensure that there is no code specifically mentioning the current location of the laptop (e.g. the long stay warning)
** find/search through all VBA modules for the current name
** address all finds; note: just changing the find to the new name may lead to undesired results, make sure the change is the right thing to do.
** make sure that the location name is not mentioned in any of the queries; I can't think of a nice way to automate this.
**Find out if any queries explicitly use the old location, decide whether to replace with new one; I can't think of an easy way to do this, likely have to do it the hard way
*change the location in [[Settings.mdb]]
*get local collector to send, and make sure all arrived


[[Category: laptop]]
[[Category: laptop]]
[[Category: IT Instructions]]
[[Category: IT Instructions]]
[[Category: Site and Location]]
[[Category: Site and Location]]

Revision as of 10:43, 2015 May 4

The location of a laptop (set in Settings.mdb) has a bearing on various cross checks, output locations etc. Therefore, to change it all the related things need to be accounted for.

Check List

  • directory structures
    • add a folder regional_server\programs\<new name> (rather than re-name, to facilitate backing out if we can’t finish)
    • add a folder regional server\data\<new name>
  • local laptop settings
  • CFE
    • anything?