This is an old revision of the document!
JobMatix uses Windows Authentication security to connect the client program to the SQL-Server service. This means that no password is stored in or seen by the JobTracking program, since the authentication is handled by the Windows network security system (eg NTLM) in conjunction with MSSQL Server security. This relies on the normal Windows user password system and network security. It means that each Windows user for JobTracking must be set-up both in the client Windows system and the Server Windows system with the same user name and password.
Also, each such username must be set-up as a valid login for MS-SQL Server (this can be done using JobMatix in admin mode). An exception to this is the group of Admin users on the server system. When the MS-SQL Server service is installed, the Windows local administrator’s logon must be added by default to the SQL Server sysadmin role. (This is a setup option for SQL Server 2005 Express). This is so that Windows administrators on the server will have automatic access to the SQL-Server admin functions (role). Also, in JobMatix, some JobTracking admin functions are reserved to users who have SQL-Server admin rights, i.e. only SQL-Server administrators can perform certain JobTracking admin operations.
The Jobmatix JobTracking database is hosted by the MS-SQL Server service. The database is not distributed with the JobTracking install package, but is created for the individual business by JobMatix (via the startup page) using a setup form to capture input from the business user and set up details particular to the business. This needs to be done once only to get the database started.
JobTracking needs to maintain an active ADO/Jet connection to the “recent.mdb” file that is the current MYOB RetailManager database for the business. The network path from that client to the current RM database is stored in the JobTracking database once it has been determined. However, when a new JobTracking client starts up, there is no path set up, and the user will be presented with a login form to connect to the database. Currently, the caption of the login dialogue box reads “Jet (Access) Database”. The user should browse to the “recent.mdb” file that is the current RetailManager database and complete the dialogue box to set up the connection.
The current path to the MYOB database is displayed on the main screen under the label “RetailManager Database”. Note that this path is relative to the client machine, ie. it is the file/network path from that client to the file-server, and it is saved in the JobTracking database for each client that has connected. To change to a different RetailManager database, double-click on the current path, and browse to the desired file.
Apart from SysAdmin users on the SQL Server machine, all other users need to be set up and known across the Windows network. In a local network that is not part of a domain, each user must be set up both on the client machine and the SQL Server machine with the same username/password in both places. This can be done through the normal Windows procedures: Eg for Win-7: Start/Computer/Manage/Local Users and Groups
In all cases, the Windows user-name must also be known to SQL-Server as a valid login. This can be done through the JobMatix main menu bar: ie. Admin/Users/Add Windows User to SQL JobTracking Logins.
Note: The user-name must be entered in domain format ie as domainName\userName or ServerName\userName.
— Updated: 18-June-2013 10:24am. JobMatix Team