CSV or Comma Separated Value files - These files contain the data for each database column separated by a comma. The first line of the file is a mapping line which allows you to map the data to Readerware database column names.
TAB Delimited Files - These are similar to CSV files except that the data is separated by the tab character. Again the first line of the file is a mapping line which allows you to map the data to Readerware database column names.
"BRWR_FNAME","BRWR_LNAME","BRWR_ID"The problem is how does Readerware know what order the columns are in? The mapping line is key to importing data into Readerware. The first row of the file is the mapping line and it identifies which Readerware database columns the data should be imported into. This is a common technique used with CSV and TAB delimited files, your file may already have a mapping line as the first line of the file. or it may just contain the data. You need to open the file using a text editor like Notepad or TextEdit. Look at the first line. If there is a mapping line, you need to change the column names to match the Readerware column names. If it is not there, you need to add the line.
"John","Doe","10023"
Readerware Column Names | |
Column Name | Contents |
---|---|
BRWR_FNAME | Borrower first name |
BRWR_LNAME | Borrower last name |
BRWR_ID | Borrower ID |
BRWR_STATUS | Borrower status, Active, Inactive or Banned |
BRWR_EMAIL | E-Mail address |
BRWR_PHONE1 | Phone number |
BRWR_PHONE2 | Phone number |
BRWR_FAX | Fax number |
BRWR_ORG | Organization |
BRWR_ADDR1 | Address line 1 |
BRWR_ADDR2 | Address line 2 |
BRWR_CITY | City |
BRWR_STATE | State, province, territory etc. |
BRWR_ZIP | Zip or postal code |
Automatic detection - In most cases Readerware can determine the encoding by examining the file. This is the default selection and you should normally use this and only specify an explicit encoding if there is a problem.In general you should use automatic detection. If Readerware is unable to determine the encoding used, you can select the correct encoding from the list.
ANSI - This is your system encoding and is the default. It will work for databases that contain the system language.
Unicode (little endian) - Unicode is a double byte character set and can handle virtually any language and any combination of languages. Little endian is used on Intel systems.
Unicode (big endian) - Unicode is a double byte character set and can handle virtually any language and any combination of languages. Big endian is used on other systems like PPC.
UTF-8 - UTF-8 is a variable width encoding and can handle all characters in the Unicode character set. It has become popular as you don't need to worry about endianness.