It is important to stress that all events are linked to a members database. The players' names and other related information are found on that database. Normally you would not use more than one database. This might be needed where more than one club is using the same computer to score events. Another situation could be where a special event is being scored on the computer.
It would be very unusual to change the members' database being used for an event.
Where you choose to use more than one database it is important to understand the internal structure of the members database.
All rows in a members database have a unique reference number. This is important where (and only where) some or all of the players on file do not have a national number.
The ASE Scorer normally keeps track of players in the events using the national number. Typically this is the same way bridge clubs keep of their members. So long as the members of the club all have national numbers, changing the database used for an event has no impact.
Where the players do not have national numbers the ASE Scorer uses the members' database internal reference numbers to locate such players. Therefore, if the masterfile is changed, then the new masterfile will have different reference numbers from those in the original masterfile. Such players will be referring to different players or will be missing from the file.
This means events that have been previously created and scored using one masterfile will have different names using a new masterfile.
Note the options [File]/[Produce CSV file] and [Imports]/[Version 8 CSV file] are compatible. The internal references are maintained and unchanged where the import option is used with a new and empty masterfile.