Re: Dis-instantiating a form object having connections
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Sun, 19 Nov 2006 09:38:57 -0500
I don't know. If you get no response here, you might try one of the Access
groups.
When I was doing Access development, forms were still using DAO, not ADO. I
don't really know what they are using now.
AK wrote:
Will dis-instantiating a form object that has an open ado connection
(to access DB), and has been instantiated by a reference to it on
another form (for example via a Debug.Print FormObject.Name
statement) close the connection that the instantiated form
establishes?
More specific:
On FormA (which opens a connection ) I instantiate form global object
by using a set statement, then I unload FormA and Show FormB :
Public g_objPredecessorForm As Form
Set g_objPredecessorForm = Me
......open up an ado connection
UnloadMe
FormB.Show
Then on FormB I do a :
Debug.Print g_objPredecessorForm.Name 'This instantiates
FormA with its open connection!
Set g_objPredecessorForm = Nothing
Will the conection that was opened when FormB instantiated FormA (via
the Debug.Print on FormB), be closed by the Set g_objPredecessorForm
= Nothing statement??
AK
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
.
- References:
- Prev by Date: Re: Indexing of Connections
- Next by Date: Check out the code for filtering ADO recordset
- Previous by thread: Dis-instantiating a form object having connections
- Next by thread: Check out the code for filtering ADO recordset
- Index(es):
Relevant Pages
|
|
