>>>>>>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...
>>>>
>>>>Dave -
>>>>
>>>> I'm guessing that you have never run a really HUGE query with tempfiles sitting on the network. I made that mistake once. And, after having the other 3 customer areas, the Network Support Specialist (NSS) for that network, and about 10 other programmers (whose work got crapped out when the network choked and gagged) bounce off my head (apparently they weren't REAL keen on a network that essentially quit working), I decided that perhaps I should go out of my way to make SURE that my tempfiles went somewhere other than the network. Especially if it's a Novell network.
>>>
>>>Point well taken, but I have users with virtually no hard drive space, so we have to use network server. I've taken to placing limits on the queries users can make, such as Name must be at least 3 chars, etc., and using SQL top # in queries also to limit size (with appropriate messages to user). And investing in 4.3 gig or larger server drive for queries also helps...
>>
>>and his object was to place it somewhere other than the user's hard drive...
>
>I thought his object was to be able to find out the local harddrive setup (little C:, big D:...) and set the tempfile locations dynamically.

That is exactly my object! The best response was to create a separate program that runs at installation. The program will get all the drive info and then create the CONFIG.FPW file with the best TMPFILES setting. Thanx to everyone for the help!