By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,264 Members | 1,795 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,264 IT Pros & Developers. It's quick & easy.

CREATE PROC syntax in ADP

P: n/a
I find that ADP does not support any Stored Procedures that use the 'CREATE
PROC spHAPPY' syntax.

CREATE PROC syntax is listed in books online.
This syntax should be supported

Here is a scenario:

1) create proc using query analyzer and CREATE PROC spHAPPY syntax
2) open this proc in ADP
3) make changes to proc
4) try to save and you get the 'Parameter is incorrect' error.

can we PLEASE get someone to fix this; and stop giving excuses??
Nov 13 '05 #1
Share this Question
Share on Google+
14 Replies


P: n/a
ADPs, as far as I know, do not themselves have "stored procedures". That's
not an "excuse", it is a fact. An ADP is a "front-end" to a database, not
itself a database.

Do you want to create a Stored Procedure in the SQL Server database that the
ADP is using as a datastore? You'd do that in SQL's dialect of DDL SQL, and
it is certainly possible, provided you have appropriate permissions.

Larry Linson
Microsoft Access MVP

"aaron kempf" <aa*********@gmail.com> wrote in message
news:2f**************************@posting.google.c om...
I find that ADP does not support any Stored Procedures that use the 'CREATE PROC spHAPPY' syntax.

CREATE PROC syntax is listed in books online.
This syntax should be supported

Here is a scenario:

1) create proc using query analyzer and CREATE PROC spHAPPY syntax
2) open this proc in ADP
3) make changes to proc
4) try to save and you get the 'Parameter is incorrect' error.

can we PLEASE get someone to fix this; and stop giving excuses??

Nov 13 '05 #2

P: n/a

"aaron kempf" <aa*********@gmail.com> wrote in message
news:2f**************************@posting.google.c om...
I find that ADP does not support any Stored Procedures that use the 'CREATE
PROC spHAPPY' syntax.

CREATE PROC syntax is listed in books online.
This syntax should be supported

Here is a scenario:

1) create proc using query analyzer and CREATE PROC spHAPPY syntax
2) open this proc in ADP
3) make changes to proc
4) try to save and you get the 'Parameter is incorrect' error.

can we PLEASE get someone to fix this; and stop giving excuses??

Not that we need to, but we are entitled to give as many excuses as we like.
How about this one:
"We do not owe free consultation to people who do not know the basics of
stored procedures and adp's."

and PLEASE don't multi-post.


Nov 13 '05 #3

P: n/a
Wow. I didn't think that there were that many idiots left in this
world.

1) I double-post in this newsgroup, because MICROSOFT CENSORS THEIR
NEWSGROUP.
I just learned this.

2) of course I know that ADPs don't store the sproc in the ADP file--
it is in the SQL Server database.

a). Create a sproc with query analyzer using the 'CREATE PROC SPHAPPY
AS SELECT * FROM SYSOBJECTS'

b). Open this sproc in ADP and in design view, change this to saw
"SELECT * FROM SYSOBJECTS WHERE XTYPE = 'U'

c). Try to save your changes; and you will get an error 'the parameter
is incorrect'

I have told Microsoft about this 100 times; and I have to deal with
this bug 10 times per day.

It just pisses me off that Microsoft can't fix a serious problem in
their most profitable business line.

And what pisses me off more, is that you ACCESS MVP DON'T KNOW
_ANYTHING_ ABOUT ADP.

SCREW MDB. SCREW MVP's THAT DONT KNOW ENOUGH ABOUT ADP.


"Tom Travolta" <to*@travolta.com> wrote in message news:<co**********@hercules.btinternet.com>...
"aaron kempf" <aa*********@gmail.com> wrote in message
news:2f**************************@posting.google.c om...
I find that ADP does not support any Stored Procedures that use the 'CREATE
PROC spHAPPY' syntax.

CREATE PROC syntax is listed in books online.
This syntax should be supported

Here is a scenario:

1) create proc using query analyzer and CREATE PROC spHAPPY syntax
2) open this proc in ADP
3) make changes to proc
4) try to save and you get the 'Parameter is incorrect' error.

can we PLEASE get someone to fix this; and stop giving excuses??

Not that we need to, but we are entitled to give as many excuses as we like.
How about this one:
"We do not owe free consultation to people who do not know the basics of
stored procedures and adp's."

and PLEASE don't multi-post.

Nov 13 '05 #4

P: n/a
AND I AM NOT ASKING FOR FREE CONSULTATION

I AM ASKING FOR MICROSOFT TO FIX BUGS IN THIER PRODUCTS



"Tom Travolta" <to*@travolta.com> wrote in message news:<co**********@hercules.btinternet.com>...
"aaron kempf" <aa*********@gmail.com> wrote in message
news:2f**************************@posting.google.c om...
I find that ADP does not support any Stored Procedures that use the 'CREATE
PROC spHAPPY' syntax.

CREATE PROC syntax is listed in books online.
This syntax should be supported

Here is a scenario:

1) create proc using query analyzer and CREATE PROC spHAPPY syntax
2) open this proc in ADP
3) make changes to proc
4) try to save and you get the 'Parameter is incorrect' error.

can we PLEASE get someone to fix this; and stop giving excuses??

Not that we need to, but we are entitled to give as many excuses as we like.
How about this one:
"We do not owe free consultation to people who do not know the basics of
stored procedures and adp's."

and PLEASE don't multi-post.

Nov 13 '05 #5

P: n/a
aaron kempf wrote:
AND I AM NOT ASKING FOR FREE CONSULTATION

I AM ASKING FOR MICROSOFT TO FIX BUGS IN THIER PRODUCTS


That will do.
Nov 13 '05 #6

P: n/a
"aaron kempf" wrote
And what pisses me off more, is that
you ACCESS MVP DON'T KNOW
_ANYTHING_ ABOUT ADP.

SCREW MDB. SCREW MVP's
THAT DONT KNOW ENOUGH
ABOUT ADP.


You are entitled to your opinion.

This MVP knows that knowledgeable Microsoft insiders, including one former
Product Manager for ADP in a previous release, now suggest that, in general,
MDB-Jet-ODBC-SQL Server is preferrable to ADP-ADODB-SQL Server.

I did, in fact, have my hype-repellent working, so I avoided jumping in
feet-first just because Microsoft was, at the time of Access 2000, pushing
ADP. In fact, when I did work with an ADP because of client needs, I was
confirmed in my belief that they were not _better_ than MDB, only
different -- then that was further confirmed by statements from Microsoft.

If, indeed, you knew, why did you not say that you knew the Stored
Procedures were stored in SQL Server, not in the ADP, instead of leaving the
impression that you thought otherwise? After all, we cannot know what you
are thinking, or what you know, but only what you post here.

If you expect to get useful answers to future posts here, I suggest you read
the FAQ at http://www.mvps.org/access/netiquette.htm for suggestions on
effective use of newsgroups. I have, just for the record, not seen anyone
ever barred from Microsoft newsgroups for being critical of Microsoft, but
only for misbehavior -- perhaps you are an exception to that "rule", perhaps
not, given your posts here.

Larry Linson
A founding member of comp.databases.ms-access, and
a Microsoft Access MVP
Nov 13 '05 #7

P: n/a
"aaron kempf" <aa*********@gmail.com> wrote
I AM ASKING FOR MICROSOFT
TO FIX BUGS IN THIER PRODUCTS


As I may have said before, the USENET newsgroup comp.databases.ms-access is
not a newsgroup that Microsoft monitors, so you are wasting your typing
fingertips asking here.

I would suggest, since you seem to think you are banned from the
Microsoft-sponsored newsgroups (which, perhaps surprisingly, are mostly also
not monitored by Microsoft personnel), a snail-mail letter to either Bill
Gates, Chairman of the Board, or Steve Ballmer, President and CEO, of
Microsoft, explaining that you have a problem, with a detailed explanation
as an attachment, and requesting that they look into the matter.

I can assure you that the language you used here "S***W YOU" is not likely
to encourage anyone to assist.

Larry Linson
a founding member of comp.databases.ms-access, and
a Microsoft Access MVP

Nov 13 '05 #8

P: n/a
Larry;

I am sorry, but i know for a FACT that I was censored on the
Microsoft.public newsgroup.

Eat shit if you don't believe me.

I know for a FACT that ADPs are more powerful that MDBs.

I know it firsthand.

I am sorry that MDB is still an option-- I think that it should have
been killed a long time ago.

SQL Server is 10x better at Data Storage than access.

ADP Reports-- are 10x more powerful than Crystal Reports.

I AM OUTRAGED THAT MICROSOFT WON'T FIX THIS CREATE PROC PROBLEM.

I DEMAND THAT MICROSOFT EITHER FIX THE BUG-- FIX THE BUG IN YOUR
PRODUCT; OR GIVE US THE SOURCE CODE SO THAT WE CAN DO IT. Spin off
ADP into a seperate product.

MICROSOFT IS BENDING US ALL OVER BACKWARDS

AND YOU LIL MDB FAIRIES DON'T CARE.



"Larry Linson" <bo*****@localhost.not> wrote in message news:<LzPpd.76$wr6.11@trnddc04>...
"aaron kempf" <aa*********@gmail.com> wrote
> I AM ASKING FOR MICROSOFT
> TO FIX BUGS IN THIER PRODUCTS


As I may have said before, the USENET newsgroup comp.databases.ms-access is
not a newsgroup that Microsoft monitors, so you are wasting your typing
fingertips asking here.

I would suggest, since you seem to think you are banned from the
Microsoft-sponsored newsgroups (which, perhaps surprisingly, are mostly also
not monitored by Microsoft personnel), a snail-mail letter to either Bill
Gates, Chairman of the Board, or Steve Ballmer, President and CEO, of
Microsoft, explaining that you have a problem, with a detailed explanation
as an attachment, and requesting that they look into the matter.

I can assure you that the language you used here "S***W YOU" is not likely
to encourage anyone to assist.

Larry Linson
a founding member of comp.databases.ms-access, and
a Microsoft Access MVP

Nov 13 '05 #9

P: n/a
"aaron kempf" wrote
I am sorry, .
Whether you are a sorry sort or just an obnoxious troll, I can't determine,
but perhaps this is one thing I can take your word for.
but i know for a FACT
that I was censored on the
Microsoft.public newsgroup.
Eat shit if you don't believe me


You have claimed to know a number of things 'for a fact' that are not so.

Here are three facts that are so -- (1) foul language will get you nowhere
in this newsgroup, though they may draw complaints to your ISP and news
server; (2) the demands you are making in this newsgroup will not get the
attention of any responsible party in Microsoft; and (3) I consider you such
a collosal waste that I am not going to bother to respond to you further.

Thus, if you want it, you can have the last word. G'nite.
Nov 13 '05 #10

P: n/a
just for the record:

http://groups.google.com/groups?q=aa...phx.gbl&rnum=3

this is the link, in microsoft.public.access where Microsoft censored
me. So don't you go about telling me who censors me and who doesn't.

I don't care how bad i ramble-- microsoft has major issues.. they have
buggy programs; and they're refusing to do anything about it.

Microsoft is a bully and someone needs to kick their ass in the open
marketplace-- teach them that they're not invincible.

They're too proud to fix problems in their products.

I just want some CLARIFICATION on what is happening with ADP;
Microsoft kept on telling me that it is being 'depecreated in Office
12' but they don't bother to tell me EXACTLY what that means.

I found MAJOR BUGS IN ADP-- RANDOM EXECUTE OF STORED PROCEDURES IS NOT
ACCEPTABLE. ADP RANDOMLY EXECUTES STORED PROCS!!!!

I've been bitching about it for a year.. And Microsoft can't fix thier
products..

So I am done; I am going to take some classes on Oracle or something

Aaron Kempf
OLAP Developer
ADP Nationalist


aa*********@gmail.com (aaron kempf) wrote in message news:<2f**************************@posting.google. com>...
Wow. I didn't think that there were that many idiots left in this
world.

1) I double-post in this newsgroup, because MICROSOFT CENSORS THEIR
NEWSGROUP.
I just learned this.

2) of course I know that ADPs don't store the sproc in the ADP file--
it is in the SQL Server database.

a). Create a sproc with query analyzer using the 'CREATE PROC SPHAPPY
AS SELECT * FROM SYSOBJECTS'

b). Open this sproc in ADP and in design view, change this to saw
"SELECT * FROM SYSOBJECTS WHERE XTYPE = 'U'

c). Try to save your changes; and you will get an error 'the parameter
is incorrect'

I have told Microsoft about this 100 times; and I have to deal with
this bug 10 times per day.

It just pisses me off that Microsoft can't fix a serious problem in
their most profitable business line.

And what pisses me off more, is that you ACCESS MVP DON'T KNOW
_ANYTHING_ ABOUT ADP.

SCREW MDB. SCREW MVP's THAT DONT KNOW ENOUGH ABOUT ADP.


"Tom Travolta" <to*@travolta.com> wrote in message news:<co**********@hercules.btinternet.com>...
"aaron kempf" <aa*********@gmail.com> wrote in message
news:2f**************************@posting.google.c om...
I find that ADP does not support any Stored Procedures that use the 'CREATE
PROC spHAPPY' syntax.

CREATE PROC syntax is listed in books online.
This syntax should be supported

Here is a scenario:

1) create proc using query analyzer and CREATE PROC spHAPPY syntax
2) open this proc in ADP
3) make changes to proc
4) try to save and you get the 'Parameter is incorrect' error.

can we PLEASE get someone to fix this; and stop giving excuses??

Not that we need to, but we are entitled to give as many excuses as we like.
How about this one:
"We do not owe free consultation to people who do not know the basics of
stored procedures and adp's."

and PLEASE don't multi-post.

Nov 13 '05 #11

P: n/a
"aaron kempf" <aa*********@gmail.com> wrote
just for the record:

http://groups.google.com/groups?q=aaron.kempf% 40gmail.com&hl=en&lr=&selm=Ou8g5md0EHA.1524%40TK2M SFTNGP09.phx.gbl&rnum=3
this is the link, in microsoft.public.access
where Microsoft censored me. So don't
you go about telling me who censors me
and who doesn't.
I see nothing in all 17 posts in that thread to indicate that (1) you were
censored or (2) that any Microsoft person posted to the thread at all. Could
you clarify just what in that thread indicates that Microsoft censored you?

.. . .
I just want some CLARIFICATION on
what is happening with ADP; Microsoft
kept on telling me that it is being 'depecreated
in Office 12' but they don't bother to tell
me EXACTLY what that means.
"Deprecated", in Redmond-speak, means they are no longer recommending you
use that feature, that you do it another way. That other way could only be
MDB or DAP, since those are the only other two options in Access. It
_implies_, too, that they don't have plans to exert a great deal of effort
on that feature/function because they think you ought to do it another way.
So, I fear you are screaming your demands into a strong wind blowing the
other way from Redmond.

Perhaps the statement that they are deprecating ADP might be translated to
"we thought this was a good idea, and we implemented it, but it didn't
really turn out as well as we had hoped, so we aren't going to do any more
with it", but perhaps there are other equally probable translations, too. I
doubt Microsoft is likely to endorse my translation, though. <G>

....
So I am done; I am going to take some
classes on Oracle or something


Good luck. Oracle is a server database, like Microsoft SQL Server, not a
user interface tool. Oracle does make an application server and has an
"Oracle Forms" capability, but those are far too complex, and thus far too
expensive, for most individuals or even smaller organizations, and not
useful except with Oracle databases, if memory serves. Sybase's PowerBuilder
is a front-end creation tool, but your clients or your employer will have to
have support for it on their systems. It, too, would be significantly more
expensive than Access.

If you are looking for a next-generation development environment to interact
with Microsoft databases, you might want to look into Visual Studio.NET's
VB.NET, C#, and ASP.NET. Borland, among others, also plans to have some
..NET-compatible development tools. And, there are open-source projects to
address .NET development.

Larry Linson
Microsoft Access MVP

Nov 13 '05 #12

P: n/a
"aaron kempf" wrote
just for the record:

http://groups.google.com/groups?q=aaron.kempf% 40gmail.com&hl=en&lr=&selm=Ou8g5md0EHA.1524%40TK2M SFTNGP09.phx.gbl&rnum=3
this is the link, in microsoft.public.access
where Microsoft censored me. So don't
you go about telling me who censors me
and who doesn't.

It appears that you added microsoft.public.access to the newsgroups in the
post to which I am responding, that it did appear in
microsoft.public.access -- and that is inconsistent with your being censored
or blocked. I see a number of other posts from you in this same newsgroup.
Nov 13 '05 #13

P: n/a
Listen Larry

When i fucking say i got censored; i got fucking censored.

don't you try to fucking double-talk me.

don't you try to put words in my mouth.

there was at least one posting that microsoft published and then
yanked-- and i don't think that is very open-minded.

I never said that 'every post was censored'

so don't try to stick up for a disaeased company that won't fix MAJOR
holes in their products.

I say i got censored-- I got censored. End of fucking story. If you
don't believe me; then I got a knuckle sandwich for you... Calling me
a liar-- shit...

Do you really think that I'm just screaming at the wind??

Microsoft is bullying and screwing customers and nobody will do a damn
thing about it. And they're trying to silence critics. Sounds pretty
1984 to me.

I think that I'm going to go and listen to some Dead Kennedys or
something.. cuz Microsoft has pissed me off so bad--- I mean.. I
demand a OPEN AND HONEST REVIEW ABOUT WHO THE HELL LET THIS PRODUCT
(ADP) SHIP WITHOUT TESTING THE 'CREATE PROC' SYNTAX.

IF IT WASN'T TESTED; FIRE EVERY TESTER ON THAT PROJECT, NO MATTER
WHERE THEY ARE NOW.

IF IT WAS TESTED AND IGNORED; GIVE US SOMEONES' HEAD.

IT ISN'T ACCEPTABLE TO HAVE MAJOR HOLES IN PRODUCTS AND NOT DO
ANYTHING ABOUT IT. IT ISN'T ACCEPTABLE TO SAY 'NO' WHEN WE COME TO
YOU WITH A BUG THAT IS SERIOUS. I DON'T CARE HOW MUCH WORK YOU HAVE,
MICROSOFT-- STOP THIS BULLSHIT OF TRYING TO SELL US A NEW VERSION OF
OFFICE EVERY 18 MONTHS AND START FUCKING FIXING PROBLEMS IN YOUR
CURRENT PRODUCTS.

IT IS TIME FOR SOME ACCOUNTABILITY, MICROSOFT.

1) FIX THE FUCKING PROBLEM
2) DON'T FUCKING GIVE US GRIEF WHEN WE FIND BUGS IN YOUR PRODUCTS
3) START LISTENING TO YOUR FUCKING CUSTOMERS, EVEN IF (AND WHEN) THEY
ARE SWEARING (or typing in uppercase-- haha get a life techies.. it
isn't yelling, im only using uppercase).

Oh, is microsoft, the richest company in the world-- scared of a few
lil swear words.. HAHAHAHAHAHAHAHAHAHAHAHAHAHA


"Larry Linson" <bo*****@localhost.not> wrote in message news:<tTusd.884$S33.451@trnddc03>...
"aaron kempf" wrote
> just for the record:
>
> http://groups.google.com/groups?q=aaron.kempf%

40gmail.com&hl=en&lr=&selm=Ou8g5md0EHA.1524%40TK2M SFTNGP09.phx.gbl&rnum=3
>
> this is the link, in microsoft.public.access
> where Microsoft censored me. So don't
> you go about telling me who censors me
> and who doesn't.

It appears that you added microsoft.public.access to the newsgroups in the
post to which I am responding, that it did appear in
microsoft.public.access -- and that is inconsistent with your being censored
or blocked. I see a number of other posts from you in this same newsgroup.

Nov 13 '05 #14

P: n/a
"aaron kempf" <aa*********@gmail.com> wrote
Listen Larry

When i f***ing say i got censored;
i got f***ing censored.

Aaron, I will be frank with you -- I don't give a big rip whether Microsoft
censors you or not; they don't have to in order for me to disregard your
posts... not many people earn a spot in my twitfilter list, but you just
have.

It is written that "a soft answer turneth away wrath". So, to give you this
good advice in parting, I will speak very ---softly---, "Don't plan on your
current approach getting anything fixed. If you want to complain and have a
chance your complaint will be acted upon, write a letter to Bill Gates or
Steve Ballmer, using civil and decent language. If you just want to spew in
the newsgroups, continue with what you are doing."

Microsoft has no control over comp.databases.ms-access, so they can't censor
you here. Whether anyone will continue to read your irrational rants is
another question, entirely.

Nov 13 '05 #15

This discussion thread is closed

Replies have been disabled for this discussion.