Re: ADO Connection to Access leaves .ldb file behind
- From: "Bob Barrows" <reb01501@xxxxxxxxxxxxxxx>
- Date: Tue, 1 Dec 2021 06:05:32 -0500
With a single-threaded environment, DAO is certainly a valid mechanism to
use for Jet databases. If it's solved your problem, then there is no need
beyond simple curiosity to investigate the ADO failure any further.
I have to admit to being really curious about that msaccess.exe process ...
:-)
Paul Sullivan wrote:
Thanks guys. I promise you, there is no other code! I've just quickly
tried the exact same thing but with DAO and it seems not to cause the
same problem.
Maybe anybody who paid for Vista should get a free copy of Windows 7
(as well as getting their head checked!)
"Ralph" wrote:
"Bob Barrows" <reb01501@xxxxxxxxxxxxxxx> wrote in message
news:eslXxUecKHA.1648@xxxxxxxxxxxxxxxxxxxxxxx
Ralph wrote:
Well, actually, yes, an ldb file will be created by an ADO
There is nothing in the code above that would require MSAccess.Exe
to be loaded, or an ldb file to be created.
connection, but I do agree that MSAccess.Exe will not be involved.
Yeah, I blew it. Was thinking one thing, typing another. <g>
.
--
Microsoft MVP - ASP/ASP.NET - 2004-2007
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:
- Re: ADO Connection to Access leaves .ldb file behind
- From: Paul Sullivan
- Re: ADO Connection to Access leaves .ldb file behind
- Prev by Date: Re: ADO Connection to Access leaves .ldb file behind
- Next by Date: Using RecordSetSave in an ISAPI Webservice
- Previous by thread: Re: ADO Connection to Access leaves .ldb file behind
- Next by thread: Re: ADO Connection to Access leaves .ldb file behind
- Index(es):
Relevant Pages
|