ADP 2000 deployment problems

A

aaron.kempf

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
 
N

Norman Yuan

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).
 
A

aaron.kempf

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
 
A

aaron.kempf

re: 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
 
N

Norman Yuan

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.
 
A

aaron.kempf

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.
 
A

aaron.kempf

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???????
 
N

Norman Yuan

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.
 
A

aaron.kempf

there is a patch required to get ACCESS DATA PROJECTS working against
SQL 2000.

was it included with one of the service packs?

i dont know; i cant find it.

But it's not working.

screw microsoft.. they're too drunk on thier own success to be
successful anymore.
 
A

aaron.kempf

ok you have SP3?

i just coudlnt' figure out what my connection problems are; Windows
didnt' work; SQL authentication didnt work

so i quit the job

not my job to troubleshoot ms products.. thats why i use Access-- is so
that if something goes wrong; it's microsofts job to fix the problem

i had office 2000 sp3 and everything else I needed.

i'm just frustrated; i wish that ADP had been more successful in the
marketplace.

i love them; but my rule has always been 'absolutely no office 2000'
because it's their version 1.0 product

i love xp and 2003 adps-- i just wish that microsoft was more
successful in working out the bugs in ADP

-aaron
 
K

Kevin3NF

No patches, no service packs.

I use 2003 now, since they have improved ADP. 2000 was a version 1 product,
which is a crapshoot for almost any real application. As someone previously
mentioned, this was released before SQL 2000 (I didn't recall that, but
don't doubt it).

Every product form every vendor has bugs. Part of life. Name one other
software manufacturer where the opportunities to make a living are so
prevalent and varied, either by creating with them or supporting them...

--
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
 
N

Norman Yuan

I am just so curiously to know WHAT is exactly the problem you have other
than keeping asking PATCH, which Kevin and I have assured your several times
that it is not a "MUST-HAVE" thing and Access2K ADP DOES work with SQL
Server2K?

After this thread going on this long, I (probably and Kevin, I am sure) am
so puzzled and eager to know if there is something for us to learn from you
that I never run into before on the Access2K adp issue. So, please, give
some details of your technical problem. It is certain, Access2K, as any
other software, contains bugs, but there is no a known bug preventing you
from using it with SQL Server2K, if you really know how to use Access ADP. I
started using Access2K with MSDE1.0 (SQL Server7) and then SQL
Server2K/MSDE2K and felt it is so easy to use that even now I have full SQL
Server with Enterprise Manager, I still use Access ADP as my routine UI to
deal with SQL Server2K.

Could you detail your problem(s) that I may have never run into, so that I
can really learn something new, and if possible, offer some help you may
need on using Access ADP to SQL Server?
 
A

aaron.kempf

it doesnt connect.

i mean-- what do i check; versions of drivers?

i can get this connection to SQL 2k working from Access 2k once someone
has installed the SQL Server client tools

i'm doing this for a oracle/ibm shop so im trying to do this using MSDE
only.

what drivers do i need to install?

i have tried it from multiple machines; nobody has XP SP2
everyone has office 2000 SP3 and i coudn't get it to work (without
purchasing SQL Server)

I dont want to install SQL Server client tools on every machine in the
company.. i mean-- 100k desktops
but uh.. what do i need to do to get Access 2000 ADP working against
SQL 2000 ADP?

So you sit there and tell me i dont need a patch

well it's not working.. and there used to be a Access 2000 SQL 2000
patch

what happened to it; what is it called and isn't it slipstreamed into
Office 2000 SP2 or Office 2000 SP3?

if it's 'supposed to be slipstreamed' how can i tell if that patch is
really there?

ps - what are the limits on machine names.. like seriously.. is 15
characters too long for a SQL Server name?

i tried it with IP; i tried if with sql authenitcation and windows
authentication

POS company won't fix SQL authentication.. boycott microsoft!
 
A

aaron.kempf

says server not found or something like that

i tried it a dozen times.. Windows Authentication or SQL
authentication.. i got it working from my machine just perfectly..

i coudln't get it working agains the trial edition of full SQL 2000. I
coudln't get it to work against MSDE (with DisableNetworkProtocols=0
obviously)

just frustrating... i haven't had a trouble with a connection like this
before

but i guess it's a moot point since i quit that job anyways.. i mean--
thats' why i use Access-- is so that it's Microsofts' job to handle
connection problems.

but they're not holding up their end of the bargain.

it's just frustrating..

i've seen 100 bugs in my days where Microsoft says 'this is a known bug
in Access'

and i just dont see this company taking Access seriously enough.

kinda pisses me off; makes me wish i had focused on Oracle 8 years
ago.. maybe i wouldnt' have to deal with bully companies that put out
crap products (I'm referring to Microsoft; not to Oracle).. i dont know

thats just how i see it-- these jerks won't fix holes in Access because
some Excel dork is in charge of the Access people-- i can tell just by
the way they act.

I just wish that they would take Access seriously.. i mean-- it's the
greatest product of all time
and these jerks refuse to fix holes and bugs left and right

i mean-- anyone else ever use the 'create proc sphappy' syntax as
listed in BOL?

that syntax hoses up ADP and these MS people are too drunk with their
own success to sell reliable products.

-aaron

-aaron
 
A

aaron.kempf

says server not found or something like that

i tried it a dozen times.. Windows Authentication or SQL
authentication.. i got it working from my machine just perfectly..

i coudln't get it working agains the trial edition of full SQL 2000. I
coudln't get it to work against MSDE (with DisableNetworkProtocols=0
obviously)

just frustrating... i haven't had a trouble with a connection like this
before

but i guess it's a moot point since i quit that job anyways.. i mean--
thats' why i use Access-- is so that it's Microsofts' job to handle
connection problems.

but they're not holding up their end of the bargain.

it's just frustrating..

i've seen 100 bugs in my days where Microsoft says 'this is a known bug
in Access'

and i just dont see this company taking Access seriously enough.

kinda pisses me off; makes me wish i had focused on Oracle 8 years
ago.. maybe i wouldnt' have to deal with bully companies that put out
crap products (I'm referring to Microsoft; not to Oracle).. i dont know

thats just how i see it-- these jerks won't fix holes in Access because
some Excel dork is in charge of the Access people-- i can tell just by
the way they act.

I just wish that they would take Access seriously.. i mean-- it's the
greatest product of all time
and these jerks refuse to fix holes and bugs left and right

i mean-- anyone else ever use the 'create proc sphappy' syntax as
listed in BOL?

that syntax hoses up ADP and these MS people are too drunk with their
own success to sell reliable products.

-aaron

-aaron
 
N

Norman Yuan

Again and again, no PATCH is required!!!

OK, go to the point: you cannot connect a SQL Server/MSDE.

Here is what you need:

On the server:

1. Install a SQL Server/MSDE on a computer of your network. If it is MSDE,
make sure its network accessibility is not disabled.
2. Create appropriate SQL Server logins (Whether you use Window integrated
security or mixed security) for expected users.
3. Create database or attach some sample databases (famous "Northwind", for
example) to the SQL Server/MSDE so that you can test
4. Assign proper access permission to users

If you are not sure 2, 3 and 4 aforementioned, I'd suggest you do some study
before rush to Access2xxx project.

On client computer (could be the same computer as the server, if you do if
testing/developing).

1. Make sure you have pretty up-to-date MDAC installed (it comes witth all
cversion of Windows. Just in case you are using Win95/98 where the MDAC
could be too old for SQL Server2K, aren't you? Win2K comes with MDAC2.5,
WinXP - 2.6/2.7/2.8. Very likely, the MDAC on your computer has been already
updated to 2.7 or 2.8 if you have installed some software fromo MS or other
venders. MDAC will install reqired SQL Server client library to the
computer).

2. Start a new Access 2K Project and choose to use existing database.
a. You will be presented a "Data Link Properties" dialog box.
b. Enter correct SQL Server/MSDE name. Note, if you use QL Server
instance name when installing it, you need to enter
"ComputerName\SQLServerInstanceName";
c. Chooes Window security or SQL Server username/password, depending on
how the SQLServer is set up (ask yourself here);
d. You should be able to see a list of available database on the SQL
Server/MSDE for your selection, including "master", "model", "msdb",
"Northwind" (if you attached/installed it). Pick a database you want the ADP
to connect to.
e. Click "test Connection" button to make sure the ADP can connect to
the database you choose.

You are done, if you did things correctly. There is really nothing on the
client computer (hundreds or thousands) need to do, if their Windows are
pretty up-to-date (actaully, even Window95 also OK), no MS Office is
required. Only need Access2K or later to run *.adp file.

I think, in most cases, it is the SQL Server security thing that cause
trouble for novice users, who do not study enough on this topic. SQL Server
is a very important server software and it is very natural strict security
is required. I would not recommend anyone try to use SQL Server/MSDE without
very basic understanding its security. I mean, getting Access project
connected to SQL Server is very easy as long as you set up SQL Server
correctly. It is not a problem of Access2K, it is, probably, your problem on
setting up SQL Server/MSDE, if I dare to guess.

Again, WHAT is exactly your problem other than saying "it does not connect"?
What did you do, step by step? What error you got if you can go several
steps ahead?
 
Top