Error 134 - Cannot lock PARADOX.NET
October 8, 1999
attempting to access Health Management System for Windows,
you may encounter an HMS1000 Error Report that contains the
following entries in the Error Statistics section of the report:
Description: During PXWinInit
Error Number: 134
error is generated when the Health Management System cannot
create an exclusive "lock" on the data file being opened.
This can occur if a lock created for a database record is
not removed due to an unexpected shutdown, or if your system
does not start the SHARE program during boot-up.
unnecessary lock files
any applications currently running.
Using File Manager (Windows 3.x), Windows Explorer (Windows
95/98), or the MS DOS Prompt, delete each instance of the
following files from the root directory of drive C:
Windows 95/98, you may use the Find Files feature to locate
and delete these files.
on the Start button and choose Find -> Files or Folders
the Named box, type *.LCK, *.NET. The Look
In box should contain (C:).
on the Find Now button to locate the files
all instances of the files listed above
that SHARE is running (Windows 3.1 only)
Windows 3.1 systems, SHARE.EXE must be installed for
the Health Management System to function properly.
To verify that SHARE is loaded on your system,
exit to DOS. At the DOS prompt, type SHARE and press
Enter. If SHARE is running already, you will get the message
"SHARE already installed." If you do not see this message,
then SHARE was not running and will need to be referenced
in your AUTOEXEC.BAT by adding the line Drive\Path\SHARE.EXE,
where Drive is the drive where your DOS commands are
stored and Path specifies the location.
You must restart your computer for these changes to take
Word (.doc) version