Maintain Databases

Away/Home Talks

Importing Data

This allows you to import home talk and away talk data into the database.  The information is held in the same data file that will be imported.  If you read on, you will see detailed instructions about this.

Importing allows you to insert many records into the database in one go. This would save you manually adding new entries into the database one by one. The file to be imported needs to be in a certain format, referred to as a tab-delimited file.

Exhaustive validation of data to be imported is not carried out by the program. It assumes that you, as the user, have ensured the data to be imported is valid and that it is indeed appropriate to do so. You import data entirely at your own risk and I accept no responsibility for any loss of data caused.

When you press the Import button, it displays a dialogue for you to select the data file to import. You are informed if the file could not be opened for whatever reason.

Please note that if you are importing a previously exported file, you must delete the header rows of text from the file first (this is the first line in the text file naming what each item represents).  Failure to remove this text line will generate errors during importing.

You are then asked if you want to delete the current table contents. Please be aware of any other tables which might refer to this current table. If you delete such entries, you are effectively removing this relationship. It won't actually delete the table until it has established that it is safe to add the import data. If you choose not to delete the table, or the program can't delete the table for some reason, it will append the data instead (if the data being imported is valid to append).

As each entry is read in from the file, it checks to see if the talk number is valid. If it isn't, the import process will be terminated. If it was unable to read in the entry information from the file, you will again be informed and importing will stop.  When importing home talk data, it will not allow duplicate dates.  As for away talks, there must be a valid home talk date to match (either in the database or the import data),  otherwise an error message will be displayed.

When the import data has been validated, it proceeds to import the records into the database.

As mentioned at the top of this help topic, the import file must be tab-delimited, which means that each line of text in the file represents an entry to add into the database. The information on each line is separated using TAB characters. The order of the information on each line must match the following template:

Home Talk entries:

Talk Number [TAB] Chairman [TAB] Interpreter [TAB] Reader [TAB] Conductor [TAB] Hospitality [TAB] Congregation [TAB] Speaker [TAB] Date [TAB] Miscellaneous [CR]

Away Talk entries:

Talk Number [TAB] Brother [TAB] Congregation [TAB] Date [CR]

where [TAB] represents the tab character and [CR] represents a carriage return.

You need a special line of text to separate the two tables in the text file. Home talk entries must be listed first. If you only want to import away talk entries, then this line of text must still precede the list of away talk entries in the file. This is the line of text:

***** END OF HOME TALKS *****

Each item of information must be entered correctly. Here is a breakdown:

Talk Number This should be an integer number (the public talk with this number should already exist in the database).
Interpreter This is a standard character string.
Chairman This is a standard character string.
Brother This is a standard character string.
Reader This is a standard character string.
Conductor This is a standard character string.
Hospitality This is a standard character string.
Congregation This is a standard character string.
Speaker This is a standard character string.
Date This should follow the following format: YYYY-MM-DD
Miscellaneous This is a standard character string.

If the above items are kept in mind when importing, you should have no problems.

All lines of text starting with a semi-colon ; are treated as comments and are ignored.