Karen, I'm not sure it's about files that are "open." I think John or Razzak or Alexsey explained once that it had to do with R:BASE using MS Windows features to build the lists in the group boxes of the Database Explorer: The applications, the databases, the command files, the external form files, not to mention all of the lists that are internal to the database. There's a size threshhold somewhere where things slow down. And it's not the same on every workstation, so it also has to do with available memory.
Bill On Wed, May 30, 2012 at 9:22 AM, <[email protected]> wrote: > No problem with this thread diverging a bit, but my original question was > not about what files might be open and running at any one given time. In > the past, people have indicated that the number of files sitting in the > database directory had a bearing on speed. That if you had 4 database > files and one startup file it would be faster than if you had those files > plus a hundred extra files in the directory. My question was if it's > different if the database is in its own directory. > > Karen > > > In a message dated 5/30/2012 8:10:12 AM Central Daylight Time, > [email protected] writes: > > We use the Microsoft Management Console to look at open files running from > the network shared folder. Some files are open with read access, some are > read/write access. We average about 500+ open files at a time on the > network share. 50 of those are connections are to the .rb* files, while > the rest are eeps, cmd, exe, etc. We now have more computers than ever > and I am worried we are stressing the system to much. > > > >
