|
|
 |
|
| |
 |
SUPPORT |
 |
|
|
PLEASE NOTE: Any issues not discussed
below can usually be resolved either by
downloading and installing the latest At Your Service service
pack, or by repairing your current installation. For a complete bug
fix history and instructions on repairing your current installation,
please see the Read Me
file. |
|
|
|
Most program features
are explained in detail in the User's Guide by pressing the F1 key
from within the software. You may also browse the
on-line version of
the User's Guide. |
|
 |
|
|
|
|
INSTALLATION ISSUES |
|
|
|
|
1. When I am
installing the program on a workstation or server with File Protection enabled I get a warning message
saying that the Windows installer service cannot
update certain files because those files are protected by
Windows (e.g. hhctrl.ocx or scrrun.dll). What should I do? |
|
Click the OK
button to ignore the
warning message and continue with the install. The File
Protection feature simply warns you when certain protected files on
your system have a different revision number than the ones in the
installation set. For
further information, see Microsoft knowledge base article
222193. |
|
|
|
2. I installed
the program on a Windows 95 or Windows 98 First Edition
operating system, however the program does not run. What
should I do? |
|
At Your Service
is no longer officially supported on Window 95 or Windows 98
First Edition operating systems. We highly recommend that
you upgrade to a newer operating system. However, the
problem is likely that you do not have Microsoft Data Access
Components installed, which is native to newer operating
systems.
Download and install MDAC
2.6 or higher before installing At Your
Service. |
|
|
|
DATABASE ISSUES |
|
|
|
|
1. My database
is stored on a Windows NT/2000/XP/2003 or Novell file server. The
program sometimes reports that the database may be corrupted
and then automatically repairs itself, or the program
reports that the database is locked. How can I prevent these
problems? |
|
Microsoft has
reported a bug on these file servers that can cause locking,
corruption or reports of corruption in Access databases. In
most cases, the data in the database is not actually
corrupted, but a flag indicates that corruption may
have occurred. The problem is resolved by turning off
Opportunistic Locking (oplocks) on the file server. On some
operating systems the problem may also be resolved by
installing the latest service packs. For further information
and instructions, see Microsoft knowledge base articles
303519 (half way down the page) and
296264. |
|
|
 |
|
 |
|
|