Help working with poorly named "Stored Procedures"

[Sean]

I am working with an Access application and have a large number of stored
procedures that have been written (primarily) for use within Access and have
been named in a variety of ways. This is troubling with ASP as I am getting
errors...

oCommand.CommandText = <sp_name>

Where <sp_name> is like some of the following. They're being seen as
whatever is read up to the non [A-Z/0-9] character, like "rptCost" fo rthe
first three and "rptCost2006" for the last.

rptCost Summary
rptCost - Total
rptCost North & South
rptCost2006/2007

My question would be is there a way in which I can use the stored
procedures, as they are? This would save renaming them all and recoding the
content of the Access application and as there are literally hundreds of
them in many applications would save an inordinate amount of time.

Many thanks.

[McKirahan]

"Sean" <sean.anderson@[nospam]oakleafgroup.biz> wrote in message
news:11664465...@kestrel.skynet.co.uk...

I have no idea if this will work but you could try enclosing your
stored procedure names in brackets, [ ], as is done with reserved words.

[Sean]

"McKirahan" <Ne...@McKirahan.com> wrote in message
news:m9Odna66sJEM4BrY...@comcast.com...

Tried that and it made no difference.

:o(

[Steve Embry]

Typically, encapsulating the sproc in brackets works fine when calling it
from an ASP page, like:

q = "EXEC [My query name] " & ID & ";"

...perhaps it's only the sprocs with characters like the ampersand that are
still problematic for you after using the brackets....and wouldbe less work
to just change them?

Steve

"McKirahan" <Ne...@McKirahan.com> wrote in message
news:m9Odna66sJEM4BrY...@comcast.com...