VB6 & Access design issues

Hi all,

Hope someone can pass on some advice re: some design issues I have made on my app.

Using VB6, Access and ADO

The app uses a local and server based db, the crunch work is done on the local machine and the results uploaded into the server db. The server db also allows for the retrieval of stored data to generate reports etc.

The app does both, the uploading and retrieval for report generation when needed, or just to query the db.

I make the 2 connections in the Sub Main. and have decided to
leave both connections open for the entire time the app is running. (I have read access can have probs with too may connects and disconnects)

Is this an acceptable way to go ?

Also I had my app running on the development machine (run from VB as it is not yet finished) for a couple of hours doing nothing. When I went to use the app, the app and VB6 crashed. Is this somehow related to leaving the open connections and does the connection time out after a certain time ? I had no open recordsets as I set them to nothing after each query.

Any comments would be much appreciated.

Cheers

jack