Just rolled out SQLS 2005. No ADP design?

[addoty]

Hi, I need some good news.

Please tell me this is a simple setting need to make somewhere to
design our views and stored procedues in our Access ADP files. We just
rolled out SQLS 2005 and no one can make any changes to the views? Is
there a patch? We are dead in the water.

Thanks,
AD

 

[addoty]

OMG, I just did a Google Groups seach, NO ADP SUPPORT IN SQL SERVER
2005 ?!?!?

Wow, this was not communicatated very well, at least from what we
received about SQLS 2005.

How do we modify the views and stored procedures? What application can
I install on my developers computers to make modifications? How much
training? What cost?

What's the easiest application to install on my developers computers to
modify views and SPs that is nearest to Access ADP as possible?

You know, being a nearly 100% MS shop it seems like once every couple
years I have one of these mornings where I say, I can't believe we
invested that many resources in this technology.

Unbelievable, Please help!!

 

[Brendan Reynolds]

http://www.microsoft.com/downloads/...59-57a4-455e-a2d6-1d4c98d40f6e&DisplayLang=en

Cost: Nil.

Training: If you're familiar with Enterprise Manager and Query Analyzer,
Nil.

 

[addoty]

Thanks for the quick response, but that is a preview piece of software
and is unsupported.

"Microsoft SQL Server Management Studio Express - Community Technology
Preview November 2005 is unsupported pre-release software."

I have played around with it before moving to SQLS 2005 and it really
is nothing like developing in Access ADP. We ruled it out just from
the development point of view. From what I remember, it doesn't even
support cutting and pasting of the objects.

Is there any other options?

 

[Sylvain Lafontaine]

Well, if you have not the Express Edition but one the commercial
version )(Standard, Enterprise, etc.) then you have the right to install the
client tools and use the real SQL-Server Management Studio, not the Express
one. This version is a fully supported software.

 

[addoty]

Thank you for the response, we have the Standard version.

The Management Studio is HUGE OVERKILL for the simple table, view, SP
designer. It installs the .NET 2.0 framework which we have been trying
to avoid with everything we have. It really bogs down our PCs...at
least 1.0 did and that left a bad taste that just hasn't gone away.
Plus, there are too many options for the simple developer to fiddle
around with. Why do they need to see the "Server Object" branch with
"Endpoints" and "Linked Servers" for example.

Since creating views, stored procedures, tables, etc is simply sending
SQL to the server, why can there not be a simple patch so Access ADP
will work with SQL Server 2005?

Why disenfranchise businesses that have put a lot of resouces (time,
money and training) in purchasing Access? Why? Why? It seems so
simple to fix. Why?

This is horribly dissappointing. Thanks for everyone's help though,
you've been great.

 

[Brendan Reynolds]

If being very similar to Access is an absolute requirement, then I'm afraid
you may be out of luck. I'm not aware of anything that is very similar to
Access.

The other Microsoft tool for developing SQL Server objects that comes to
mind is Visual Studio, but you seemed concerned about cost, and there would
certainly be costs involved in moving to Visual Studio if you don't already
have the licences and/or the familiarity with the product.

There may, of course, be third-party products of which I am not aware.

Are you making a lot of use of new features of SQL Server 2005? If not,
perhaps you could do at least some of your development against MSDE, even if
using SQL Server 2005 in production.

 

[addoty]

Thanks Brendan for the suggestion. We were planning on using a lot of
the new features. I have just informed our management about this
unfortunate situation and luckly we may be able to return to SQL 2000
quickly without many problems. They are going to re-evaluate our
database setup.

I think we have too huge of investment in Access and ADP to go the SQL
2005 route. With FrontPage being dropped and now this Access snafu, it
strikes at the core of our development productivity. Being the head
designer, I've been pushing Microsoft for a long time and our whole
shop is nearly 100% MS. We have upper management that are pseudo IT
people that do not like MS, now I think they see a wedge they can
exploit. Unfortunately I think I'm going to need to learn another
skill set soon.

 

[David Portas]

Thanks Brendan for the suggestion. We were planning on using a lot of
the new features. I have just informed our management about this
unfortunate situation and luckly we may be able to return to SQL 2000
quickly without many problems. They are going to re-evaluate our
database setup.

I think we have too huge of investment in Access and ADP to go the SQL
2005 route. With FrontPage being dropped and now this Access snafu, it
strikes at the core of our development productivity. Being the head
designer, I've been pushing Microsoft for a long time and our whole
shop is nearly 100% MS. We have upper management that are pseudo IT
people that do not like MS, now I think they see a wedge they can
exploit. Unfortunately I think I'm going to need to learn another
skill set soon.

I'm sorry but I find your reasoning difficult to comprehend. You were
planning to use new 2005 features, which presumably would deliver value for
your business, but you have backed off doing that because your developers
can't handle a new UI?!! Don't be daunted by SSMS. It is a far superior
development tool to Access ADP. Just by using it you and your developers
should pick up valuable new skills and you may learn about all the stuff
that was hidden from you by the Access front end (although you can continue
to ignore it if you wish to). That must be worth considering if the
alternative is to throw it all out in favour of a new skill set. I do wonder
what alternative database you have that might be more acceptable to your
development team.

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

 

[aaron.kempf]

HEY **** YOU MVPS ADP IS MUCH SUPERIOR TO 2005

GO USE THE TOOLS BEFORE YOU TALK SHIT

ASSHOLES

Will SSMS even let me view a subquery in design view??

Will SSMS let me bind a form to a sql server database without writing a
single line of code?

Take your SQL 2005 and SHOVE IT MICROSOFT

 

[aaron.kempf]

and Microsoft IS going to come out with a patch for ADP against SQL
Server 2006 lol.

it just pisses me off that you guys all talk shit about ADP without
ever having used the product.

 

[aaron.kempf]

and FURTHERMORE

I have been developing in SQL Server for SEVEN YEARS.

I spend $3000 to learn SQL 2005 last year.

Can i do a single thing in 2005? NOT EVEN CLOSE.

Can i create a simple database and populate it with records?

NOT IF MY LIFE DEPENDED ON IT.

SQL 2005 is just another reflection that Microsoft is run by a bunch of
C++ FAGS.

I dont want visual studio anywhere near my DATABASE. Your bullshit
tools-- they take 3 minutes to LAUNCH.

You MVPs are a bunch of WIMPS. All you do is sit around and say 'oh
microsoft you are so great, i am so glad that you violted every
antitrust rule in the book and now you have an absolute monopoly over
the desktop.

MICROSOFT DOESN'T MAKE QUALITY PRODUCTS ANYMORE AND YOU MVPS WIMPS=-=

Take your ATTITUDE AND SHOVE IT ADP-HATERS!!

-Aaron

 

[aaron.kempf]

Brendan

you are full of shit

and you are full of shit.

TRAINING? SQL 2005? IT'S THE MOST OBNOXIOUS INTERFACE IVE EVER SEEN.

SSMS IS A PIECE OF SHIT PROGRAM-- WHY WOULD WE WANT TO SLOW QUERY
ANALYZER DOWN TO THE LEAST COMMON DENOMINATOR?

I CAN LAUNCH QUERY ANALYZER IN ABOUT 2 SECONDS ON A LAPTOP THAT IS 4
YEARS OLD.

I CAN'T LAUNCH SSMS IN LESS THAN A MINUTE ON ANY MACHINE ANYWHERE.

WHERE DO I WANT TO GO TODAY?

I WANT A FAST, NIMBLE INTERFACE TO SQL 2005.

YOU ASSHOLES NEED TO STOP TALKING SHIT ABOUT ADP.

I CAN OUTDEVELOP THE SHIT OUT OF YOU IN SQL 2000 AND ADP.

I MEAN SIMPLE, COPY AND PASTE.

CAN YOU COPY AND PASTE A VIEW IN 2005?
CAN YOU COPY AND PASTE A TABLE IN 2005?
CAN YOU COPY AND PASTE A SPROC IN 2005?

 

[REMOVE_BEFORE_REPLYING_dportas]

Can i create a simple database and populate it with records?
NOT IF MY LIFE DEPENDED ON IT.

You don't say? Reading the rest of your garbage I can well believe that
your statement is true. Aaron, you need to grow out of kindergarten
first. Meantime keep taking the medication.

 

[aaron.kempf]

hahaha good stuff

 

[aaron.kempf]

i really honestly and sincerely-- want an answer out of you guys

can you copy and paste a view in SSMS?

can you copy and paste a sproc in SSMS?

how about a table?

we've been able to do this in Access Data Projects; and basically-- the
value proposition for us just isn't there yet for SQL 2005.

charge us a shit load of money in order to give us LESS FUNCTIONALITY?

grow up microsoft!

 

[aaron.kempf]

i mean seriously

tell me when i can COPY A VIEW in SQL Server without using an Access
Data Project.

tell me when i can COPY A SPROC in SQL Server.

your grandiose bullshit software is crap; you guys have all the tools
you need

JUST TELL US WHEN AND WHERE ADP PATCH FOR SQL 2005 WILL BE RELEASED!!

 

[Randall Arnold]

As much as I detest Aaron's juvenile approach, his actual points have merit,
sad to say.

MS is not listening to its rank-and-file developer base. That sums it up.

Randall Arnold

 

[Mark Olbert]

As much as I detest Aaron's juvenile approach, his actual points have merit,
sad to say.

MS is not listening to its rank-and-file developer base. That sums it up.

I'll second all of those observations.

- Mark