Database resource use

[mattbrown]

I am designing an application that uses DAO objects in code to reference a database.

This application will be running all day ie. 8am - 5pm, but may only be used for maybe 20 mins every couple of hours or so.

My question is, is it more resource friendly to initilise 1 global recordset object at the start and leave it open all day, whether it is needed or not, Or
to keep opening and closing recordsets when they are needed.

I would be happy to give you more information on the specifics of my application if you feel it is relevant

[JHausmann]

It's just memory. I will open once for as long as I need mainly because it minimizes the *chance* of memory leaks.