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

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

Tabbed Gridlinker Problem Overriding Child Component Properties

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

    Tabbed Gridlinker Problem Overriding Child Component Properties

    My application has what may be an atypical configuration, in that it's using a tabbed gridlinker where I have a parent grid with 3 reference number fields that I use to link to 3 instances of the same child grid (each defined with a unique alias). Each record in the parent grid may have anywhere from 0-3 reference numbers populated in the appropriate fields. In cases where reference number(s) exist for a given record in the parent grid, there is only a maximum of 1 record linked to it in each child grid instance.

    I realize that the way something like this would typically be handled would be by simply basing a grid upon a view that joins the 2 tables behind each of the grids, and that tabbed gridlinkers are typically used in applications which link 1:Many records. But, given the similarities between the 2 tables and the data contained within them, it seemed a less confusing approach to use a tabbed gridlinker, especially because of the way in which the tables' data are displayed as separate logical entities.

    This approach has worked rather well, with exception of some presentation issues that I'm trying to iron out. Specifically, seeing as how I have a maximum of 1 record in each child grid instance, I would like to hide a number of elements that are usually displayed, including the Search and Grid components and automatically display just the Details component right away. The problem here is that I cannot get the child grid to always show its Details component, even if I override this property. Given this, even removing the Search & Grid components from the tabbed gridlinker via Customize Page Layout doesn't do the trick, due to the fact that the Details component will not automatically display. In fact, I'm attempting to override several properties, and none of them seem to be taking, for whatever reason. These include:

    tmpl.show_title = .f.
    tmpl.DetailView.OnlyShowOnRequest = .f.
    tmpl.DetailView.HideGridIfDetailViewIsVisible = .t.
    tmpl.DetailView.HasTitle = .f.

    Actually, typing this all out made me think to try this is regular grid, and it doesn't appear to take effect there, either. I've tried several combinations of the above settings with no luck. So, this would appear to be a more generic grid issue..? Is this a bug, or have a missed some prerequisite configuration needed to get this to work?

    Regards,
    Tarek
Working...
X