Not so. It's a external file to the database, and has to be distributed
along with the MDB. Granted, that may be easier than creating a DSN, but
DSN-less is far superior, in my opinion.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"martinjeffreys" <ma************@btinternet.com> wrote in message
news:cg**********@titan.btinternet.com...
There are 3 different types of ODBC set up
User
System
File
I think File's the one you want - this incorporates itself into the mdb
and moves with it
"Enzo's Dad" <~D**********@Hotmail.com> wrote in message
news:Gq**************@news.uswest.net... I have an Access frontend for an SQL backend. I'm simply using ODBC to
connect. On my copy of this Access database, I have four linked tables and all works well. If I copy the Access MDB to another workstation, I have
to 1) recreate my ODBC connections, 2) delete all my linked tables, and
then 3) recreate the linked tables.
Ideas to automate this? I'd like to have multiple users use my MDB.
Thanks in advance.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.714 / Virus Database: 470 - Release Date: 02/07/2004