This was a great idea, but I have to actually do this on the
production server as M$ Access can't link tables using a UNC path nor
can I manually edit the path. Sucks!
The only other solution I have come up with is to upload the .mdb file
as a different filename and run a scheduled script at night to copy
over the actual one.
From: [EMAIL PROTECTED] AT INTERNET on 03/07/2001 04:00 PM
To: [EMAIL PROTECTED] AT INTERNET@CCMAIL
cc: (bcc: Douglas Knudsen/ATL/ALLTELCORP)
Subject: Re: Those darn Access .ldb files
Douglas,
A simple way of avoiding Access .ldb files would be to create a blank
database. Then link it to the real database using File -->Get External
Data-->Link Tables. Select the appropriate database and tables. Then
whenever you need to swap out the database its just a matter of
copying
the file without having to worry about the Access .ldb files.
hth,
larry
--
Larry C. Lyons
ColdFusion/Web Developer
EBStor.com
8870 Rixlew Lane, Suite 201
Manassas, Virginia 20109-3795
tel: (703) 393-7930 x253
fax: (703) 393-2659
http://www.ebstor.com
http://www.pacel.com
email: [EMAIL PROTECTED]
Chaos, panic, and disorder - my work here is done.
--
[EMAIL PROTECTED] wrote:
>
> Ok,
>
> I've searched through the House of Fusion Mail Archive and Allaire's
> support forums for info regarding how to unlock a M$ Access file
through
> CF.
>
> Any thoughts?
>
> -----
> Douglas Knudsen
> Leveraged Technologies Group
> 678-351-6063
> Got Linux? http://linuxmall.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
