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



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

Bound fields in forms

  • Filter
  • Time
  • Show
Clear All
new posts

  • Bound fields in forms

    I want to use 2 forms to hold info for 1 contact record. In both forms I'm using fields created from 1 table. When I access the second form in Browse the field contents are not bound to the same record as displayed in form one. How do I "bind" the 2 forms together?

    I'm not yet strong in xbasic so hopefully there is an "easy" solution.

  • #2
    Re: Bound fields in forms

    Two ways come to mind.

    1) Filter the display in the called form to match a key value in the calling form; or

    2) Open the called form but keep it hidden; set the index to suit; then do a find by key; finally, show / activate the called form to the user.

    I believe the first can be done entirely with Action Scripting. The second will require a bit of xbasic coding.

    If you don't really need to open a second "form", you might investigate the "companion browse" for your primary form. It's available with the F8 key. And is explained in the user's guide.


    • #3
      Re: Bound fields in forms

      Forms don't hold any information. Forms display records from a table, generally one record at a time.

      If you are opening two different forms and locate the same record by some unique identifying field both forms will display whatever fields from that record they are designed to display.

      Your question seems to indicate that you expect/want to open one form, then the second, and have the same record displayed. That would require opening the first and then opening the second filtered to the same identifying field. That should be fairly easy to do with action scripting a button on the first form. The genie for action scripting a form open button should lead you through the process.

      (Slow typing, Tom got there first.)
      There can be only one.


      • #4
        Re: Bound fields in forms

        Why 2 forms?
        Try this:
        Create Form based on one Table using default.
        Add an embedded Browse - on the right say - and use a field from the Table.
        As you move through the record in the Browse, the Record data is also changed.

        Else as Stan says, displaying Forms with the same record identifier is easy using ActionScripting.
        See our Hybrid Option here;

        If at first you don't succeed; call it Version 1.0


        • #5
          Re: Bound fields in forms

          Fantastic. Thanks fellows.
          I have so many fields displayed one form1 that it is necessary to incorporate a second form.
          I'm learning that Alpha 5 can do virtually anything you want if you spend enough time with it.


          • #6
            Re: Bound fields in forms

            I have so many fields displayed one form1 that it is necessary to incorporate a second form.
            Generally tabbed objects or conditional objects are employed to let the user choose which fields to display on the current form.

            I can't help but wonder if your table structure is part of the issue. Are all of the fields in the table necessary to the task. IOW, do you have, say a product part number, the part description, the vendor number for that product, and the vendor name in one table? Normalization moves all product details to their own table, linked back through the part number when needed. Likewse for vendor details.
            There can be only one.


            • #7
              Re: Bound fields in forms

              You can use file - open(not open database) - and choose another form.

              That is available as an action script from a button that can 'switch' from form1 to form2 and back and keep you pointed to the same record.
              Al Buchholz
              Bookwood Systems, LTD
              Weekly QReportBuilder Webinars Thursday 1 pm CST

              Occam's Razor - KISS
              Normalize till it hurts - De-normalize till it works.
              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
              When we triage a problem it is much easier to read sample systems than to read a mind.
              "Make it as simple as possible, but not simpler."
              Albert Einstein



              • #8
                Re: Bound fields in forms

                Originally posted by Stan Mathews View Post
                Generally tabbed objects or conditional objects are employed to let the user choose which fields to display on the current form.
                This might well suit your requirements Del.
                You can set the Tabs up so it looks like a series of screens you are swapping between.
                If you go this route, and use Memo fields in the tabs, suggest you put a [Save] when departing the Memo Field in case you loose the data.
                See our Hybrid Option here;

                If at first you don't succeed; call it Version 1.0