>Is the new drive formatted as NTFS or a FAT partition?
>Could the application be ignoring config.fpw and defaulting inside it to the C drive windows\temp or c:\temp, so if you added a
>new drive it would not use it?
>
>Just some thoughts...

Good thoughts.... Its NTFS alright. And I can tell the apps using the config.fpw because I keep playing with the default drive setting, and when I launch the app the first thing it does is prompt to pick a "day" which is a table of call records, and the open dialog is coinciding with where I'm setting the default drive in config.fpw.

But here's something even stranger, on this same machine I opened up a regular FPW 2.6 session and open every big table I have (used like 30+ work areas)and cant get a disk space error for the life of me. Any other ideas before I give and setup multiple partitions?