For others out there who may have encountered the same problem that I
reported here about two weeks ago, I finally found out what was causing the
Btrieve 5.10a for MS-DOS was* during a load, specifically while being
called from our batch file. It turns out the culprit was the /T parameter,
but the reason was because the file specified (and all files in that and all
sub-directories for that matter) were flagged as read-only.
The end-user had used a CR-RW to copy our system from one machine to a CD-R,
then copied the entire directory structure to the new computer. This caused
the new copy to retain all the read-only attributes.
Apparently, when Btrieve attempts to access the file specified with the /T
parameter, and it is set as read-only, Btrieve will hang instead of
reporting any problem.
The solution, of course, was to do an ATTRIB -R *.* /S from within that
Bill Hileman, Programmer/Analyst, DASI
Language Comparison: http://www.veryComputer.com/
PROGRAM n. A magic spell cast over a computer allowing it to turn one's
input into error messages. tr.v. To engage in a pastime similar to banging
one's head against a wall, but with fewer opportunities for reward.