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

Appending records from a UX component

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

    Appending records from a UX component

    I would like to set up a button that will append specific fields from a ux component into a lookup table. Im using AAv12 running a MySQL backend. I've set up a field in the ux to look up this table and fill in fields based on matching license number, but if there is no matching records in the lookup table I would like the user to be able to press a button to append the information entered, in order to make future entries easier, but at the same time making sure that duplicate records are not allowed in the look-up table. Is this something I would have to create in the MySQL database or can this be written in the buttons properties in AA?

    Can anyone point me to some kind of information that I can read on how to accomplish this? I'm still learning how to accomplish these tasks using MySQL back end, Ive always only built desktop applications using dbf's so this is very frustrating for me. Thanks for any help in advanced, and Im sorry if Ive left out any information so please ask if you need more info.

    -Ivan

    #2
    Re: Appending records from a UX component

    create separate dialog - called ux in your version. bind that to the look up table whatever it is. and in the afterdialog validate event or something that is equivalent in your version, add save data to the table.
    then go to the dialog that you are working in the button's onClick event select to open a dialog and point to the dialog you just created in enter mode.
    that will take care of adding the record. if you need to refresh, the add another button refresh the dropdown list.
    should be able to do with little or almost a little coding in xbasic.
    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


      #3
      Re: Appending records from a UX component

      Originally posted by GGandhi View Post
      should be able to do with little or almost a little coding in xbasic.
      I need to learn how to code, do you have any suggestions on material where I can get started?

      I don't want the user to have to enter this info twice, once in the main entry form and then again to add the values to the look up table. Whats the easiest way of doing this, can the ux that opens populate its values based on whats currently on the main form?

      Comment


        #4
        Re: Appending records from a UX component

        the logic is not making sense to me, I could be the problem.
        you have a field and that looks up and fills other fields in the ux, if the data is not there nothing will be filled in. you will not be entering the data into the fields in the ux, even when the lookup is successful. that is the idea of the lookup, to prevent errors or duplicating data entry. ideally the filled in fields should not editable by the user. if you don't have the right entry for the lookup field,
        then you press the button and add entry to the lookup table, press another button refresh the lookup dropdown. now go forward.
        that is the way I think, it is logical to me.
        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


          #5
          Re: Appending records from a UX component

          My apologies, let me explain a bit more of my application.

          Table1 = the main table that holds CONTRACTOR, PROJECT, and AWARDING AGENCY information
          Table2 = is just a table with only contractor information
          Table3 = is just a table with only Projects information
          Table4 = is just a table with only Awarding Agency information

          Table 1 brings tables 2-4 together with all the values in the lookup tables. But table1 in no way links with tables 2-4 other than a simple lookup of information. The information from tables 2-4 gets entirely copied to table1.

          Comment


            #6
            Re: Appending records from a UX component

            Originally posted by Gustavo1478 View Post
            My apologies, let me explain a bit more of my application.

            Table1 = the main table that holds CONTRACTOR, PROJECT, and AWARDING AGENCY information
            Table2 = is just a table with only contractor information
            Table3 = is just a table with only Projects information
            Table4 = is just a table with only Awarding Agency information

            Table 1 brings tables 2-4 together with all the values in the lookup tables. But table1 in no way links with tables 2-4 other than a simple lookup of information. The information from tables 2-4 gets entirely copied to table1.
            then the way I do is
            in the ux I will have a button to add to contractor table, another to refresh that look up field
            in the ux I will have a button to add to project table, another to refresh that look up field
            in the ux I will have a button to add to awarding agency table, another to refresh that look up field
            all the fields that are filled in using the look up will not be editable by the user.
            that's how I will do.
            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