ADP 2000 deployment problems

so i've got a SQL 2000 trail edition on my desktop; trying to get
someone else to connect via Access 2000 Data Projects.

Wasn't the SQL2000/Access2000 patch included with Office 2000 SP3?

how can i tell if that patch is installed?

any other clues?

thanks

-aaron

What patch?

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.

www.experts-exchange.com - experts compete for points to answer your
questions


wrote in message
oups.com...
so i've got a SQL 2000 trail edition on my desktop; trying to get
someone else to connect via Access 2000 Data Projects.

Wasn't the SQL2000/Access2000 patch included with Office 2000 SP3?

how can i tell if that patch is installed?

any other clues?

thanks

-aaron

If your SQL Server is installed correctly and the "someone else" are
networked to your computer, they only need Access2000 or later, nothing
else. What problem do you have? Why ask "patch"?

You simply do:

1. Copy the Access Project file (*.adp) to the other computer;
2. Double-click to start it. if the connection setting in the file is
connect, you are done. If the connection setting is not correct (for
example, when you work with it on your computer, you may have specified the
SQL Server name as "(local)" instead of a server name), then the Acceess
project will take some time to start, trying to connect to the server (of
course, it cannot get connected, in this case). After about 30 second, the
Access project will be started without being connected to SQL Server (you
will see forms, reports, code modules, but not tables, views, sps). Then,
you click menu "File-Connection..." to connect the Access project to the
SQL Server on your computer (or on any other computer networked).

wrote in message
oups.com...
so i've got a SQL 2000 trail edition on my desktop; trying to get
someone else to connect via Access 2000 Data Projects.

Wasn't the SQL2000/Access2000 patch included with Office 2000 SP3?

how can i tell if that patch is installed?

any other clues?

thanks

-aaron

yeah i just can't get it to connect and im under the gun and i need it
to connect

and it's a standard corporate desktop; i dont have time to fix patches
you know what i mean?

i just know it works MUCH better than i remembered in Access 2000 on my
local machine.. It's a named instance..

do i need to put servername\$instancename in the connection box?

or just servername\instancename?

anything else i need to do to get a named instance to work correctly
with ADP?



-aaron

what patch..

the uh.. patch that allows Access _2000_ to work with SQL Server
_2000_.

I just can't believe that they won't let the left hand talk to the
right hand
i mean-- ridiuclous that Access 2000 and SQL 2000 aren't best of
friends

Again, no "patch" issue here. Simply make sure you enter the correct server
name: "ServerComputerName" or "ServerComputerName\SQLInstanceName". If you
enter all information correctly in "Data Link Properties" dialog box, you
should get connected. Make sure the user from other computer has permission
to log in (Windows security or SQL Login, depending on the SQL Server
configuration).

What exactly is happening that you cannot connect? Error message? Nothing at
all? Prompt for "patch"?. What OS? Old Win95? The only thing needed is MS
Data Access Components (Mdac_type.exe), which comes with all Windows
version. If your OS is Win95/98, you may want to may sure to update it to
newer version (2.8 is the latest, free download. Also, since Access2K was
release before SQL Server 2000, there may be some issues, but it is not
likely your problem (what problem other than crying for "patch"?). I used
Access 2K to connect SQL Server/MSDE for years, from Win98, 2K, XP, Windows
Server2003, without issue.

wrote in message
oups.com...
yeah i just can't get it to connect and im under the gun and i need it
to connect

and it's a standard corporate desktop; i dont have time to fix patches
you know what i mean?

i just know it works MUCH better than i remembered in Access 2000 on my
local machine.. It's a named instance..

do i need to put servername\$instancename in the connection box?

or just servername\instancename?

anything else i need to do to get a named instance to work correctly
with ADP?



-aaron

it is a Windows XP machine.

Without SP2.

and it's a Office 2000 SP3 install.

Isn't there a patch required for Access 2000 ADP to work with SQL
Server 2000?

Again, the PM that approved that concept should be fired; Access 2000
_should_ plug into SQL 2000 without a problem.

God, i wish that MS would take Access seriously.

Excel is a disease; and it thrives because Microsoft doesn't take
Access seriously.

it is a Windows XP machine.

Without SP2.

and it's a Office 2000 SP3 install.

Isn't there a patch required for Access 2000 ADP to work with SQL
Server 2000?

Again, the PM that approved that concept should be fired; Access 2000
_should_ plug into SQL 2000 without a problem.

God, i wish that MS would take Access seriously.

Excel is a disease; and it thrives because Microsoft doesn't take
Access seriously.

AND YOU'RE DEFINITELY TALKING ABOUT ACCESS DATA PROJECTS RIGHT???????
AND YOU'RE DEFINITELY TALKING ABOUT ACCESS DATA PROJECTS RIGHT???????
AND YOU'RE DEFINITELY TALKING ABOUT ACCESS DATA PROJECTS RIGHT???????

No, there's not a patch required
It does
They do
Excel is an outstanding tool when used for the correct purpose

Would you care to give us some actual error messages or a link to where you
saw that there is a patch required?

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.

www.experts-exchange.com - experts compete for points to answer your
questions


wrote in message
oups.com...
it is a Windows XP machine.

Without SP2.

and it's a Office 2000 SP3 install.

Isn't there a patch required for Access 2000 ADP to work with SQL
Server 2000?

Again, the PM that approved that concept should be fired; Access 2000
_should_ plug into SQL 2000 without a problem.

God, i wish that MS would take Access seriously.

Excel is a disease; and it thrives because Microsoft doesn't take
Access seriously.

Again, and again, if you really know what you are talking, or asking, no
"patch" issue. Please detail what exactly is your problem. Something that
you cannot make it work, while thousands other make it work very well, does
not necessarily mean the product is bad. Do your study first.

Access2K project works with SQL Sever2000 fairly well, although Asscess2K
was released before SQL Sever 2K and there is an downloadable update to make
Access2K more compatible to SQL Server, but it is not a "Must Have" thing.

If you can get you started on Access2K project, and run into problem, focus
on the problem, rather than keep asking "patch". If you simply cannot get
started, Access Help is good place to get started. I can only assure you
that Access2K WORKS with SQL Server2K.

wrote in message
oups.com...
it is a Windows XP machine.

Without SP2.

and it's a Office 2000 SP3 install.

Isn't there a patch required for Access 2000 ADP to work with SQL
Server 2000?

Again, the PM that approved that concept should be fired; Access 2000
_should_ plug into SQL 2000 without a problem.

God, i wish that MS would take Access seriously.

Excel is a disease; and it thrives because Microsoft doesn't take
Access seriously.