Just a note for the forum:
Mouser requested, and I have provided, details of the trigger for the error (DBISAM Engine Error #11949 SQL parsing error) and its symptoms.
He has been doing some problem analysis and resolution and has has given me a new test version of CHS .EXE to try out - and it not only seems to fix that error, but also seems to make CHS more stable and well-behaved overall.
Over time, I have come to depend more and more on CHS
- so this is very heartening for me.