Changing a Laptop identifier: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) |
||
Line 23: | Line 23: | ||
* local laptop settings | * local laptop settings | ||
** set [[A_Info]]/[[Settings (CCMBD.mdb)]] to new location | ** set [[A_Info]]/[[Settings (CCMBD.mdb)]] to new location | ||
** test sending | ** test [[sending]] to make sure new location and directory name don't break anything | ||
* CFE | * CFE |
Revision as of 16:44, 2018 September 19
The Laptop location 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
- confirm with the statistician whether there is impact
- CCMDB.mdb which feeds CFE tables
- possibly table S Tmp
- s_dispo table
- table s_locations_allowed_collection table
- 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.
- Category:Site/Location check might take care of 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
- create/update Data to local.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?
Transitioning
If a location is no longer available on a laptop records with that location can't be set to "complete". So, if we transition from one location to a new one, we need to get collectors to change the locations for all existing records to the new one, and change the number to using the new number series. Another option might be to keep old location available, at risk of manual mistakes and continuing to use the old location, and of location-numberPool mix-ups. Either way, needs to be planned.
Related articles
Related articles: |