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

Updating Existing Forms

  • Filter
  • Time
  • Show
Clear All
new posts

    Updating Existing Forms

    I have a form for new projects that is linked to my contacts table so that when I select the field for client ID it pulls up a list of my contacts and I can select one and it will insert the information into the specific fields I have chosen in my new project form. The problem that I am having is that when I change information in my contacts table the information does not automatically update in my New Project form. Is there a way for me to set it up so that any information I change in one table will automatically update the fields in another table? Any help would be much appreciated.

    Re: Updating Existing Forms

    Is there a way for me to set it up so that any information I change in one table will automatically update the fields in another table?
    Take a look at posting field rules.
    There can be only one.


      Re: Updating Existing Forms

      Thank you for your help. I am still either not understanding something or not being clear on what I am trying to accomplish. I am trying to create a form for the set I created but I don't want to have the embedded browse in the form. So what I did was I cut out the embedded browse and inserted the fields from the child table into the form for the set where I wanted them to be located. Now the fields for the child table just stay blank and don't fill in automatically. I don't understand why this would be. How would I go about setting up this form the way I want? How do I connect my two tables in this set to automatically update whenever I make a change to either table or the set? Thanks so much for the help I really appreciate it.


        Re: Updating Existing Forms

        Cassie, a specific answer to your questions is not possible until you supply a copy of your database and a detailed description of how you want a specific form or button to work.

        In general terms there are two commonly used approaches that may be close to what you need:

        a) In the case where a particular contact person may be involved in multiple projects the designer (you) would store the contact_id in each project table record. This would be filled in using a table lookup field rule in the projects table, using the contacts table as source. A two table set would be used for reports and forms. the link would be one to one based on contact_id fields in both tables. No need to update field values in the parent table at all. Each record there is linked to the corresponding contact table record so the "current" field values are always available. There's no reason in this scenario to store any field values in the projects table except the contact_id value. In this case the key information you need to have availble is the current contact table field values. You don't care what those values might have been at some point in the distant past.

        b) In other applications the need exists to "lookup" information from one table, and auto-fill multiple fields in the current table. i.e. looking up a product record to retrive and store current pricing information. In this case a table lookup field rule would be defined to select and autofill several fields in the current table. Changes that occurr later on in the lookup source table would NOT be automatically transferred to previously entered transaction records, since that would overwrite the previous pricing information that was applicable to the transaction when it was recorded. In this case you would not use a set. Just a field rule table lookup. Here, you don't care what the current pricing field values might be in the lookup table, you are only interested in what those field values where when they were looked up and stored in a trransaction record at some point in the past.
        Last edited by Tom Cone Jr; 11-12-2009, 02:22 PM.