Changing a Laptop identifier: Difference between revisions
Jump to navigation
Jump to search
Fschumacher (talk | contribs) |
TOstryzniuk (talk | contribs) |
||
Line 2: | Line 2: | ||
==Check List== | ==Check List== | ||
As of today this is only brainstorming, this list has not been tested. Trish, can you think of anything else? [[User:Ttenbergen|Ttenbergen]] 19:22, 9 December 2009 (CST) | {{discussion}} As of today this is only brainstorming, this list has not been tested. Trish, can you think of anything else? [[User:Ttenbergen|Ttenbergen]] 19:22, 9 December 2009 (CST) | ||
We’ll need to | We’ll need to |
Revision as of 19:16, 2014 January 9
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
Template:Discussion As of today this is only brainstorming, this list has not been tested. Trish, can you think of anything else? Ttenbergen 19:22, 9 December 2009 (CST)
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, incl. in output DBs