Maintaining data integrity

Maintaining data integrity is essential to the proper functioning of a database, and Paradox offers many ways to ensure data integrity.

In this section, you'll learn about

  defining referential integrity
  
  repairing referential integrity
  
  modifying and removing a referential integrity relationship
  
  applying validity checks
  
  applying picture string validity checks
  
  deleting validity checks
  
  creating a table lookup
  
  creating, modifying, and deleting a master password
  
  creating, modifying, and deleting auxiliary passwords
  
  entering and releasing passwords
  
  locking tables
  
For more information about data integrity, see "Reference: Maintaining data integrity."

Defining referential integrity

You can define a referential integrity relationship between tables in a database. You can also view dependent tables in a database. Viewing dependent tables allows you to verify referential integrity in a database. While data integrity ensures that the values in a table are valid, referential integrity requires a field or group of fields in a child table to refer to the key of the parent table to determine valid values.

Defining referential integrity verifies the validity of a value before it is accepted by Paradox. For example, you can define referential integrity between a parent table, Customer.db, and a child table, Orders.db, on their Customer Number fields. If you type a value in the Customer Number field of the Orders.db table, the Customer Number field of Customer.db is searched to determine if the value you entered is acceptable. If the value exists in Customer.db, the entry is accepted. If the value doesn't exist in Customer.db, the entry is rejected.

When you define or modify a referential integrity relationship, a secondary index is created for the referential integrity fields. The index is named with the name of the field, if it's a single-field definition, or the name of the referential integrity link, if it's a multiple-field definition. The index displays in the list of secondary indexes. If you delete the referential integrity relationship, you must manually delete the index. For more information about secondary indexes, see "Defining and deleting secondary indexes."

You can also define a self-referential integrity relationship. Self-referential integrity is a relationship between a field in a table and the same table's key field. For example, an Employees table may have as its primary key the Employee Number field and contain a Supervisor number field. You can define a self-referential integrity relationship in the table. Because the supervisors are also employees, by linking between the Supervisor field and Employee number primary key field.

When you define a self-referential integrity relationship, you must enable the Prohibit option in the Update rule box of the Referential Integrity dialog box. This security feature prohibits changes to records in a parent table that also exist in a child table. In other words, you cannot create a circular reference, which is a relationship in which a field refers to itself.

For more information about referential integrity, see "Referential integrity guidelines."

To define a referential integrity relationship

1	Open a child table.

2	Click Format  Restructure table.

3	Click the Referential integrity tab.

4	Click Add.

5	Type a name in the Link names list.

6	Choose a parent table from the Parent table list box.

7	Choose a parent key from the Parent's key list.

If the parent table has a composite key, add fields to match all of the parent's key fields.

8	Choose a child table field from the Child fields list.

9	From the Current table list, choose the field to which you want to add the referential integrity link, and click the right arrow.

You can also	

Specify that any change you make to the value in the parent table's key field is automatically made in the child table	In the Update rule area, enable the Cascade option.

Specify that you cannot change a value in the parent table's key field if there are records that match the value in the child table	In the Update rule area, enable the Prohibit option.

Ensure that earlier versions of Paradox, for example, Paradox for DOS, cannot access a table on which you've established referential integrity	In the Update rule area, enable the Strict R I check box.

Notes

  Always set your working directory to the folder containing the tables for which you want to establish referential integrity. If you don't, you can't define the relationship.
  
  You cannot establish referential integrity between dBASE files, Paradox 3.5 tables, or tables that do not have a key. You can use files and Structured Query Language (SQL) server tables if you need referential integrity. Please refer to your server documentation to determine if your table type supports referential integrity.
  
To define a self-referential integrity relationship

1	Open a child table.

2	Click Format  Restructure table.

3	Click the Referential integrity tab.

4	Click Add.

5	Type a name in the Link names list.

6	Choose a parent table from the Parent table list box.

7	Choose a parent key from the Parent's key list.

If the parent table has a composite key, add fields to match all of the parent's key fields.

8	Choose a child table field from the Child fields list.

9	From the Current table list, choose the field to which you want to add the referential integrity link, and click the right arrow.

To view dependent tables in a database

1	Click Format  Restructure table.

2	Click the Referential integrity tab.

3	In the Dependent tables area, view the table information.

Repairing referential integrity

There is always a risk that a table may become damaged. If a table is damaged, Paradox lets you verify the integrity of a table and repair the damage. Depending on the severity of any damage, you may not always be able to correct the problem. For this reason, you should make regular and frequent backup copies of important data.

Moreover, If the table's header is damaged, the block size and file format information may display incorrectly in the Table repair utility dialog box. If the table's block size and file format are displayed incorrectly, you need to specify the table's original block size and file format settings. If you specify settings that are different from the original settings, you will no longer be able to recover the table. For more information about changing a table's block size, see "Applying a new block size to a table."

Violations

When trying to rebuild tables, you may run into problems trying to save the repaired table. This could be because the data now violates certain validity checks or because duplicate values violate the rebuilt table's key.

If problems occur, Paradox responds as follows:

  If Paradox cannot save certain records because of data violations, it stores them in one of the auxiliary tables indicated in the Repair settings tab of the Table repair utility dialog box.
  
  The key violation table contains records that Paradox cannot save in the repaired table due to duplicate values in the table's key. When this occurs, the first occurrence is stored in the repaired table and all duplicates are stored in the key violation table.
  
  Records that violate validity checks and other data-type violations are stored in the problems table. You can view both tables by enabling the Display error tables option in the Repair settings tab of the Table repair utility dialog box.
  
To repair a table

1	Click Tools  Table repair.

2	Click Browse.

3	Choose the drive and folder where the table is stored.

If the table's header is not damaged, the table's header information displays.

4	Click Verify.

If errors are detected, you are prompted the Table repair utility prompts whether to display errors or not. If specified, the table repair errors are displayed.

5	Choose the table's original file format from the File format list box.

6	Choose the table's original block size from the Block size list box.

7	Click Rebuild.

Notes

  Make sure all windows are closed on the Paradox desktop before you attempt table repair.
  
  If the table's header is damaged, the block size and file format information may be incorrect. If the table's block size and file format are displayed incorrectly, you need to specify the table's original block size and file format settings. If you specify block size and file format settings that are different from the original settings, you will no longer be able to recover the table.
  
Tip

  If the table's header is damaged, choose Borrow to copy the structure from an undamaged back up table.
  
To change the backup table name

1	Click Tools  Table repair.

2	Click the Repair settings tab.

3	Type a new backup table name in the Backup table name box.

If the table is password-protected, type the password in the Master password box.

Note

  By default, the table repair utility supplies a backup table name of "Copy of" with the original table name appended to it.
  
Modifying and removing a referential integrity relationship

When updating a database, you may need to modify or remove a referential integrity relationship. However, if the table you are modifying is a parent table, you may be prohibited from manipulating certain data that relates to a child table. Before making changes, you need to determine what tables depend on the current table for referential integrity. You can do this by viewing the dependent table information. For more information about viewing referential integrity, see "To view dependent tables in a database."

To modify a referential integrity relationship

1	Click Format  Restructure table.

2	Click the Referential integrity tab.

3	Choose a referential integrity relationship from the Link names list.

4	In the Update rules area, enable one of the following options:

  Cascade-specifies that any change you make to the value in the key of the parent table is automatically made in the child table. This is the default rule for Paradox. To cascade an update across tables, Paradox must place a lock on the target table. If the lock is denied because another user has already placed a lock, Paradox cannot perform the cascade update.
  
  Prohibit-specifies that you cannot change a value in the parent table's key field if records match the value in the child table.
  
  Strict R I-ensures that earlier versions of Paradox, for example, Paradox for DOS, cannot access a table on which you've established referential integrity. Locks must be on all tables involved in a referential integrity relationship when you modify it.
  
5	Click Save.

Note

  For more information about applying update rules, see "Defining referential integrity."
  
To remove a referential integrity relationship

1	Open a child table.

2	Click Format  Restructure table.

3	Click the Referential integrity tab.

4	Choose a link from the Link names list.

5	Click Remove.

Applying validity checks

Paradox lets you apply validity checks to a database. Validity checks help you maintain data integrity by allowing you to place constraints on the values you can enter in a field.

You can place a required field validity check on any field type. A required field validity check specifies that you must enter a value in the field for every record in the table. When you create a required field validity check on a field, the field must contain data before the record is accepted. If you try to enter a record in a table that doesn't have a value in a required field, you receive a message that the validity check has failed, and does not let you move from the record until you enter a value in the required field.

You can also define minimum or maximum value validity checks. Minimum and maximum value validity checks allow you to define the minimum and maximum acceptable values for a field. For example, if all customer identification numbers in a table are at least five digits, defining a minimum value of 10,000 on that field, can reduce data entry errors.

You can use minimum value and maximum value validity checks for alpha, number, short, long integer, money, timestamp, time, and date field types. You cannot use a maximum validity check on an autoincrement field.

You can also apply default value validity checks, which automatically enter a value in each record of a table as soon as you create the record. For example, if most of a company's customers are located in the United States, you can define USA as the default value for the Country field in the customer information table. Whenever you insert a new record, USA would automatically appear in the Country field.

For more information about validity checks, see "Validity checks."

To create a required field validity check

1	Click Format  Restructure table.

2	Click the Field roster tab.

3	Choose a field from the list.

4	Enable the Req'd check box.

To define a minimum or maximum value validity check

1	Click Format  Restructure table.

2	Click the Field roster tab.

3	Choose a field from the list.

4	Click any of the following columns, and type a value:

  Minimum - the values entered in the field must be greater than or equal to the minimum specified
  
  Maximum - the values entered in the field must be less than or equal to the maximum specified
  
Notes

  When you define a numeric minimum or maximum, you must use the number format currently selected in the Windows Control Panel. During data entry, however, you can use any format.
  
  You cannot use minimum-value and maximum-value validity checks on BCE (Before the common era) dates; instead, you can define a picture validity check. For more information about picture validity checks, see "Applying picture string validity checks."
  
To create a default value validity check

1	Click Format  Restructure table.

2	Click the Field roster tab.

3	Choose a field from the list.

4	Type a value in the Default value box.

Note

  You can override the default value by clicking in a field and typing a new value. You can also delete the default value and leave the field blank, unless it also has a required field validity check.
  
Tip

  You can use the TODAY operator to define today's date as the default value in a date field. The NOW operator can be used as a default for time and time-stamp fields.
  
Applying picture string validity checks

Picture string validity checks allow you to restrict the type of information you can enter by specifying a character string as a template for the values that can be entered in the field. Paradox provides a selection of standard picture strings that you can specify for data such as phone numbers and words that must be capitalized.

If you don't want to use any of the sample picture string validity checks, you can create a custom picture validity check either by editing one of the samples or by coding one of your own. You can also rename custom picture validity checks.

If you specify a picture validity check for a table that contains data, Paradox does not reformat existing data to match the picture, nor does Paradox validate existing data to check that it matches. However, if you choose to add or change a validity check, you have the option of enforcing the new validity check on existing data. If you choose to enforce the new validity check on existing data and any data that does not comply with it, Paradox places the non compliant data in the Keyviol.db table. However, Paradox does not do this for picture validity checks.

For more information about picture string validity checks, see "Picture string validity checks."

To specify a standard picture string validity check

1	Click Format  Restructure table.

2	Click the Field roster tab.

3	Choose a field from the list.

4	Click the Picture field and choose a sample from the list box.

To create a custom picture string validity check

1	Click Format  Restructure table.

2	In the Field roster tab, choose a field from the list.

3	Click the Picture field and choose Picture assistant from the list box.

4	Choose the default field type from the Type list box.

5	Click Add.

6	Type a name in the Pictures box.

7	Type the syntax in the Picture code box.

The indicator button to the right of the Picture code box will inform you if your code is correct or incorrect.

8	Type a value in the Sample value box.

If you want to verify if the sample value is correct, click Test.

9	Type a description in the Description box.

You can also	

Refer to a list of codes and descriptions for creating a new picture code.	Click Code syntax.

Delete all the custom pictures you create.	Click Restore default pictures.

Tip

  You can create a picture that can be used with any field type by choosing Any type from the Type list box.
  
To rename a custom picture string validity check

1	Click Format  Restructure table.

2	Click the Field roster tab.

3	Click Picture assist.

4	Double-click a picture name in the Pictures list.

5	Type a new picture name.

Deleting validity checks

If you decide that a field for which you created a validity check should no longer be restricted by this check, you can delete the validity check. You can delete default value, minimum value, maximum value, required field, picture, and picture string validity checks.

To delete a default value validity check

1	Click FormatRestructure table.

2	Click the Field roster tab.

3	Click the Default column.

4	Right-click, and click Delete.

To delete a minimum or maximum validity check

1	Click FormatRestructure table.

2	Click the Field roster tab.

3	Click any of the following columns:

  Min
  
  Max
  
4	Right-click, and click Delete.

To delete a required field validity check

1	Click Format  Restructure table.

2	Click the Field roster tab.

3	Click a field, and disable the Req'd check box.

To delete a picture validity check

1	Click Format  Restructure table.

2	Click the Field roster tab.

3	Click the picture field defined as a validity check, and choose None from the Picture list box.

To delete a picture string validity check

1	Click FormatRestructure table.

2	Click the Field roster tab.

3	Click Picture assist.

4	Choose the picture name from the Pictures list.

5	Click Delete.

Creating a table lookup

You can create and use a lookup table for a field to specify that the field can contain only values that are in the first field of the lookup table. When you create a table lookup; you can also specify whether the person entering data in the field can view the lookup table and copy values from it, or whether they are required to match the lookup table's values without seeing them. The following diagram demonstrates a table lookup.

A table lookup lets you enter data that already exists in one table to another table. To establish a more powerful tie between two tables, you can define a referential integrity relationship. While a table lookup ensures that data is copied or added accurately from one table to another, referential integrity ensures that the ties between like data in separate tables cannot be broken. For more information about referential integrity, see "Defining referential integrity."

Follow these rules when setting up a table lookup:

  The field of valid entries must be the first field in the lookup table.
  
  The field that you are defining as a table lookup must have the same field type and size as the first field of the lookup table.
  
  For best performance, the first field should be the primary key for the lookup table.
  
You can use a table lookup across different directories. When you define a table lookup on a table from a different directory, Paradox stores the full path to the table.

To create a table lookup

1	Click Format  Restructure table.

2	Click the Table lookup tab.

3	Choose a field from the Fields (Current table) list.

4	Click the right arrow.

5	Choose a lookup table from the Lookup tables list box.

6	In the Lookup type area, enable one of the following options:

  Current fields - specifies that the current field gets its value from the lookup table, even if the current table and the lookup table have other fields in common.
  
  Applicable fields - specifies that all fields that correspond to fields in the lookup table get their value from the lookup table. Corresponding fields must have identical field names and compatible field types in both tables. Only the first field of the lookup table is used as part of the validity check.
  
7	In the Lookup rights area, enable one of the following options:

  Fill only - informs you when a value is invalid when editing a table, but does not allow you to view the lookup table
  
  Fill and view - allows you to display and select values from the lookup table while editing a table
  
Notes

  The Fill only option is useful when you want to keep values in the lookup table secure.
  
  When a Paradox table is created in version 5 or earlier, it can't create a lookup if the table name or directory path has more than eight characters. If you want to apply a table lookup, you must upgrade the table to version 7 by using the table repair utility or by defining a version 7 feature for the table when restructuring, such as a descending index.
  
Tip

  You can search for a lookup table by clicking (...) next to the Lookup tables list box.
  
To use a table lookup

1	Click View  Edit data.

2	Click Record  Insert.

3	Choose a field that has an assigned lookup.

4	Press CTRL + SPACEBAR.

5	In the Lookup table, click the field that contains the value you need.

6	Click OK.

Tip

  You can use a table that you create from scratch that holds all pertinent values for the field as the lookup table. Remember that the first column in the table must contain the values for the other table's lookup field. After you create the table with the pertinent values, you can follow the steps above to use it as the table lookup.
  
Creating, modifying, and deleting a master password

Creating a master password controls access to a table. You must input the correct password before Paradox opens the table. Typically, one person, such as a database administrator, has access to a master password. A group of users who need to perform different tasks in the table have different auxiliary passwords that provide different levels of access. For more information about auxiliary passwords, see "Creating, modifying, and deleting auxiliary passwords."

You can also change a master password. In addition, if a password-protected table contains information that no longer needs to be restricted, Paradox lets you delete the master password.

To create a master password

1	Click Format  Restructure table.

2	Click the Passwords tab.

3	Click Define.

4	Type a password in the Password box.

5	Retype the password again in the Verify password box.

Notes

  A password can be 15 characters long including spaces.
  
  Passwords are case-sensitive.
  
To change a master password

1	Open the table that contains the master password.

2	Type the master password in the Password for box.

3	Click Format  Restructure table.

4	Click the Passwords tab.

5	Click Modify.

6	Type the new password in the Password box.

7	Retype the new password in the Verify password box.

8	Click OK.

9	Click Save.

You can also	

Add a master password to the Paradox passwords list. This lets you to access any table that recognizes the master password during the current Paradox session without having to type it.	Click Add.

Delete a master password from the password list	Click Remove.

Deletes all master passwords from the passwords list	Click Remove all.

Notes

  A password can be 15 characters long including spaces.
  
  Passwords are case-sensitive.
  
To delete a master password

1	Open a table that contains a master password.

2	Type the master password in the Password box.

3	Click Format  Restructure table.

4	Click the Passwords tab.

5	Click the master password in the Passwords list.

6	Click Delete.

7	Click Yes.

8	Click Save.

Creating, modifying, and deleting auxiliary passwords

Creating auxiliary passwords lets you apply read and write permission to a table as a whole. Auxiliary passwords provide different levels of access privileges for different users in a group. Once you define the permission for the whole table, you can further limit user access to the table by assigning permission to individual fields. For example, you can give users read permission to the whole table but then hide fields in the table that contain sensitive information you don't want general users to see or edit. To create auxiliary passwords, you must first create a master password for the table. For information about creating a master password, see "Creating, modifying, and deleting a master password."

Once you've created an auxiliary password, you can modify or delete the password depending on your needs and changes to the tables.

To create an auxiliary password

1	Open a table that contains a master password.

2	Type the master password in the Password box.

3	Click Format  Restructure table.

4	Click the Passwords tab.

5	Click Add.

6	Type the auxiliary password in the Auxiliary passwords list.

7	In the Table rights area, enable any of the following check boxes:

  All (highest access) - gives a user rights to any function in the table, including the ability to restructure, delete and to change or delete passwords.
  
  Insert and delete-gives a user the right to insert, delete, or empty records, but not to delete or restructure the table.
  
  Data entry-gives a user the right to edit data and insert new records, but not to delete or empty records or restructure the table.
  
  Update-gives a user the right to view the table and change non-key fields, but not to insert or delete records or change key fields.
  
  Read only-gives a user the right to view the table only.
  
8	Click Save.

Tip

  When creating an auxiliary password, you can assign permission to specific fields in the table from the Field rights area by choosing a field and choosing Full, Read only or None from the Access list box.
  
To modify an auxiliary password

1	Open a table that contains an auxiliary password.

2	Type the master password in the Password box.

3	Click Format  Restructure table.

4	Click the Passwords tab.

5	Choose an auxiliary password from the Auxiliary passwords list.

6	In the Table rights area, enable any of the following check boxes:

  All (highest access) - gives a user rights to any function in the table, including the ability to restructure, delete and to change or delete passwords.
  
  Insert and delete-gives a user the right to insert, delete, or empty records, but not to delete or restructure the table.
  
  Data entry-gives a user the right to edit data and insert new records, but not to delete or empty records or restructure the table.
  
  Update-gives a user the right to view the table and change non-key fields, but not to insert or delete records or change key fields.
  
  Read only-gives a user the right to view the table only.
  
7	Click Save.

Tip

  When creating an auxiliary password, you can assign permission to specific fields in the table from the Field rights area by choosing a field and choosing Full, Read only or None from the Access list box.
  
To delete an auxiliary password

1	Open a table that contains an auxiliary password.

2	Type the master password in the Password box.

3	Click Format  Restructure table.

4	Click the Passwords tab.

5	Choose an auxiliary password from the Auxiliary passwords list.

6	Click Remove.

7	Click Save.

Entering and releasing passwords

Whenever you open a password-protected table, you are prompted to enter the password before you open the table. If you open a table once, supply the correct password, and then close the table, Paradox allows you to reopen the table without reentering the password. However, once you quit Paradox, all passwords are released. Releasing a password means that the password is reactivated and you must enter the password before accessing the table. For more information on creating a password, see "Creating, modifying, and deleting a master password." For security purposes, you can also release a password without quitting Paradox.

If you created the same password for several tables, Paradox allows you to enter the password to all applicable tables at the same time.

To enter a password for several tables

1	Click Tools  Security  Passwords.

2	Type a password in the Enter password box.

3	Click Add.

To release a password

1	Click Tools  Security  Passwords.

2	Type a password in the Enter password box.

3	Click Remove.

Locking tables

You can lock tables to prevent others from opening or editing table records, which is useful in a multi-user environment. You can display the table locks placed, the type of lock and who has placed each lock. For example, when you edit a value, you see the message "Record is now locked" on the status bar. As soon as you move off a field, Paradox automatically unlocks the record.

You can also choose various locks, such as a lock that locks an entire table, locks that provide varying levels of protection, and locks that must be explicitly placed and removed.

This table summarizes users' rights under different levels of locks. The lock levels are arranged in order of increasing strength.

Lock level and your rights	Others rights and locks others can place

None, None	All, All

Open, Read (write if no other read lock is in place)	Read/Write, All except exclusive if no record lock in place

Read, Read (write if no other read lock is in place)	Read, Open/Read

Write, Read/Write	Read, Open

Exclusive, All	None, None

Image	Others sharing the table can't modify its properties

To lock a table

1	Click Tools  Security  Set locks.

2	Choose the drive and folder where the table is stored.

3	Enable any of the following options:

  Read lock-prevents others from writing to the table and from placing a lock on the table that prevents you from reading it. Your right to read the table is guaranteed.
  
  Write lock-allows you to read and write to the tables, and prevents others from writing to the table
  
  Exclusive lock-prevents others from reading or writing to the table
  
  No lock-removes a lock from the table
  
  Open lock-prevents others from placing an exclusive lock on the table
  
To display table locks

1	Click Tools  Security  Display locks.

2	Choose the drive and folder where the table is stored.

3	Click Open.

Column	Shows

Type	What type of lock is on the table

User Name	The name of the user who placed the lock

Net Session	The session number of the user who placed the lock

Our Session	1 means the lock is yours; 0 means another user placed the lock

Record Number	Which record is locked and whether the lock is a record lock, not a table lock

Reference: Maintaining data integrity

The following topic contains reference information pertaining to data integrity issues.

Referential integrity guidelines

Follow these guidelines when you establish referential integrity relationships.

  You can establish referential integrity relationships only between like fields that contain matching values.
  
For example, you can establish referential integrity relationships between the sample customer.db and orders.db tables on their Customer Number field. The field names do not matter as long as the field types and sizes are identical.

  You can establish referential integrity only between tables in the same directory.
  
  You can establish referential integrity between an autoincrement field and a Large Integer field.
  
  The referential integrity parent table must be keyed.
  
  If you define referential integrity on a table that already contains data, existing values may not match a value in the parent's key field. When this happens, Paradox places existing records that do not match into the temporary keyviol.db table in your private directory.
  
Paradox validity checks

Paradox provides five kinds of validity checks.

Validity check	Meaning

Minimum	The values entered in this field must be equal to or greater than the minimum you specify here.

Maximum	The values entered in this field must be less than or equal to the maximum you specify here.

Default	The value you specify here will be entered in this field automatically if no other value is entered.

Picture	The character string that you specify here acts as a template for the values that can be entered in this field.

Required field	Every record in the table must have a value in this field.

When you save a table, Paradox saves validity checks in a file with the table's name and the .val file extension.

Picture string validity checks

A picture validity check acts as a template that formats the value you enter in a field. For example, if you specify the picture (###)###-####, which is a common template for North American phone numbers, and enter the value 4085551234, Paradox formats the value into (408)555-1234. You can use the following characters in a picture validity check string.



Character	Represents

#	Numeric digit

?	Any letter (uppercase or lowercase)

&	Any letter (converts to uppercase)

~	Any letter (converts to lowercase)

@	Any character

!	Any character (converts to uppercase)

;	Interpret the next character as a literal, not as a special picture-string character

*	Any number of repeats of the following character

[abc]	An optional part of the string that can be left out; type nothing, or type abc

{a,b,c}	Optional characters a, b, or c

*where n is a number that means Repeat the next symbol exactly n times therefore typing *3#-*4# indicates you want to enter three numbers, a dash, and then four numbers, which is the picture of a standard North American telephone number. You can also use a semicolon to override this syntax; for example, typing '*;3' means any number of threes.

The following are some examples of picture validity checks.



Picture	Description

&#&#&#	Canadian postal code; for example, K1S 2A2

*!	Any entry; all letters will be in uppercase

{Yes,No}	Either "Yes" or "No"

 




