I recently got the above mentioned 'Too Many Files Open' error while developing several forms. Each has a separate, private, data session. One form opens 30 remote views, and the other two open 6 remote views each. Only one remote table is common among all three data environments. Upon checking the current MS KnowledgeBase, there were three potential solutions.

The first suggested that the FILES setting in the CONFIG.SYS file wasn't high enough. It was set at FILES=150, and pumping it up to 175, 200, and 250 made no difference. This is not a Novell network, so there is no NET.CFG file. The CONFIG.FPW file simply runs the VFPSTART.PRG file, that's it. No luck.

The second potential solution had to do with the SHARE utility and some of it's switches as specified in the AUTOEXEC.BAT file. It wasn't in use. I put it into use with the suggested settings, but no luck. The error
remained.

A third potential solution talks about private data sessions using many more file handles than default data sessions. While this is true, each form can be opened multiple times, thus default data sessions will not
work. I instantiated each form and used the AUSED() function to determine how many cursors were open in each. The first had 38, the second 7, and the third 6. Now, assuming the very worst case, (and this is NOT the
case), that is 3 file handles for every cursor (.DBF, .CDX, .FPT) and 2 handles for each private data session (.DBC and .DCT - only two used according the KnowledgeBase), having all three forms opened at once should use 159 file handles, not 255!

Now, the application is based on CODEBOOK, so there are several other cursors open in each session, and in the default session AUSED() returns 7 so for the default and the 3 privates that another 28 handles. Where are
the other 58 handles being used?

Thanks to anyone who can help...

Mario