CL>>   The problem is not system dependent.  It has happened on various
CL>>   systems - 386, 486SX, Pentium.  It has happened when running GW
CL>>   exclusively on DRDOS as well as on MSDOS under WIN95.  The operating
CL>>   system, hardware, and memory configuration does not appear to be a
CL>>   factor. The only consistent factor present appears to be the number
CL>>   of records in the file, as mentioned above.  Not even the number of
CL>>   fields seems to matter.  I have had some records with about a half
CL>>   dozen fields, others have closer to two dozen.  Get too many records,
CL>>   though, and crash it may.
CL>>   Needless to say, it is frustrating and time consuming.  Any comments
CL>>   or suggestions?
The number of records is not the problem.  I have 2000 records in one
database and over 1000 in each of 2 other databases with no problems,
although I have had your problem in the past.  I did several things.
Got rid of any TSR's that weren't needed, increased my handles in
Preferences, deleted the state files and ran memmaker to get as much
conventional memory as I could get.  Also, make sure you don't have
share.exe loaded.  I think that was my problem way back then.
                                                Terri
... Live long enough to become a problem to your kids.
--- MsgToss 2.0d(beta) 02/21/93
---------------