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

Unbound UX versus bound UX

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

    Unbound UX versus bound UX

    I am new to Alpha (and application development) so I apologize if this question is elementary. I have searched Alpha's documentation, videos, and this forum but have yet to find a clear answer (at least clear to me ). What are the advantages/disadvantages to using a bound UX versus an unbound UX? Are there scenarios that warrant one or the other? I have found certain controls (e.g. upload/download) won't work if the UX isn't bound to a table. But I know you can create an unbound UX that pulls data from a table just fine. Thank you in advance for your feedback.

    #2
    Re: Unbound UX versus bound UX

    I think the unbound control is a later addition. It gives more control to the programmer. I would tend to use the unbound control when i was using multiple tables.

    Comment


      #3
      Re: Unbound UX versus bound UX

      I concur with Michael

      With unbound it feels like I have more control,
      choosing exactly how the data loads with calling runAction method to execute
      Javascript Action (Populate controls in an UNBOUND UX...)

      and which events call the runAction method to execute a Javascript Action based on
      (Update Insert or Delete Data for use with an UNBOUND component)

      Comment


        #4
        Re: Unbound UX versus bound UX

        Thank you both for the answers. This forum really does provide a great amount of support. Thanks again. Cheers!

        Comment


          #5
          Re: Unbound UX versus bound UX

          Michael C, Michael M,

          Could you please direct me to some links or videos where I can learn more on working with multiple tables? I'm kind of stuck with it.

          Thanks,
          Laksiri

          Comment


            #6
            Re: Unbound UX versus bound UX

            Another obvious scenario where unbound is required is the Data Binding method cannot be used. For example if you need to update TableA under one condition, or TableB under a different condition. But if Data Binding works, which it does most often, it is a much easier than writing the code out yourself (don't tell Selwyn I said that).

            The "history" of the *unbound field actually comes from Grids and pre-dates Dialog2/UX. Before the Dialog2 (called UX in V12) we used Grids with unbound fields to mimic Dialog-like forms. Unbound was specifically added to support that. You could also use the old style Dialog (v10 and earlier) but the new Ajax-enabled Grid was superior to the older Dialog at that time.
            Steve Wood
            See my profile on IADN

            Comment


              #7
              Re: Unbound UX versus bound UX

              Hi Laksiri

              Alpha has so many videos, where are you stuck?

              By multiple tables do you mean repeating sections or the more complex example Steve mentioned. As Steve said the genie route is the easiest, Alpha has plenty of paths to follow.

              Let me know a bit more and I can probably help.

              Michael

              Comment


                #8
                Re: Unbound UX versus bound UX

                Michael,

                Thanks for your reply. I think I found some videos in Alpha library. Below are two titles I found.

                CRUD Operations (CReate, Update, Delete) in an Unbound UX Component
                Populate Controls with Data from a Table - UX Component is not "Data Bound"


                Here is my question more in details. I maintain some sort of "session" variables in StateInfo object (such as user, office, and user level retrieved from the database when a user login-in). I want to use them in the selection criteria (in the where clause if you think in SQL) or I want to write them to the database when a new record is added (as an example, when a sales person add a new customer to the customer table, I want to assign current user [managed in a system variable, not in a control] as the default sales person)

                How can I do with action script genie? or do I have to go to XBasic for that.

                Please let me know if my question is not clear enough.

                Laksiri

                Comment


                  #9
                  Re: Unbound UX versus bound UX

                  The portion where you say when a salesperson adds a customer,
                  That can be done with bound or unbound dialogs.
                  On a bound dialog when the dialog is called to open you can populate those controls with the session variables and then when save they are saved if you mark them dirtied.
                  On an unbound dialog you check all the fields make sure they are ok and write your code to save the data including the assigned data from session variables.

                  Regarding bound vs unbound
                  If you have single table or two tables linked by a field then bound dialog is easy to build less code writing by you
                  On the other hand if you have two or three table not related to each other by any common fields in the table unbound will be the way to go
                  Session variables may be used in either.
                  thanks for reading

                  gandhi

                  version 11 3381 - 4096
                  mysql backend
                  http://www.alphawebprogramming.blogspot.com
                  [email protected]
                  Skype:[email protected]
                  1 914 924 5171

                  Comment

                  Working...
                  X