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

"Object Inheritance"

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

  • "Object Inheritance"

    Recently, (while uncovering a browse related bug) I ran into the following scenario:

    You can set object properties on a "stand-alone" browse (created in the CP browse tab), and the properties (USUALLY) "propagate" into the form where the browse object is placed. ~ And when editing the form, some of these (SAME) settings are available on the browse objects properties.

    I noticed that when certain object properties are set at the browse level, this information is "respected" once the object has been embedded into the form, when it is "run."

    However: Upon viewing the object's properties (on the form itself) many of the same browse object option settings are available for editing/changing. But, the setting options shown do not "reflect" the objects actual settings. (So to see the actual properties settings of the browse object, you have to edit & view the browse itself from the CP browse tab.)

    Seems to me these object properties should:
    1. Propagate (and show the current settings correctly since they are inherited) correctly from the browse itself to the browse object on the form, AND......
    2. Either not be editable (in which case the properties would have to be set on the browse object itself from the CP, OR be editable (so that the settings can be overridden).

    This is not the case whatsoever. There is no consistency or pattern that I can see.

    The other associated problem here is: After you make changes to many of the properties (when you're editing the browse object properties from within the form) the settings are l"ost." (Change a setting, and save. Then go back and look for the setting. It was not saved.) ~ One would think that if the setting is editable, any changes should should be saved. (If you try to change the browse object's settings from the form object on the form itself, the settings "do not take.")

    Note: In other parts of the a5 program (such as when dealing with tables/sets), "object inheritance" is respected.... When you make changes at the set level, the changes do "propagate" to the table itself. (This is what happens when you're editing field rules via a set. Although in this instance, I believe it's not actually "propagation." ~ You're actually making changes to the table settings through the set.)
    Last edited by SNusa; 01-20-2013, 04:03 PM.
    Robert T. ~ "I enjoy manipulating data... just not my data."
    It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
    RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

  • #2
    Re: "Object Inheritance"

    In general, I would forget about "propogation," per se. I don't think yoiu will ever derive any absolutely reliable formula. Rather the browse will by default reflect the current state of the from, and vice versa, unless otherwise set in the form or browse itself. Also opening a companion browse based on the form's set versus the form's parent table will make a difference.
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    martin_w_cole@msn.com

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    Comment


    • #3
      Re: "Object Inheritance"

      Thank you Martin.
      Robert T. ~ "I enjoy manipulating data... just not my data."
      It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
      RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

      Comment

      Working...
      X