Problem : Heap/Stack over-run in TextStream I/O
Solution : Can be caused by overflowing the TextStream buffer
add WriteLine() call(s) more frequently
Well, after much thrashing with what I had thought was
a table search bug, it turns out that Paradox (most likely)
doesn't flush TextStreams until a End-Of-Line condition
is reached. If you have TextStream I/O and you exceed the
stream buffer size you can see your variables (stack-space),
data (heap), or even code (code-space) being corrupted.
This may (or may not) crash the Paradox/Windows session.
Hughes Aircraft Co. voice: (310) 616-1059
PO Box 902, EO/E01/B125, El Segundo, Ca. 90245