Re: Online "INTO TEMP" bug

For what it's worth we hit the same problem. The app created a temp file with the name "printconf" for each user at the start of a session. The result was utter chaos. The chaos ensued until I was able to: a. Unload the *entire* database (no mean task in itself). b. Reconfigure the HD to delete the raw partition and add the space to an existing file system (not trivial in SCO). c. Load a *borrowed* copy of SE on to the system. d. Reload all of the data. This is *not* a fun way to spend your days. Currently my customer is still banging away on SE. They're not happy, but they're also in no rush to have the business completly disrupted again to get them back on to Online. ---------------------------------------------------- These opinions are mine; if you want them, take them ---------------------------------------------------- Stuart Hemming | shemminga@cix.compulink.co.uk The Data Base | +(44) 1602 250005 Nottingham UK | ----------------------------------------------------