Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Error using Stored Procedure to retrieve result set in Reports.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Error using Stored Procedure to retrieve result set in Reports.

    I'm trying to execute a Stored Procedure to retrieve data from SQLServer 2008R2 to use as the source for a report.
    The Stored Procedure takes one argument, a date, and should return a range of records determined by the week in the year.

    sqlselect.jpg

    When I try to preview the data whilst specifying the datasource for the report I get the following error -
    Could not execute query against Database. Error reported was: Success
    I went ahead and finished defining the datasource so that I could try previewing the report and I got an almost identical error -
    Could not create ResultSet from DataSource definition. Could not execute query against Database. Error reported was: Success
    I tried calling a different procedure that took no arguments and performed a simple select statement but it returned the same error.
    Does this sound familiar to anyone? So far as I can tell the procedure and calling statement are all syntactically correct.

    #2
    Re: Error using Stored Procedure to retrieve result set in Reports.

    Originally posted by RaEd. View Post
    I'm trying to execute a Stored Procedure to retrieve data from SQLServer 2008R2 to use as the source for a report.
    The Stored Procedure takes one argument, a date, and should return a range of records determined by the week in the year.

    [ATTACH=CONFIG]36382[/ATTACH]

    When I try to preview the data whilst specifying the datasource for the report I get the following error -


    I went ahead and finished defining the datasource so that I could try previewing the report and I got an almost identical error -


    I tried calling a different procedure that took no arguments and performed a simple select statement but it returned the same error.
    Does this sound familiar to anyone? So far as I can tell the procedure and calling statement are all syntactically correct.
    Does the procedure work properly away from the report?
    Glen Schild



    My Blog

    Comment


      #3
      Re: Error using Stored Procedure to retrieve result set in Reports.

      I have executed it before, but just to test I tried running the same procedure in management studio using the following query -

      DECLARE @dateArg date
      SET @dateArg = CONVERT(DATE,'22/07/2013',103)

      EXEC dbo.ReportDailies @dateWeek = @dateArg
      The procedure ran and returned the expected result set, so there doesn't seem to be any issue with the procedure.

      I know that, when entering a query into the datasource wizard, Alpha5 demands that you open with a SELECT statement.
      The procedure in question has two lines before the SELECT -

      BEGIN
      SET NOCOUNT ON;
      SET DATEFIRST 1;

      SELECT...
      Could this have any effect?
      I did try running a procedure that did nothing but use SELECT to retrieve records from a table, but that didn't work either. I'm stuck!
      Last edited by RaEd.; 08-05-2013, 05:17 AM. Reason: typo

      Comment


        #4
        Re: Error using Stored Procedure to retrieve result set in Reports.

        I came back to this after the weekend and took a look at the process that was taking place.

        I checked the permissions for the SQL Server user account that was defined in the connection string and found that there were no permissions for executing Stored Procedures.

        Permission has now been granted and Stored Procedures can be executed no problem.
        Last edited by RaEd.; 08-05-2013, 05:31 AM. Reason: typo

        Comment

        Working...
        X