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

Can't use native SQL in UX list ... why not??

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

    Can't use native SQL in UX list ... why not??

    I get results back in the preview but I also get an error. See screenshot below.

    My SQL query runs fine in a report because I have the option of selecting "Native" as my SQL syntax. There is no such option, that I have found, in a UX list.

    For now I guess I'll create a view for the list to run against.

    ScreenShot_003.jpg

    EDIT: See post #2 ...Native syntax is available here but for some reason Alpha doesn't like my query.
    Last edited by mikeallenbrown; 02-16-2016, 02:42 PM.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    #2
    Re: Can't use native SQL in UX list ... why not??

    Just spotted this...

    ScreenShot_005.jpg

    I don't understand why I'm getting an error then. The query runs fine in SQL and fine in a report but bombs here.

    My SQL query..

    Code:
    SELECT case e.Field6 when '551B' then 'Skilled Nurse (LVN)' when (551) then 'Skilled Nurse' when (571) then 'Home Health Aid' when (561) then 'Social Worker' when (569) then 'Social Worker Phone Call' when (421) then 'Physical Therapy' when (431) then 'Occupational Therapy' when (441) then 'Speech Therapy'  end AS Type
    ,e.Field6, CAST(e.STARTTIME AS DATE) AS Date, p.LastName, p.FirstName, p.MRNum
    FROM EventsPT e
    	 INNER JOIN Patient p
    		 ON  e.GROUPID = p.ID AND p.ClientID = 5049
    WHERE e.RPTYear = 2015 AND e.Field6 IS NOT NULL AND e.Field6 <> ''
    ORDER BY Date
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    Comment


      #3
      Re: Can't use native SQL in UX list ... why not??

      check the statement you have for "cast(e.STARTTIME as data) as date". The second occurrence of 'date' might be better off as a quoted identifier or something other than "date".

      Comment


        #4
        Re: Can't use native SQL in UX list ... why not??

        Thanks Rich. I changed the second occurrence of Date to VisitDate but received the same error.

        I ended up using a view so my list is working now. Still doesn't make sense to me why my original query wouldn't work.
        Mike Brown - Contact Me
        Programmatic Technologies, LLC
        Programmatic-Technologies.com
        Independent Developer & Consultant​​

        Comment


          #5
          Re: Can't use native SQL in UX list ... why not??

          Found the issue ... seems to be an Alpha bug.

          In examining my components xBasic I discovered that the sql.portableSQL property was set to .T. . Since I wanted to use native syntax I changed this to .F. . Now my original query runs fine.

          Screenshot taken after I changed the property to .F.

          ScreenShot_006.jpg
          Mike Brown - Contact Me
          Programmatic Technologies, LLC
          Programmatic-Technologies.com
          Independent Developer & Consultant​​

          Comment


            #6
            Re: Can't use native SQL in UX list ... why not??

            I don't know how you managed to change that setting from the "Xbasic" tab in the designer. I've always thought anything shown on the tab was just calculated stuff and that the system would throw away any change you attempt to make there. I just tried making that change on a sample UX and it wouldn't stick.

            Comment


              #7
              Re: Can't use native SQL in UX list ... why not??

              Truth be told I am still using the view in my list. I did change that property and then previewed the data in the list designer successfully without error. I didn't actually publish my component because I already had it working with the SQL view. I see what you mean now and I think you're right.

              I sent Alpha a bug report with my findings. I suggested to them that they add a dropdown so that a developer can choose native or portable (like you can in a report component). Otherwise the syntax in the list is always portable.
              Mike Brown - Contact Me
              Programmatic Technologies, LLC
              Programmatic-Technologies.com
              Independent Developer & Consultant​​

              Comment


                #8
                Re: Can't use native SQL in UX list ... why not??

                From Selwyn: i have exposed the 'portable sql' property in the list builder.

                Thanks Alpha!
                Mike Brown - Contact Me
                Programmatic Technologies, LLC
                Programmatic-Technologies.com
                Independent Developer & Consultant​​

                Comment

                Working...
                X