Hi,

Wanted to do just the same thing myself, had same problem, and wondered if 
you ever came across a solution?

Many thanks

Robin


> 
> Hi,
>  
> I have 2 databases x, and y. Both are Access 2000 databases.
>  
> To x, I want to link a few y tables. I do not want to use direct path
> because it will lead to
> problems when I deploy the application using database x. 
> Therefore, I created an ODBC DSN for database y thinking that I could 
> link
> its tables to x.
> Everytime I try to link the tables, I select ODBC in the FileType: drop
> down. When I select
> the ODBC DSN for y, Access prompts me with the following message:
> 'You cannot use ODBC to import from, export to, or link an external
> Microsoft Jet database table to your database'
>  
> This is what the help says:
> ' You are attempting to link, import data from, or export data to 
> either an
> external  <javascript:hhobj_1.Click()> Microsoft Jet table or an 
> external
> ISAM database 
> table (for example, dBASE, Microsoft=AE FoxPro=AE, Paradox, or 
> Btrieve), but you
> have selected <SQL Database> as the data source. 
> You must select the appropriate data source for the data you are 
> attempting
> to link.'    
>  
> I think ODBC is the best way to facilitate deployment headaches, it 
> should
> have worked with Jet or non-Jet databases.
>  
> Does anyone know about a way around this? 
>  
> Many thanks
>  
> Terrence
>