In order for users to be able to print from this applet, it may be necessary to run in Windows 98 Compatibility Mode. To do so, the Applet and its associated files should be installed on the user’s local machine, not the server. Right click on the shortcut to the applet, select Properties, click the Compatibility Tab, and set to Win98/ME.
If the Applet displays a Dialect Application Stopped Working message when it is closed, it is possible that the msvcrt.dll is the cause of the error. Updating to updating the msvcrt.dll to a newer version.(7.0.7600.16385 as of this writing). The Microsoft Knowledge Base should be consulted for an appropriate update.
1. RPC Server
The RPC server must be running in order for the Remote Time Applet to operate. This is typically configured to run as a service: contact your support representative for details. When your users log in remotely, they must be able to access this service.
2. Employee Id in User Record
The Employee Id must be included in the User Record for all employees who will be entering time remotely. The Access Type must be set to Full or Remote.
3. Registry Entry
The Registry Entry for Remote Time Expense Applet configurations enables you to control the format of the time and expense display sections of the remote time screen, the number of previous and future periods that may be accessed, the first day (and number of days) of the period, retry and timeout constants, etc. You may create multiple registry entries to accommodate different data entry styles.
Note that the data entry fields in the top portion of the Time & Expense Screen are managed by the screens.txt or the screensstylename.txt file. Contact Data-Basics support for details.
4. Employee Record - Time Sheet Styles and Groups
If your firm retains two or more types of employees (for example, project managers and other employees), you may wish to provide each with a different style of remote time screen, suitable to their needs and restrictions. If you will be using Styles (for data entry), or Groups (for posting hourly vs. salary time, for example) see Employee_W2_Tab for details. Both Groups and Styles must be specified in the Employee record if they are to be implemented.
5. Executable and Configuration Files
The following files must be all located in the same directory, and must be accessible to the remote time user. If these files are revised, they must be copied to all applicable user locations.
time_expense_viewer.exe
The remote time executable file. It is recommended that you create a shortcut to this file on the user’s desktop.
ip.txt
This file specifies the location and port that the applet must query in order to run.
screens.txt or screensstylename.txt
This file, obtained from Data-Basics, is also required; it controls the configuration of the upper (data-entry) section of the screen. When determining which screens.txt or screensstylename.txt file to use, the software will look at the Remote Timesheet Style field in the user’s Employee record. It this field is blank, the system will use the screens.txt file to determine the data entry configuration.
If the Remote Timesheet Style field is completed, the system will look for a correspondingly named screens file. For example, if the Remote Timesheet Style file is completed as pm, the system will use the screenspm.txt file to set the data entry configuration. In addition, the system will also look for a registry entry named sys-remotetime-pm to configure the display fields, number of previous periods, and so on.
mag.bmp
The magnifying glass bitmap used by the remote time applet.
6. Payroll Period
When remote users enter their hours and expenses, the system will determine which Payroll and Accounting periods to use based on which payroll period encompasses the computer’s system date.
7. Posting Remote Entries
When remote users enter their time, it is held in the RPC table until it is posted via the Start Post Remote Time Sheet function. Once an entry has been posted, it cannot be altered or detailed in the Remote Time and Expense function.