Re: Error created linked tables from one .mdb to another .mdb
- From: "Jeff Johnson [MVP: VB]" <i.get@xxxxxxxxxxx>
- Date: Thu, 28 Apr 2005 16:30:18 -0400
"Dale" <dale0610@xxxxxxxxxxx> wrote in message
news:OLM072CTFHA.3620@xxxxxxxxxxxxxxxxxxxxxxx
> Hi, this is sorta related to a thread I created earlier about using the
> Access.Application object to relink tables. Jeff suggested I use the
> DAO.Database object instead. I googled some example code that I modified
> a little and testing it right now. It works fine and creates the linked
> tables to SQL Server tables in my .mdb file. However, there are also
> linked tables to another Access .mdb as well. I thought if I just change
> the strConnect parameter to connect to the other .mdb file that it would
> link properly but it fails with this messagebox message popping up:
>
> "Error # 3170 was generated by DAO.TableDef
> Could not find installable ISAM."
>
> This is the value I am passing for strConnect:
>
> "Provider=Microsoft.Jet.OLEDB.4.0;Data
> Source=\\Backoffice_demo\C\ServerDB\POSBdat.mdb;"
Sounds like you may need to install the Jet OLE DB provider on the target
machine. This is no longer part of MDAC and must be installed separately.
You can probably find it starting here: www.microsoft.com/data.
.
- Follow-Ups:
- References:
- Prev by Date: Re: MDI Loading multiple children
- Next by Date: Re: MDI Loading multiple children
- Previous by thread: Error created linked tables from one .mdb to another .mdb
- Next by thread: Re: Error created linked tables from one .mdb to another .mdb
- Index(es):
Relevant Pages
|
Loading