How to transfer/link data from mdb to MSDE ?

  • Thread starter Thread starter hkappleorange
  • Start date Start date
Of course you can.
Go to File/Get external data/link
At the bottom of the dialog that opens, change the files of type to ODBC
In the Select Data Source dialog, click on the second tab - Machine Data
Source
Choose your database from the Data Sources that are listed. If your
database does not exist, you will need to use the New button to create a new
one.
Make sure the MSDE engine is on while you do this.
 
If you want to link in the other direction, you
must have Jet installed, and change the MSDE
configuration to allow it to connect to Jet.
(By default connection from SQL Server to Jet is
disabled for security reasons) For syntax and
configuration details you will need to ask in
a SQL server forum.

(david)
 
Gunny,

As a matter of fact, MS have recently taken a U-turn, and are now
recommending .mdb instead of .adp as the FE for SQL Server BE. It seems
that, starting with SQL Server 2005, support for .adp is going away.
I happened to come accross this a couple of weeks ago in a thread titled
"ADP vs. MDB?" in the access.sqlserver NG, and this came from Mary
Chipman of MS, if you care to have a look.

Regards,
Nikos
 
Hi, Nikos.

I would never recommend using the MSDE when other database engines are
available, like SQL Server. But some folks don't have the choice. ADP's
are set up to work directly with MSDE's, which is what the questioner wants
to connect to.

When I was an Access developer, I worked with Access 2K's ADP's, and they
left a lot to be desired. You won't find me recommending ADP's unless folks
are already stuck using MSDE's.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
 
..ADP's work with SQL Server also. MSDE IS SQL Server with a governor to
slow it down when there are more than a few connections. This is to
prevent the free MSDE version from being used in place of the full SQL
version. Otherwise there is no difference.
 
.ADP's work with SQL Server also.

If one has SQL Server, then there is no good reason to use ADP's as a front
end over MDB's, other than it's been developed in the past and there's no
money to build a new front end. ADP's were developed by Microsoft to quell
the complaints about Jet. The implementation fell short of the promise.
Otherwise there is no difference.
Click to expand...

Those of us who aren't good at OSQL notice a difference. There's no license
to use the Enterprise Manager with MSDE, so OSQL is the officially
authorized method of maintaining the back end of MSDE. And the SQL-DMO
library is non-distributable, so creating an interface with this library may
present a problem to those who distribute databases.

Those of us who need more than 2 GB of data in one file notice a difference,
too. SQL Server is capable of handling terabytes, not a mere 2 GB.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
 
This was one of the original reasons for all that
Jet "sandbox" garbage. After the SQL server
security failures that disrupted commerce and
brought the net to it's knees, MS realised that
having a connection from SQL Server to a
database engine which allowed you to Shell out
and run the OS "delete" command was a security
weakness. The first step was to tighten Jet security
and turn off Jet integration for new installations:
then Jet was excluded from MDAC: then service
packs which turned off Jet integration in legacy
installations.

(david)
 
Back
Top