>>>>We have an app that will be distributed in a stand-alone version on CD-ROM. The problem is that temp files are written by default to the startup directory. On CD-ROM, that would be the startup directory on the CD which is read-only of course. Instant crash.
>>>>
>>>>While we could just put "TMPFILES C:\" in CONFIG.FPW, this isn't a great solution. Some folks may have partitioned drives with C being a small partition with the operating system on it and D being the data partition.
>>>>
>>>>Is there any way to intelligently set TMPFILES? It would nice to be able to get the space available from all local drives and set TMPFILES to the drive with the most space.
>>>>
>>>>TIA
>>>
>>>we usually use c:\temp or c:\windows\temp. space shouldn't be an issue unless the user has developed the habit of turning off the computer with apps up. if he has, space will be the least of your problems.
>>
>>Space IS an issue. Our app does lots of queries and some of them can be quite large. The cursors are stored to temp files during processing.
>
>that kind of work should be done on the network server, not brought down locally... add a temp directory to your dir structure on the network and do it there...
We need the program to run from the CD and it has to run on any machine, not just a networked one.
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
