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

How to prevent unwanted saving records in dbf set-in

  • Filter
  • Time
  • Show
Clear All
new posts

  • How to prevent unwanted saving records in dbf set-in

    My set consists of two dbf table.
    On the form, when entering a new record, when the first table fields entering data and I cross on field of second table and enter date in any field , alpha automatically preserve all entered data into the fields of the first table, and I am not finished entering all the fields in both tables. I do not want to entering data to be finished until I clicks the appropriate button.

    How do I prevent alpha saves the data from the first table fields of set automatically when I enter any data in the field of another table of the set that the form is based off..

    This is a big problem. What if after entering data in second table fields (data from the first table alpha already saved in the first table), the user withdraws from all entries and close the form. I'll have data 'orphans' in the first table with no corresponding data in second table of the set.

    As can be seen in the photos, set consists of two tables with a mutual relationship one to many. And the fields on the form, the first two tabs are from first table of the set and fields on other tabs are from second table of the set.
    Attached Files
    Last edited by draganksg; 01-16-2012, 03:56 AM.
    Dragan Milosavljevic

    [email protected]

  • #2
    Re: How to prevent unwanted saveing records in dbf set-in

    On the Set Design, choose Referential Integrity/Cascade Changes Deletes.
    When the parent is deleted, the children go as well.
    You will need to ensure that if a user cancels the data entry, then the parent record needs to be deleted also.
    The reason that the Child record entry can be cancelled, is because the Parent might contain many Children as the name suggests and you might need to preserve the Parent.
    If you put a button on the Form and an Action Script "Delete Record" which is shown with a message "Cancel all Data Entry?" when the data entry is abandoned, then the Parent will go as well.
    Last edited by Ted Giles; 01-16-2012, 05:51 AM.
    See our Hybrid Option here;

    There are 3 things you can do in any situation;
    Live with it, Change it or Walk away from it.


    • #3
      Re: How to prevent unwanted save records in dbf set

      I do not want to entering data to be finished until I clicks the appropriate button.
      Dragon, Alpha Five saves data to tables, not sets of tables. When the field objects are bound to table fields and you choose to do data entry through a set based form, the behavior you're seeing is necessary. Consider this. If the "Parent" table record in your set were NOT saved, how would Alpha know what link field value to supply to the child table records?

      If this is not what you need, then you may have to create your own data entry sequences from scratch. This could be done by binding your form objects to variables, not table fields, and then writing scripts that pass link field values from parent to child, and writing other scripts that create new records in the parent and child tables, populate fields from the variables, and then save them. A lot of work. Often required on other development platforms, but made unnecessary here by Alpha's default set based behaviors.


      • #4
        Re: How to prevent unwanted saveing records in dbf set-in


        Referential integrity is sometimes not the best choice. There are complications when the app is run over a local network and users on different workstations want to work with the tables in the set. They can't. Those tables are locked by RI. Also, there's a numeric limit on the number of linked child table records that RI can handle. I think it's pretty big, like 512 or something, but in some apps, this would be a deal breaker.

        I'd prefer an approach that uses a script in the "Delete All" button that deletes all the children, and then deletes the Parent. I don't use RI.

        Related material on this is available at Dr. Wayne's site: learn


        • #5
          Re: How to prevent unwanted saveing records in dbf set-in

          Thank's Tom, I look at Peters site quite a bit but didn't go into RI as I've not experienced any issues (so far).
          I'll read up on it.
          See our Hybrid Option here;

          There are 3 things you can do in any situation;
          Live with it, Change it or Walk away from it.