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

Can't populate linked fields in target grid

  • Filter
  • Time
  • Show
Clear All
new posts

  • Can't populate linked fields in target grid

    Hello everyone.

    I have two tables, subjects and slides that are linked by a single field. I've made a few web components to display and edit the rows in these tables. I have a component to add a new row to the slide table, and I'd like to make a link from the subject edit page to the new slide page and have the new slide page have the linking field (call it subject_number) already populated. Ideally the user wouldn't be able to modify the subject_number on the new slide page, but the other fields would be modifiable. The problem is that I can't seem to get alpha 5's link expression to work.

    The subject_edit grid component has the subjects table as its source. I've added a calculated field just for the purposes of having an "add slide" link. That field has a fixed value of "Add Slide", and the field type is set to Link with the following URL:


    When I publish all of this, view a subject through the subject_edit page and click "Add Slide", the slide_new page loads but everything is blank; the Subject_Number isn't filled in. The slide_new page works if I manually type in the Subject_Number. Is there something wrong with my tables, components or pages? The link syntax seems correct.

    Thanks for your help


  • #2
    Re: Can't populate linked fields in target grid

    Nevermind, problem solved.


    • #3
      Re: Can't populate linked fields in target grid


      And what is the answer to the problem posed?? This messageboard is a bit different than most in that it is used very intensively to find answers to problems--and as such my reason for asking for the solution---to help others (and myself!). Thanks.
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau


      • #4
        Re: Can't populate linked fields in target grid

        Sorry, it's just that I'm not sure what was wrong. I have three grid components, slide_list, subject_edit, and slide_new that are linked to one another via filter and link expressions. The slide_list component had a link with a filter expression using the subject_id variable which linked to subject_edit. The subject_edit component had a link with a link expression using the subject_id again, this time going to the slide_new component.

        The filter expression from slide_list to subject_edit wasn't correct somehow, and all subject_ids on the latter component were being loaded. This seemed to break the link expression from subject_edit to slide_new, though I'm not sure why. Once I corrected the filter expression and subject_edit loaded only one subject_id, the link expression to subject_new worked and the subject_id filed was populated on subject_new.

        One outstanding issue is that the slide_new component doesn't display the subject_id, which I would like it to. When I submit on slide_new, the row is entered into the target table with the correct subject_id, but it's a bit confusing for the user to not see that filed value while entering the other data.