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

SQL Builder truncation?

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

    SQL Builder truncation?

    Whisky, Tango, Foxtrot!!!!

    I copy and paste a large (confirmed-working) SQL statement (including a UNION) into the SQL Builder "SQL Text" tab. Seventeen (17) lines appear - just as they should.

    (see http://msgboard.alphasoftware.com/al...ad.php?t=80406 for an idea of general structure)

    I click "Preview Query", and data is returned precisely as I expect it to be.

    Then, with everything being absolutely perfect, I click "OK".

    BUT THEN...

    Alpha Five strips off EVERYTHING... EVERY SINGLE LINE beyond the first six lines. It strips everything, all eleven lines, from UNION onward.

    This is not nice!

    What can I do to fix this?
    Last edited by fsi; 07-12-2009, 12:13 PM.

    #2
    Re: SQL Builder truncation?

    Choose stored procedure and Alpha won't try to change the SQL to a 'standard'..
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


      #3
      Re: SQL Builder truncation?

      This is an ODBC connection, by the way.

      This is the procedure I am following (perhaps it is incorrect):

      New->Web Component->Grid

      Grid->Data Source = Remote, via AlphDAO
      Choose connection name from drop down. CONNECT (successful)

      Base on: SQL Statement (my v9 edition does not explicitly include Stored Proc as option)

      Click Edit SQL

      Click SQL Text tab, copy & paste into box.

      Preview (perfect!)

      Click OK (truncation occurs)


      NOW... I have since created a stored proc on the DB server.
      If I execute
      select * from "My_Proc"(arg1,arg2)
      in my SQL IDE, it returns proper data (a number of rows); however if I copy and paste that into the aforementioned SQL Text box in A5, I receive error "SQL statement is not valid"

      On the other hand, Preview Query of
      execute procedure "My_Proc"(arg1,arg2)
      within A5 goes without error, but returns only a single row - when several should return to my grid. And clicking OK again gives error SQL statement is not valid.

      Shouldn't approach number one (copy and paste full statement) be simply passed through without conversion?

      And, if approach number two (stored proc) is best, am I forced to implement that via xbasic as an a5w page?

      Or is some other way "best"?
      Last edited by fsi; 07-13-2009, 08:34 AM.

      Comment


        #4
        Re: SQL Builder truncation?

        Aha!

        Select Data Source DAO, not AlphaDAO (as recommended by A5 IDE).

        Problem solved. Thanks, Al.

        Comment


          #5
          Re: SQL Builder truncation?

          Jon

          What I was talking about is shown in this image. This option is also available with other means of connecting to an SQL data source..
          Al Buchholz
          Bookwood Systems, LTD
          Weekly QReportBuilder Webinars Thursday 1 pm CST

          Occam's Razor - KISS
          Normalize till it hurts - De-normalize till it works.
          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
          When we triage a problem it is much easier to read sample systems than to read a mind.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment


            #6
            Re: SQL Builder truncation?

            I received the following from Selwyn:

            we don't support stored procedures in a grid component.

            we could add limited support for stored procedures, but then the grid
            will not be searchable/sortable or updateable.

            for example, when the user does a search, we take the sql SELECT
            statement, parse it and then add on the computed WHERE clause.

            if the select statement is really a stored procedure, what sql would
            be run to execute the SEARCH? or when the user clicks on a column to
            sort, how would be compute the SQL Sort statement?

            we don't support union clauses at this time. (similar reason for not
            supporting stored procedures).

            Comment

            Working...
            X