Hi Shawn,

It would also be helpful to know things like...
1) Is this a general slowdown on ALL user connected at the time, or just some specific users? (say, the ones who are quickest or the ones who do the more complicated work)
2) What is "runs slow"? Is it down from sub-second response to over 2 seconds, or over 5 seconds, or what. In other words, what is 'normal' acceptable response and what is "slow" response?
3) Does this last for the rest of the day once it happens, or does it get better again at some point?
4) Is there something being run on the server which could be causing a slowdown? At the office I'm working at now there was a marked slowdown observed, with later determination that it was happening twice a day around specific times and was lasting for between 30 - 90 minutes each time. It later came to light that a "systems guy" (I was one, once upon a time) was doing some personal backups and some other work at those times and since he stopped, so did the slowdowns.

You say "only instantiated when the user goes to the page". Are you quite sure that they are being fully removed from RAM once they are finished with? - don't go by the absence of a variable in DISP MEMO for this, because VFP will trash a referring memvar but RETAIN an object (without notice to you) under certain circumstances. I call this a "memory leak" because you have no real and legitimate way to detect it through "natural" VFP other than experiencing what your users are complaining about or getting an actual out-of-RAM condition. You can learn if this is the case by testing and monitoring RAM consumption while you do so.

Good luck,

Jim N


>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