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

Using Session variables across multiple grids in same session

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

    Using Session variables across multiple grids in same session

    Alpha 5 v10.5 build 3641 web application on Vista

    I have setup a session.__protected__ulink variable in the initial value row of a "user name" field on multiple pages. Each page contains a columnar update only grid. Total of 4 pages within the user signup process will be needed.

    Page 1 is the dialog page where I have defined the session.__protected__ulink variable.

    Page 2 thru 4 are update only grids with a common link of "user name" with the initial value of the "user name" field being session.__protected__ulink.

    I can call the variable on the 2nd a5w page so I know that Alpha is passing the session.__protected__ulink variable but I am having trouble getting the 2nd Page grid's initial value field to populate with the session.__protected__ulink variable. The first page's grid works just fine.

    Any ideas?

    Tim

    #2
    Re: Using Session variables across multiple grids in same session

    Tim,

    The initial value property is only used during an insert so if your grid is update only it will never fire.

    If the 2nd grid is update only then what are you attempting to accomplish with this? If the grids are "linked" by userid then that presupposes that the userid will not change.

    If you are looking on updating the userid with a session variable then I would put the session in the BeforeValidateExistingRecords event or the CanUpdateRecord event. It would look something like:
    Code:
    DataSubmitted.userid = session.__protected__ulink
    Rod

    Comment


      #3
      Re: Using Session variables across multiple grids in same session

      Thank you Rod for responding.

      All the grids are update only so I know that the initial value does work on an update grid. However you may be correct in regards to multiple update grids.

      The reason I attempting to do it this way is that I have a database of information for unregister users so that when they do register their information is associated with a user name. I have 4 tables that are design like that.

      My solution is to update the user name on all tables from the AfterUpdateRecords events on the first grid. I want the display to be easy on the eyes so I don't want too much information displayed on one page so therefore the linked grids isn't a good option to me.

      Tim

      Comment

      Working...
      X