>Hey All! I'm having a problem with a client who is saying our application runs slow after 40 users have been on it for some time (they have too many network people at their disposal). What I'd like is any general info on foxpro and memory leaks, and I'll give a general rundown of our app and how we handle things to see if there are any immediate problems.
>
>Database for mortgagebanking. We use quite a bit of private datasessions because the user needs to be able to open the same form on multiple properties at once (we see no other way to accomplish this). The master table has about 30,000 records (ie loans). We use local views for the main screen (a major chunck of laon info brought up at once), which is broken down to a form with 8 pages and classes on the pages (only instantiated when the user goes to the page). Other than the main page though, we tend to make direct reference to the table (ie USE sometable.dbf... someobject.ContorlSource = table.field). Since there are a number of Private Datasession forms, it is possible for the same table to be open many times within the app either on the same loan or on a different loan. The server is running 310Mg RAM on a Raid 5 Drive structure, out through a gig card, through a gig backbone, to cat5 cable to the 100mps client (clients range from P166, PII233, PII400 but all with 128 Ram).
>
>Ok there's a start, let me know what else you need and thanks for the help.
>
>Shawn Burke
>DRI Management Systems

Memory leaks may cause PC to get frozen, but just separate PC. It has nothing to do with network resources. Again, running multiple local views you enhance network traffic. Each view requering means running Select-SQL, i.e. moves index tags down the wire, and if you have many users doing similar operation then network traffic can increase too much. How much is too much depends on network configuration (sorry I'm not an expert here).
I don't want to advise you to re-engineer your approach, but the truth is that local views have own speed threshold , and this threshold is lower then VFP native data access limitation.
The last thing (probably even more irrelevant), it's quite possible to open the same form multiple times without having private DS. This way assumes unbound controls.