Summary

When you create a database using the /init or /initsql switch, the Init.ini file is created in the same folder as Hr.exe.

The settings that you complete on the Company Setup form (when you create a new database or secure an existing database) are saved to the Init.ini file.

• If you are using Windows Authentication, then ‘WindowsAuthenticate=1’

  If you are using SQL Authentication, then ‘WindowsAuthenticate=0’.

• If SqlAdminUsername= does not have a value, then Windows Authentication is used when you run Hr.exe with the /autocreate or /autosecure switches.
• If Database= is ‘Oracle’ or ‘Advantage’, then the /autocreate and /autosecure switches will not run. You must complete the options on the Company Setup form manually.
• When you use the Company Setup form manually, the new settings are written to the Init.ini file when you save the Company Setup form.
• Oracle and SQL Server specific settings can co-exist in the Init.ini file.

Saving settings to the Init.ini file

If you open the Company Setup form and an Init.ini file exists, then the settings are copied from the file to the form.

Settings are saved back to the Init.ini file in the following situation.

• When you start PayGlobal with the /Init or /Initsql options and use the Company Setup form to manually create or secure a database, all but one of the existing Init.ini file settings are overwritten when you exit the form. For security reasons the sysadmin password is not saved to the file; the string "\\password not saved" is saved in its place.

Settings are not saved back to the Init.ini file in the following situation.

• When you use the /autocreate or /autosecure switches, the Init.ini file is not changed. If a valid sysadmin password is defined with a line such as "SqlAdminPassword=ThisPassword", then it will remain in the file after the process is complete.

See also

Switches

Using Switches

SQL Database After Installing PayGlobal

SQL Database in PayGlobal

SQL Recommended Configuration

SQL Server Authentication Process