DM ->        DBSETINDEX(0) internal error 5333
All of what David Brelew wrote is correct, but may not solve your
problem. To elaborate on his explanation, if you have the NOEMS on your
EMM386.EXE command line in CONFIG.SYS, it disables expanded memory, but
versions of Clipper prior to 5.2 don't recognize it. This causes the
program to crash when it tries to access the non-existent expanded
memory. If you _don't_ have NOEMS specified, this definitely isn't the
problem.
The internal error 5333 is well known, and was never fixed in Clipper
5.01a. It took all the way until 5.2d was released for it to get fixed.
It means the Clipper Virtual Memory Manager has run into a situation it
doesn't know how to handle.
The only real fix is to upgrade to Clipper 5.2, apply the 'e' patch,
and recompile and relink your program.
Raymond Pesek
 * 1st 2.00 #2448 * Moderator - Clipper Echo
--- InterEcho 1.19
---------------