I remember reading in a book (the O'Reilly one?) that an open database
handle
eats up some amount of dynamic memory and it recommended you only have
a database open when you are in a form that might access it.
Personally, my app has 7 databases. It keeps 2 open the entire time.
The other 5 are lookup codes and it only opens them when the user
displays the form that lists all of the codes. I have noticed no
performance
problem with opening/closing those databases when I open/close the form.
Brandon
----- Original Message -----
From: Jamie Macleod <[EMAIL PROTECTED]>
Newsgroups: palm-dev-forum
To: Palm Developer Forum <[EMAIL PROTECTED]>
Sent: Friday, April 14, 2000 9:19 AM
Subject: Re: Opening and Closing databases
> I'm not an expert on this, but I would guess that it would be better to
open
> and close each database as you need/don't need it. Since a database is
> really just memory, the overhead to open and close it can't be that high.
> Anyone else?
>
> Jamie
>
> "Timothy Astle" <[EMAIL PROTECTED]> wrote in message
> news:8281@palm-dev-forum...
> >
> > I have 3 databases, and each one is separate from each other. Each
> database
> > will be used in a different section of my application.
> >
> > I was wondering if it's a good idea to open all 3 databases at the start
> of
> > the application and then close them all down upon exiting, or open and
> close
> > each database depending on which section the user is in?
> >
> > What are the benefits / drawbacks from either approach?
> >
> > --
> >
> > Timothy Astle
> >
> >
> >
> >
>
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
