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

Can a Viewbox use a SQL Stored Procedure for the datasource

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

  • Can a Viewbox use a SQL Stored Procedure for the datasource

    I have a complex query with quite a few subqueries, and the SQL parser in the ViewBox doesn't like them, so I was trying to see if the SQL Statement could be a Stored Procedure??
    I would want to pass 3 arguments.

    I don't think I can create a view since the subqueries are using 1 of the arguments

    I could create a function and it would work
    select * from fnViewBox(:Arg1,:Arg2,:Arg3)

    But the view box sql editor doesn't like that either.
    Last edited by asawyer13; 01-02-2019, 07:30 PM.

  • #2
    Re: Can a Viewbox use a SQL Stored Procedure for the datasource

    Haven't done it myself, but I'm pretty sure that since the LIST control can do that that the ViewBox control can as well. See the video "UX_V12--93 List Control - Using Native SQL For List Data". However, there is another technique that would most likely work and that is to define the "source" of the data to be "Static Data". In that method you list only the column names in the static data and in your xbasic you convert the query result set into JSON using one of the built-in aa functions like "VarToJsonStandard" and send back a little JavaScript code that gets a point to the LIST (ViewBox in your case) and calls the "populate" method with that json data.

    Comment


    • #3
      Re: Can a Viewbox use a SQL Stored Procedure for the datasource

      You could move the complex query to the database and make it a view

      Comment


      • #4
        Re: Can a Viewbox use a SQL Stored Procedure for the datasource

        Originally posted by GarthMc View Post
        You could move the complex query to the database and make it a view
        The query has inline subqueries in it that needs to use an argument so I don't think I can put it in a view

        For example.

        Select field1
        from table1
        where field2 = (select field3 from table2 where field4 = :Arg1)

        I don't believe I can create a view that will work for that. I have the value for Arg1, but I can't just add it to the where clause of the query that's using the view.

        Does that make sense??

        Unless I'm missing something, which is always possible.

        I tried using the List with the ViewBox and it works in a simple test, but My viewbox is inside a Container, which is inside a PanelHeader which is inside a PanelLayout and for some reason it won't show the viewbox at all.

        Comment


        • #5
          Re: Can a Viewbox use a SQL Stored Procedure for the datasource

          Originally posted by GarthMc View Post
          You could move the complex query to the database and make it a view
          Let me see if there is some way I can rework my query to be subqueries rather than inline.

          Comment


          • #6
            Re: Can a Viewbox use a SQL Stored Procedure for the datasource

            I should add that if I use a view in the viewbox everything works great but I don't think I can get my complex query put into a view, that's why I started thinking of using a stored procedure as I can do it very easily there.

            Comment


            • #7
              Re: Can a Viewbox use a SQL Stored Procedure for the datasource

              I was able to rework my complex query so it could be put into a view. Now to test that.
              Thanks for the replies.

              Comment


              • #8
                Re: Can a Viewbox use a SQL Stored Procedure for the datasource

                I was able to redo my query into a view, however the real issue was my criteria. So the stored procedure stuff worked as it should, it was just me

                Comment


                • #9
                  Re: Can a Viewbox use a SQL Stored Procedure for the datasource

                  BTW Alan,
                  Did you try putting your original query in the ViewBox as a Nested SQL Query? On the "Data Source" tab for the ViewBox there is a "Query Type" field which can be set to "SQL Query" or "Nested SQL Query". I would think the builder for the latter type of query could have done what you want. You can make really complicated queries with that builder. Arguments can be used in the WHERE expression at any level in the Nested Query Builder.

                  Comment


                  • #10
                    Re: Can a Viewbox use a SQL Stored Procedure for the datasource

                    Without knowing the relationships between your tables, there are many ways to write SQL queries to accomplish a task. This may or may not be of help here.
                    Here is a simple example. Return a list customers who have purchase a specific product category.

                    I verified that this query will work in both a list control and viewbox.
                    SELECT distinct o.CustomerID
                    FROM orders o inner join [Order Details] OD on od.Orderid = o.orderid
                    left join products p on p.productID=od.productid
                    where p.CategoryID in (select p.categoryid from products p where p.categoryid= :Arg1)

                    Here is a method to move the argument to the main where clause but Alpha does not know how to parse this statement using left join sub queries.
                    SELECT distinct o.CustomerID
                    FROM orders o inner join [Order Details] OD on od.Orderid = o.orderid
                    left join
                    (select productid, categoryID from products) p on p.productID=od.productid
                    where p.CategoryID = :Arg1

                    Convert the above statement to a view

                    create view view_CustomerProductCategory
                    as
                    SELECT distinct o.CustomerID, p.CategoryID
                    FROM orders o inner join [Order Details] OD on od.Orderid = o.orderid
                    left join
                    (select productid, categoryID from products) p on p.productID=od.productid


                    Now use the view as your record source.
                    select CustomerID
                    from view_CustomerProductCategory where categoryid=:Arg1

                    Comment


                    • #11
                      Re: Can a Viewbox use a SQL Stored Procedure for the datasource

                      @frankiez +1 nice!

                      Comment

                      Working...
                      X