Dan,

>Yes. And, I thought I understand why we were having so many problems with Multi-Use. But now I am not so certain.

Please indulge me for a moment while I run through an alternate approach. I'm remembering/surmising that your original problem when running several instances of Single-Use EXE's, was a buffering issue? Data wasn't getting written out quickly enough, or something like that?

I remember that Rick's suggested solution was to close the table after writing, but what was the problem with that solution?

If you concern is the time needed to close/open data files, did you try something like the following (I have not tried this under a stress test, but it's something that I would investigate if I were in the same situation):

1) Compile project as Single-Use
2) In your MAIN program that runs on startup of the EXE, open heavily used data files.
3) In PROCESS class code, call logic/data access components built from the SESSION class, with private data session. In these components open and close files as needed.

I believe that those private data sessions will do the equivalent of USE AGAIN on the tables originally opened, so the opening should be fast, and perhaps closing the table in the private session would properly flush, while leaving the tables still open in the MAIN program. That's the part I have not tested, but wanted to spark an idea for you in case you had not tried that.