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

Populating fields in a form based on button press

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

    Populating fields in a form based on button press

    I'm designing my first Alpha5 DB for my small business.

    I'm trying to keep track of Leads and Customers. I'm using 3 fields for this:

    Lead_type--> Field rules limit this to either "Lead" or "Customer".

    Lead_date-->The date the lead was entered into the system.
    Cust_date-->The date the lead is converted to a customer.

    I have a button on my main app called "New Lead". You press that button and my main data entry form pops ups with Lead_type defaulted to "Lead" and Lead_date filled in with the current date.

    Every now and again, a new lead will also be a customer right off the bat. Therefore, I have a button called "New Customer". When that gets clicked, I want the form, with the Lead_type field set to "Customer" and I want to have the Cust_date field filled in.

    What's the best way to do this?

    I tried setting some global variables as an event for the push of "New Customer" button, but then I can't seem to figure out the proper way to reference those on the form and get the proper data added into the fields I want.

    Any help?

    Thanks.

    #2
    Re: Populating fields in a form based on button press

    Terry,
    Welcome to the A5 message board! Nice to have you aboard. I'm sure we can help. Nomeclature and details are important.
    I have a button on my main app called "New Lead". You press that button ...
    The term "main app" is a term we will have to conjecuture about. If we take this to mean you have a Form named 'New Lead", with some buttons for the user to chose. ".. that button.. " is something you know about but we do not.
    my main data entry form pops ups with Lead_type defaulted to "Lead"
    . Is this a secondary form based upon the same table that the first calling form is based upon?

    I'm needing some clarification to help you, but maybe others are more on top of things than I.
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    Comment


      #3
      Re: Populating fields in a form based on button press

      Thanks, Mike. I was afraid I didn't have enough info in my original post, but then again I didn't want to start out and write a novel that no one would read. I'll try and clarify a bit.

      My entire DB is just composed of one table. I call that table "maindata".

      I have a form called "mainapp" that is just a series of buttons with onClick events. Most of those buttons open up browses to saved queries. The "mainapp" form is started automatically by Alpha for my users.

      Two of the buttons on "mainapp" are called "New Lead" and "New Customer". Clicking either of those buttons opens up the same form called "DataEntry".

      Clicking "New Lead" has the default behaviour. The "DataEntry" form is opened, the "Lead_Date" field is filled in as today and the "Lead_type" field is defaulted to "Lead".

      I want a press of the "New Customer" button to open the "DataEntry" form for a new record, but I want the "Lead_type" field to be set to "Customer" and I want BOTH of the date fields (Lead_date and Cust_date) to be set to today.

      Hope that helps. Thanks.

      Comment


        #4
        Re: Populating fields in a form based on button press

        Hi Terry,

        It sounds to me that you are trying to build a very simple application but are making it more complicated than need be.

        Use Alphasports as your guide.

        Where are you based? Maybe I can give you some personal help.
        Regards
        Keith Hubert
        Alpha Guild Member
        London.
        KHDB Management Systems
        Skype = keith.hubert


        For your day-to-day Needs, you Need an Alpha Database!

        Comment


          #5
          Re: Populating fields in a form based on button press

          Terry,
          Thanks for the detailed explanation. Attached is an example of what you describe. To set the field values in the opened dataentry form from the calling form buttons using Action Scripting, the dataentry form has to be open as you are writing the action script on the calling form buttons OnPush event.

          Hope that helps.
          Mike W
          __________________________
          "I rebel in at least small things to express to the world that I have not completely surrendered"

          Comment


            #6
            Re: Populating fields in a form based on button press

            Mike - Excellent. Thanks so much. That made it really easy.

            I was definitely confused about when my DataEntry form had to be opened. I thought it just had to be open at runtime. Now I realize that to use that form for Action Scripting it has to be open when I'm actually designing it.

            Comment

            Working...
            X