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

Form based off set - fields in child tables not displayed on form

  • Filter
  • Time
  • Show
Clear All
new posts

  • Form based off set - fields in child tables not displayed on form

    Hi everyone,

    I'm on Alpha Five v9 and a couple months back I took out 4 memo fields from my primary table and put them into 4 new separate tables. There were some lag issues and it looked liked there was some corruption going. The database file appeared to be ballooning from 4 GB to around 20 GB every time I tried to back it up, rendering it unusable. I think this also happened upon database compression/packing.

    After reading a few threads indicating that it is best to keep memo fields in separate tables if you don't want to lose all your data (correct me if I'm wrong), I went ahead and recreated tables, imported data and took the four memo fields. It currently has around 7,000 records.

    All four links in the set are matched on the same key as all one-to-one relationships matching on first record, cascade changes, and always include record from parent.
    For example

    Primary_table *Indexes: Issue_Count, ASC, Include Unique only
    -issue_count (auto-increment; audo advance after field filled; Skip set to True)
    +20 other numeric/char/date fields

    Child_table_bcc *Indexes: Issue_Count, Order by Issue_Count, Asc, Include All
    • issue_count (char, width=6, user entered)
    • memo_field (simple default expression, set default value to field expression at start of record)

    Child_table_cc *Index: Issue_Count, Order by Issue_Count, Asc, Include All
    • issue_count (char, width=6, user entered, value of field must be unique)
    • memo_field_two (simple default expression, set default value to field expression at start of record)

    Child_table_issue *Index: Issue_count order by Issue_count, Asc, Include All
    • issue_count (char width=6, user entered, value of field must be unique)
    • memo_field_three

    Child_table_resolution *Indexes: Issue_Count1, Order by Issue_Count, ASC, All; Issue_count order by Issue_count, Asc, Include Unique only
    • issue_count (char width=6; user entered, value of field must be unique)
    • memo_field_four

    Alpha5 automatically added that Issue_Count1 index at some point, and doesn't really allow me to delete it.

    First issue: Why isn't the field rule working anymore now? The first two fields of Child_table_one and Child_table_two originally auto-populated in the form itself. However, after moving them to their own tables, the field rules don't appear to be working anymore. My only work-around for this was to add a set field value action in the OnEnter Form event to evaluate to the field expressions I had already in the table's field rules.

    Second issue: Why are duplicate records being created and disappearing from the form? For Child_table_resolution, it appears that field data entered disappears from the form after saving, switching to a different record then returning to the same record. I checked the tables themselves, and the records are there. I don't quite understand why it disappears from the form itself. I tried adding more text to the field that went blank and it now appears to create another record in the child table with the same issue_count number and the new entry. It appears to be happening with Child_table_resolution table only. Perhaps it's a field rule?

    Any clues on where things might have gone awry?
    Last edited by Alston; 01-15-2015, 08:18 PM. Reason: formatting, added missing field rule to Child_table_resolution

  • #2
    Re: Form based off set - fields in child tables not displayed on form

    Please attach a zipped copy of the database, with sample data, and provide step by step instructions for us to follow to see the behaviors you're describing.


    -- tom