>Finally, I'm game for the virtual (Chicago style?) pizza, washed down with a few virtual beers after this is over. I also hope (for your sake) that this is virtually the end of both this thread and your problem.
>
>Good Luck and Keep the Faith,
>
>George

Well this ordeal is over now, and once I finally got the app to work I think I now see what the real problem is, so I'll toss it out for any who are interested.

With 2.6, any drive thats is 2.1 GB or smaller is seen by FPW just fine. SYS(2020) gives you the correct default disk size (2147450880 bytes). But if your drive is larger than 2.1 GB, SYS(2020) defaults to like 1 GB (1023932928 bytes), regardless of how big the drive is. Yesterday I was looking at this 1 GB number and reading it as 10 GB unfortunately. (smacks head)

This AT&T Billing Edge app needs to pull in a day's file from CD, do trending analysis, mormalization, and whatnot, then delete the file it took from the CD. Since I work for a telecommunications company, a "day's worth of call records" for us has grown larger than 1 GB (1.75 for July 31 file) Before the app moves the file over, it must be using this SYS(2020) to determine if there is enough space. So with a 4 GB drive with 3.5 GB available, FPW was only allowing the app to see the 1 GB default and this of course was smaller than the day's file.

Once I gave in and reformatted and set a partition to split my 4 GB drive in half, the app was able to see the full 2 GB disk size and went about its business of copying in file, etc.

Thank you everybody, this was weird but its over. And Barbara came to my rescue with a virtual beer & pizza! :)