I've been using this linking external databases method with Access
(rather than futz with creating a bad query to try and break the lock)
and it works great, but there's a caveat. If you're making the mods
locally on your development box and then uploading to a remote server,
you need to ensure that the physical file path to where the Access .mdb
file is stored on the remote server is mirrored on your develpment box.
Apparently Access stores the path when a link to an external .mdb is
made, so they need to be the same on both sites (remote and
development). For example, if your .mdb file is stored on your remote
server at e:/web/mydomain/mydata/, then you will need to have your
Access databases for your site stored in this same directory on your
development machine.
Chris Montgomery [EMAIL PROTECTED]
Web Development & Consulting http://www.astutia.com
Allaire Consulting Partner & NetObjects Reseller
210-490-3249/888-745-7603 Fax 210-490-4692
>-----Original Message-----
>From: Jeff Beer [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, November 08, 2000 12:33 PM
>To: CF-Talk
>Subject: RE: Remote DB Alteration
>
>
>Assuming you are using MSAccess:
>
>Create an empty DB and create linked tables that point to the
>tables in your
>real DB. The ODBC connection can remain open, and you can
>upload a new DB
>at any time by overwriting the real DB. This works as long as
>you don't add
>any tables - you'll still have to modify the DB with the linked tables.
>
>The other route is to talk the host into turning off "Maintain database
>connections" in the CF Administrator for your ODBC source.
>That's the dealy
>that's locking your file.
>
>Good luck!
>
>Jeff
>
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
