Wrox Programmer Forums
| Search | Today's Posts | Mark Forums Read
Classic ASP Professional For advanced coder questions in ASP 3. NOT for ASP.NET 1.0, 1.1, or 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Classic ASP Professional section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
  #1 (permalink)  
Old December 18th, 2006, 09:54 AM
Friend of Wrox
 
Join Date: Oct 2006
Location: Northampton, Northants, United Kingdom.
Posts: 114
Thanks: 0
Thanked 0 Times in 0 Posts
Default Working with poor named Access procedures

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.

(apologies for xpost)

Regards,

Sean Anderson
__________________
Regards,

Sean Anderson
  #2 (permalink)  
Old December 18th, 2006, 05:38 PM
Friend of Wrox
Points: 6,664, Level: 34
Points: 6,664, Level: 34 Points: 6,664, Level: 34 Points: 6,664, Level: 34
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jan 2004
Location: Sydney, NSW, Australia.
Posts: 1,870
Thanks: 12
Thanked 20 Times in 20 Posts
Send a message via AIM to mat41
Default

I dont understand why they are troubling you, nor what your problem is

Wind is your friend
Matt
  #3 (permalink)  
Old December 19th, 2006, 05:25 AM
Friend of Wrox
 
Join Date: Oct 2006
Location: Northampton, Northants, United Kingdom.
Posts: 114
Thanks: 0
Thanked 0 Times in 0 Posts
Default

The following code:

Set oCommand = Server.CreateObject("ADODB.Command")
Set oCommand.ActiveConnection = cn
    oCommand.CommandType = 4
    oCommand.CommandText = "rptCost Summary"
    Set rsData = oCommand.Execute

Leads to the following error:

Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E37)
[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot find the input table or query 'rptCost'. Make sure it exists and that its name is spelled correctly.

Regards,

Sean Anderson
  #4 (permalink)  
Old December 24th, 2006, 12:42 PM
Friend of Wrox
 
Join Date: May 2006
Location: San Diego, CA, USA.
Posts: 643
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Try enclosing the name in square brackets:
oCommand.CommandText = "[rptCost Summary]"


Woody Z
http://www.learntoprogramnow.com


Similar Threads
Thread Thread Starter Forum Replies Last Post
Stored Procedures; handling poorly named procedure seananderson Classic ASP Databases 0 December 18th, 2006 08:06 AM
Stored Procedures not working in Server Explorer hexOffender VB Databases Basics 2 October 13th, 2006 09:52 AM
poor perfomance using Access front end to SQL tanjuakio Access 24 April 19th, 2005 07:21 AM
Access 2002 VBA book quality poor celletay Wrox Book Feedback 9 May 21st, 2004 07:35 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.