[AccessD] Persistent Connection question

[Jim Dettman]

Janet,

  I can't think of any reason why that should bother anything.

  While it would not be my first choice (just open recordset on a table),
there's nothing per say wrong with this.

  Your chewing up another connection to the DB, but that's it.  There's a
little more overhead in your app of course, but still, that should not
amount to anything.

Jim. 

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Janet Erbach
Sent: Friday, April 03, 2015 04:41 PM
To: Database Advisors
Subject: [AccessD] Persistent Connection question

Hello all -

I've finally discovered what's been causing extremely flaky behavior in a
database I've been wrestling with for the past 3 weeks.  It was one line of
code in the menu form that opens with the app:

Dim dbsAlwaysOpen As DAO.Database
Set dbsAlwaysOpen =
OpenDatabase("S:\MAINT\ToolingTech\dbToolingTechData.accdb", False)

Some forms were not populating consistently, records were sometimes being
dropped during select and insert queries, other forms needed to be manually
refreshed repeatedly in order to display all records, things like that.
The app worked fine when opened in design view - not when run from the menu.

This morning I bound the menu form to a small, 'fake' table in the backend
and everything seems back to normal now.

Why would this method of establishing a persistent connection cause
issues?  I found code like this on a couple of websites when I was pursuing
serious speed issues with the app.

Thanks!

Janet Erbach
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com