A form properties file saves all the customizable properties about a record edit window, such as the "Customer Edit" window, or a data list window, including form sizes, column widths, sort criterion and default search options, etc.
If you find any form not showing correctly, Invoice Manager for Excel (namely Uniform Invoice Software) provides an easy way to let you reset all the properties to defaults.
Note that the "Reset form properties" command deletes all the customized user-interface settings, such as the column widths and default search options of the search bar. However this does not affect the data stored in the database.
For each database you connect to,creates a corresponding form properties file automatically, with the same file name as the database file and an extension " ".
For example, if you connect to a database MyInvoice.mdb, a form properties file "MyInvoice.fs" is created automatically. By default, form properties files are stored in the following folder on Windows XP:
<System Driver>\Documents and Settings\<User Name>\Application Data\uniformsoft.com\Invoice Manager for Excel (namely Uniform Invoice Software)\
Note: Thefolder is hidden by default. To make it visible: In Windows Explorer, click the menu -> ; Go to the tab; Choose the option; click .
On Windows Vista and Windows 7 / Windows 8/ Windows 10, by default the form properties files are stored in the following folder:
<System Driver>\Users\<User Name>\AppData\Roaming\uniformsoft.com\Invoice Manager for Excel (namely Uniform Invoice Software)\
Note: Thefolder is hidden by default. To make it visible: In Windows Explorer, click -> ; Go to the tab; choose the option; click .
For this reason, you don't need to deal with the form properties file in most cases. If a form properties file is corrupt for some reasons, such as a power failure when you are closing a data list window, simply use the "Reset form properties" command, or delete the form properties file to have the program create a new one for you.
There will be no problems if all the databases you are using have different names, but what if two databases have the same name, or what if you want to move the form properties file from the default folder (the installation folder of) to another folder where you have read-write privilege?
This is why the Form Properties Map File was introduced. As the name implies, the map file forcesto load a specified form properties file for a given database, instead of the default form properties file that has the same file name as the database file and an " " extension.
Generally you don't need a map file, unless you have two or more database files that have the same name, or you don't have read-write privilege in the installation folder of.
In the first situation, you can use map file to instructto load a specified form properties file when connecting to a database. For example, if you have two database file that are both named as , but stored in the different folders, say and , you can put the following lines in the map file:
Database= C:\MyCompany1\MyCompany.mdb Properties=C:\MyCompany1\Company1.fs Database=C:\MyCompany2\MyCompany.mdb Properties=C:\MyCompany2\Company2.fs
In the second situation, you need to be able to create and write to the form properties file, sinceshould be able to write to the properties file whenever you modify a form property, such as its width or height, or the size of the columns.
For example, you installed the program into a folder in a network driver, where you don't have the privilege to create or update file. In this case, you can use the map file to instruct to load the form properties file from a folder in which you have read-write privilege, instead of the installation folder of :
A form properties map file is a plain text file that has a name of. The file must be stored in the installation folder of . You can create this file using any text editor, including .
For each database you will connect to, create an entry which consists of two lines. The first line starts with the keyword "" followed by the full qualified database file path and name; the second line starts with the keyword " " followed by the full qualified properties file path and name.
Below is an example of thefile:
Database=c:\MyInvoice\Company1.mdb Properties=c:\MyInvoice\Company1.fs Database=e:\INV2\Sample.mdb Properties=E:\INV2\Sam.fs
In this example, when the invoice template connects to thedatabase, uses as the properties file. If the invoice template connects to , it uses as the form properties file.