 |
|
|
|
|
|
|
|
|
 |
|
|||||||
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
|
|||||||
Read this first...
Please read the support policy and this page;There are also a handful of operating system specific issues that technical support staff might find useful.
The help system in ScriptBase is fairly comprehensive, and should answer most of your questions if you have a problem in your use of ScriptBase. Press the F1 key at any time for context sensitive help (that is, relent to what you are currently doing) or select the help menu / contents.
If you still have difficulties your are not able to resolve, please contact ScriptBase software with your questions.
Your problem will be solved most quickly if you take a little time at self diagnosis, and use email for questions that you are unable to solve.
The following are the solutions to over 90% of support emails.
Unable to Log On
9.5 times out of 10 the user has the 'caps lock' key on, so they are inadvertently typing their password all in upper case. First try tapping the caps lock key and trying to log on again, if that doesn't work, restart the whole computer. The other reason might be that the user has actually forgotten the password, if so they need the system admin to help (see the help file). The other possible reason is:
Data Corruption Problems
If you are unable to get into ScriptBase with a corruption error, have or access violation error or DBISAMERROR or the data browse has just gone weird, you may have some corruption of the data tables. This is usually minor, and ScriptBase includes a utility to repair your data. This is on the Tools / Utilities menu, and should only be run if no other users on a network are currently logged on to ScriptBase.
If this is unable to fix the problem, you may have to replace the reported files from a backup (though this is extremely rare). If you are unable to get in to ScriptBase to run this utility, it is also included on the ScriptBase menu, without going into ScriptBase. Running the fix tables utility periodically is quite a good habit. Say once per month should be ample.
On older versions of ScriptBase, a common causes of corrupt data on the current release of ScriptBase, is users shutting down Windows without exiting ScriptBase properly first. We believe this is less likely with current versions, though if you often have corruption problems, put a polite notice on a yellow sticky piece of paper on each monitor requesting users to desist from this disgusting habit.
Printing Errors
I have always offered the following advice, a combination of which seems to have solved this in every instance.
1 Your computer has a bit of software called a 'driver' to tell it how to talk to the printer. The driver is specific to the printer, and is usually delivered with the printer on a disk. You can see the available printer drivers in the 'My Computer ' / 'Printers' folder. It is vital that the printer driver is the most up to date version available for the printer you are using. This error usually occurs when there is a slight mismatch between the two. For example, you have a HP Laserjet 6P printer, but the driver is for the HP Laserjet 6L. Often the driver has not been updated as under most circumstances it does not make any difference. You may not have noticed this as being out of date as it is close enough for most software. With it's need to line up text very precisely on the page, ScriptBase is very fussy about printer drivers. If in doubt, it can be helpful to get the most up to date version of the printer driver from the manufacturers web site. It is possible that even if it appears to be the correct version, that a newer version has been released since you bought the printer.
2 If that doesn't work, and the problem relates to missing the last name off the script, try adjusting the top margin using the Settings utility on the options menu.
3 If this still doesn't work, you need to check whether the printer is able to print close enough to the top margin. Do this using any word processor: set the top margin to 0 (or a negative number if this will allow) and type several lines of text. Print this out (saying yes to printed in an unprintable area if asked). Then hold this up to the light under (and lined up with) a blank script: look to see if there is a printed line where you need the name to be. If the text is cut off at this point, or only starts below this line, your printer is unsuitable for printing prescriptions! Go out and buy something by Hewlet Packard, which almost always seem to work (though personally I don't recommend diskettes).