if you're using CF 4.5.x, you can try the following to force the release of
the DSN (and therefore the access file):
<CFSET temp=CFUSION_DISABLE_DBCONNECTIONS("DSN", 1)>
and to re-enable the DSN, you have to use:
<CFSET temp=CFUSION_DISABLE_DBCONNECTIONS("DSN", 0)>
of course, replace DSN with the real DSN.
-----Original Message-----
From: Mark Smeets [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 03, 2001 9:54 AM
To: CF-Talk
Subject: Access ldb files w/a twist
So, here is my question and basically it's a problem.
Now when you open any Access file you get that little annoying ldb file with
it, it closes no problem if you're working with Access directly however what
if the Access file is on a server and you don't have access to it directly?
What if I need to replace that database with a new one (and that stupid ldb
file won't go away)?
Any ideas would greatly help.
Mark Smeets/stranger0/ICQ #1062196
"Mr. West, not every situation requires your patented approach of shoot
first, shoot later, shoot some more and then when everybody's dead try to
ask a question or two" - Wild Wild West
A Stranger's Domain (Redesigned and New)
http://24.113.34.178/stranger
Official Splitting Adam Homepage
http://www.splittingadam.com/
Over the Wall Productions and Web Designs
http://www.solarcourt.com/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
