ADOConnection - odd problem solved but why?
From: Peter Piper (NoEmail_at_Email.com)
Date: 12/14/04
- Next message: Peter: "Re: Reading all the packets from NIC"
- Previous message: Peter Piper: "Re: Reading all the packets from NIC"
- Next in thread: Moi: "Re: ADOConnection - odd problem solved but why?"
- Reply: Moi: "Re: ADOConnection - odd problem solved but why?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 14 Dec 2004 11:52:08 +0000 (UTC)
I have a form with an ADOconnection and two tables.
The form is created on the fly (ie. not auto created).
When i close my application i get an Access Violation Exception unless
the ADOconnection Connected property is set to true at *design time*.
Set to True at design time, no exception.
I have used ADO in nearly every big app I have ever wrote and never had
this before.
Now all I can think is because the are more than one instances of the
form something odd is happening. Why settings connected to true should
solve this i dont know.
Maybe an application cannot handle more than one ADO connection at once
to the same database - ???
Any one any ideas?
Cheers Pete.
- Next message: Peter: "Re: Reading all the packets from NIC"
- Previous message: Peter Piper: "Re: Reading all the packets from NIC"
- Next in thread: Moi: "Re: ADOConnection - odd problem solved but why?"
- Reply: Moi: "Re: ADOConnection - odd problem solved but why?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|