Re: Dev 2000 - forms eating up memory

[Quoted] We had the same problem and discovered one thing that helped.

One of the developers coded a form that DIDN'T CLOSE ANY CURSORS!!

We found it by watching the memory usage while we opened and closed forms. It always would hang on to more memory when we opended the form that was incorrectly coded. I helped that the form didn't close a single cursor, I imagine it would be harder to find if only one cursor was left open - but it's something to check anyways.

In article <vApP4.101421$2D6.2584183_at_news20.bellglobal.com>,   "Colt5" <Colt5_at_interlog.com> wrote:
> We currently deployed a new billing application using an Developer
 2000
> Forms and Reports runtime out to 700 machines. The database resides on
 a
> nice HP V Class server. The deployment was essentially running all
 Forms
> from an NT server.
>
> When Clients connect, as they open more windows/forms they use more
 memory.
> When the window/form closes, it does not release the same amount of
 memory
> as it first consumed. After a period of time the memory is used up.
 Only
> closing completely out of the designed app does all the memory that
 the
> Forms/Reports windows used when it originally launch.
>
> Now the Developer 2000 software is installed locally on persons
> workstations, but the Forms etc, are on a NT server with a share. It
 works
> perfectly except for the memory issue
>
> What we are trying to firgure out, is if its the way the connection is
 made,
> the way the Forms were designed, or something to do in the network
 client
> side.
>
> Can anyone offer some suggestions ?
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Tue May 23 2000 - 00:00:00 CEST