Is it possible to connect to Sql Server 2005 using an Access 2000 adp? I
keep trying, but it doesn't want to accept my id, even though it is right.

JA (jarmour at kc.rr.com) writes:
You cannot accuse me for knowing too much Access, but I don't see why
it would not work. (Mind you, I don't even know an ADP is.)

It could help if you post the error message you get and the connection
string you are using.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Hi Erland,

I don't have the original post in my Windows Mail so I am replying to the
group by replying to your post. ADP stands for Access Data (or Database -
It's been a while)
Project. With Access 2000 you had the option to continue use .mdb files
that used primarily JET engine and you could use linked tables to connect
to SQL 2000. Using .adp you were directly connected to the SQL databases
and you could not use JET engine.


JA, it seems you can not use Access 2000 with SQL 2005

http://groups.google.com/groups/sear...0+adp+sql+2005

http://groups.google.com/group/micro...4b34707134f81f


"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote

Thanks Erland and Serge,

I found a program from Microsoft that allows me to do some of what I need to
do (add and populate a new table), without using Access.

It's called the SQL Server Migration Assistant (SSMA) and is free from
Microsoft. You have to have the .Net framework 2.0 or better on your
computer, also J# framework, both are free from Microsoft.

Go to this blog for info and a step-by-step Word doc on how to do it.
http://cfpayne.wordpress.com/2006/07...l-server-2005/

He says you need to dl Sql Server 2005 to your machine, but I used it (SSMA)
without doing that.







"serge" <sergea (AT) nospam (DOT) ehmail.com> wrote

They have an SSMA for MS Access too?

I've used SSMA to migrate Oracle databases and I was happy with the product
since it was easy to use to migrate the data. I only had to migrate the
data.
Converting PL/SQL to T-SQL didn't seem to be 100% efficient but in my
case I didn't need to convert code also.

So as long as it worked for you to get the job done, then it's good.