Access and SQL05

[Ana_T]

Hi,

I'm using Acc03 sp2 to connect to SQL05. However, a message alerts me that I've
an older version and that I cannot modify the content of SQL server 2005.
Sp2 is the latest version so, HOWTO get around?

TIA

Ana

 

[Norman Yuan]

You can manupulate data in the SQL Server database with Access2003 as front
end (*.mdb or *.adp), but you cannot create/modify SQL Server's server side
objects (table, view, SP, UDF....). No update will ever be available for
Access2003 or older for doing this. The only work around is do buy
Access2007 when it is released soon sometime early next year.

 

[Mike]

Have the same problem. However worked fine with sql2k. It's not right that
we'll be forced to purchase a new version.
Mike.

 

[aaron.kempf]

Yes; I agree may the gods rain down fire in Redmond.

They TOTALLY betrayed us on this one.

-Tom

 

[Norman Yuan]

As Access application user, you are not forced to buy new version, Access
2003, or 2002, or even 2000, can use used as front-end to a SQL Server2005
back-end, as long as the Access app works, or should I say, developed
properly.

You simply cannot use Access 2003 to manipulate SQL Sever2005's server-side
objects, as developer (you wouldn't want app user to touch server-side
objects, would you?). It is understandable that Access2003 does not have the
full capability to deal with SQL Server2005: it was release almost 3 years
earlier than SQL Server2005.

If you as developer, want to develop SQL Server2005 application, you would
need a better tool to deal with SQL Server2005 server-side objects than
Access anyway. SQL Server2005 comses the SQL Server management studio, as
you may already know. Or you can wait for Access 2007, which might be a
basic tool for an Access and SQL Server2005 developer, IMO.

 

[dbahooker]

Norman;

I disagree with your diagnosis.

There are PLENTY of reasons not to use ADP with SQL 2005.. for example;
you can't properly use extended properties in all circumstances.

Microsoft is a bunch of fat lazy assholes and they can screw themselves
for not supporting Access 2003 ADP on SQL 2005

Do you even know how to spell ADP, Norman?

-Aaron

 

[dbahooker]

and for the record; ADP _SUPPORTS_MORE_FUNCTIONALITY_ than Enterprise
Manager.. or Query Analyzer.. or even SQL Server Management Studio 2005


can you copy and paste sprocs / views in any of those other tools?

Norman; why dont you STFU and start pressuring Microsoft to deliver a
PATCH.

this from the company that made SQL 2000 and Access 2000 incompatabile.

WHAT A JOKE

This company needs to start delivering a simple, reasonable MARKETING
MESSAGE.
ADP is the most important tool to ever come out of Redmond and the
dipshits in redmond are too drunk / blind to even know what it is.

-Aaron

 

[aaron.kempf]

I disagree with the tone of your post, Norman.

'properly designed' does not mean that it's built with MDB.

MDB is obsolete; and it is dead. anyone using MDB for anything should
be fired and spit upon.

-Aaron
It's no longer the 90s' bitches!

 

[aaron.kempf]

Norman;

and I really dont understand where in the hell you come up with this:
you wouldn't want app user to touch server-side

objects, would you?

I strongly disagree with that statement; of COURSE we want our end
users to be able to write views / sprocs

THAT IS THE POINT OF ADP.

I didn't say that we're going to let them edit existing objects; but
yes-- end users SHOULD be able to create view views / sprocs...

Maybe that's the big point that you kids still dont understand about
ADP..

End User Queries shouldn't be written in MDB; use ADP everything is
simpler

-Aaron