The databases used in PowerLine all work on the same general principles described below:
Some of the values used to label a session are refreshed from the database whenever the session is opened. For example, if a rower called "Frederick" is attached as a crew member to a session, then if his name is later changed in the database to "Freddie", then the name "Freddie" will be displayed from then on.
Auto-refresh properties are indicated with a green arrow in the database dialog.
Other properties are copied into the session and are not subsequently refreshed. For example, the rower's squad.
So, as a rower goes through their career at a club, data might be accumulated where their squad changes. When search facilities become available in future versions, you might want to search for all sessions where name="Ann Bright" AND squad="junior", or all sessions where name="Ann Bright" AND squad="senior".
Each entry is uniquely identified, even if the values are the same. Be careful: do not enter the same rower twice by mistake, as the software will be quite happy to accept two "John Smith"s.
Each PC running the PowerLine software has its own database to provide crew, boats and venues. This means that the PC doesn't need to be connected to any other computers, such as a fileserver, in order to work. Each PC can be designated either as a "master" or a "slave" with regards to its own database.
It is very important that within an organisation, only one of the PCs is designated as a "master" and all the others should be "slaves". For example, if an organisation has more than one PC as a master, then it becomes possible for several users to create database entries for the same rower.
So, decide which PC is going to be the master, and develop a strategy for periodically exporting / importing databases.
To determine the master/slave status of a PC, go to Tools→Options→Lists.
Note that if a PC is a "slave", it is still possible to enter names of rowers that aren't in the database. These will be displayed in italics, and can be updated later when the user has access to a database with that rower in.
Any changes to the database on the master can be periodically transferred to the slaves by means of an export/import facility.
.peach-lists
When importing a database, it is merged with the existing database - i.e. no entries are deleted. However, updated entries (for example, an updated rower's weight) will be refreshed.