Create linked tables in Access database

  • Thread starter Thread starter Fred
  • Start date Start date
F

Fred

Hello,

I need to create linked table in a mdb (or accdb) file.
These linked tables sources can be csv files, sql server table or other
if I have the odbc driver (sage for instance).

How can I do this ?

Thanks for any suggestion.
 
I do not know why you ask this question here in ADO.NET NG.

You only need and do linked table when you use MS Access as front-end
application (so you will not use .NET stuff with it). You start MS Access,
go to menu "Files->Get External Data->Linked Tables..." to link this front
end to a back end data source (ODBC data source).
 
Fred said:
Hello,

I need to create linked table in a mdb (or accdb) file.
These linked tables sources can be csv files, sql server table or
other if I have the odbc driver (sage for instance).

How can I do this ?
Click to expand...


I didn't find something else than using a com reference to ADOX which is
what I wanted to avoid.
Never mind. I finally used another way.
 
There are many free resources available online -- simply search on
some combination of "odbc linked tables from MS Access".

--Mary
 
I hope you don't expect this to work very well. While it's possible to link
tables into an Access/JET database, the JET engine does not handle them
particularly efficiently.

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
____________________________________________________________________________________________
 
Not necessarily, you just have to understand what you're doing. See
Optimizing Microsoft Office Access Applications Linked to SQL Server
http://msdn.microsoft.com/en-us/library/bb188204.aspx. It gives you
the lowdown on how to use Jet efficiently, which is basically the same
rule of thumb as for any client-server application -- fetch only
needed data; don't "link" to the whole megilla. Used correctly, Jet
gives you a lot of flexibility (basically you can use it to cache data
on the client machine, much the same way you'd use a DataSet, except
with a decent query engine and the ability to persist it, if desired).

Stephen Forte and I are co-presenting a session at TechEd this year,
DAT312, "Solve Problems without Spending Money: Access and SQL Server"
in which we'll cover using Access as a front-end to SQL Server data to
solve various business problems when there isn't a need (or there
aren't the resources) to develop a full-fledged .NET app. See
http://www.msteched.com/sessionlist/default.aspx for details.

--Mary
 
Back
Top