MGR requires an mgr-sql configuration file that contains the server and database information in order to connect to the server. After the database has been set up, you will need to create your mgr-sql file.
The main login screen contains a hidden area below the the database that houses configuration options. To access this, you will hold the ctrl key on your keyboard and click the AgWare logo on the login screen. You’ll see two tabs – Access Database and SQL Database. On the SQL Database tab, click on the Create SQL Server Link button.
The create SQL server link button will pop up a new window where you will enter the server and database name and choose your type of authentication. If you cannot use “Trusted Connection”, please contact AgWare. You will most likely need to also check the “Trust Server Certificate” option. Please see Microsoft’s documentation for more information on that. Once the details are entered, you will click the “Test Database” button to test the connection to the database. You will hopefully see a message that the connection was successfully established. If you don’t, double check your server name and database name.
Then, use the “Save As…” button to save your mgr-sql file to the same folder as your current Access Database (if you are a previous Access user, otherwise save this on a file share that each user will have access to). Do not put this in a different location or you will lose your custom reports, transaction attachments, and logo. The network share where these items are stored will continue to be used, and the location of the share will be determined by the physical location of the mgr-sql file.
After the mgr-sql file is created and saved, make sure the login page is pointed to your new mgr-sql file before continuing. You can use the change button if it is not pointed to the correct location.
Then, click login. If the connection is not correctly configured, you will see an error message in a tooltip. This will be a message directly from the SQL Server driver similar to the message shown below:
Reasons the login can fail include:
- the server name or database name is wrong, or the network is incorrectly configured to allow access to the server
- the user is not mapped to a SQL server login
- the user has a login but is not mapped to a database user with db_owner permissions