SqlServer2005 with Win2k workstations running Access 2003

[CyberDwarf]

Hi

Has anyone out there had any problems running Win2k (SP4)
workstations/Access 2003/SqlServer 2005 in combination?

I have a client reporting connection dropout when loading our shrink-wrapped
Access ADE app, preceded by an error message saying 'class not registered'.

Not sure if this is an Access problem, or a Win2k problem run against the
SQL Server...

Any relevant comments gratefully received

TIA

Steve

 

[Barry Gilbert]

I have an app deployed in that architecture, although mine is an adp. I
haven't had any problems like that.

Barry

 

[aaron.kempf]

wtf you doing with sql 2005?

do you know how to use databases??
sorry; but you need to wait until Access 2007 ships.. I would
definitely call up MS and bitch up a storm though


-Aaron

 

[aaron.kempf]

SQL 2005?

I've had SOME good results; but seriously-- you can't deploy an ADP
against SQL 2005.

I would call MS and bitch up a storm; stand up for what you believe in

I mean; they won't support MSDE on Vista.
So how is it that people are supposed to develop ADP on Vista?

When is SP2 going to ship?

They're totally screwing with us; they need to offer a SQL 2005 patch
for Access 2003; instead of always trying to shove new shit down our
throats.

-Aaron

 

[Graham R Seach]

As I understand, you can't use Access 2003 (or earlier) ADP/ADE against SQL
Server 2005. To use an ADP/ADE with 2005, you must use Access 2007.

Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia

 

[PBsoft]

As I understand, you can't use Access 2003 (or earlier) ADP/ADE

against SQL Server 2005. To use an ADP/ADE with 2005, you must use
Access 2007.

Absolutely not.

You CAN create ADPs with Access 2003, using SQL 2005 as back-end. I did it.
What you CANNOT do is manipulate SQL 2005 objects via Access 2003, because
SQL-DMO has significant changes from previous version.

 

[Barry Gilbert]

PBSoft is correct. However, it sounds like MS is starting to steer people
away from ADP's. This page sums it up pretty well:
http://www.databaseadvisors.com/gazette/sqlexpress.htm

Barry

 

[aaron.kempf]

Barry

you are a liar and a fag.

I'm sorry that you feel the need to draw your own conclusions.

just because ONE DEVELOPER said it in ONE PLACE; does that mean that
ADP aren't a better solution?

START THINKING FOR YOURSELF

ADP is superior in every possible fashion.
Easier development
Easier administration / security
More reliable.

MDB is for crack addicts and fags.

-Aaron

 

[aaron.kempf]

I find it humorous (not humourous) that a friggin MVP doesn't know JACK
SHIT about ADP.

go play with your kangaroos and aborigines; buddy

maybe you can sell them some piece of shit access mdb apps

friggin lamer

-Aaron