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

Session variable in Open Grid Action JS

  • Filter
  • Time
  • Show
Clear All
new posts

  • Session variable in Open Grid Action JS

    I am trying to set a session variable in the Open Grid Action JS (see pic) so I can use it in the child grid. The problem is the variable gets populated once with a value form row in parent and does not change after that. For expl if I open the child grid the 1st time from parent row#2 and lastname is Rigan, no matter from what row I subsequently reopen the child grid, the value stays the same (Rigan), until I close the parent grid and reopen it. Has anyone used this feature? Any idea why the value is not dynamic?
    Attached Files

  • #2
    Re: Session variable in Open Grid Action JS

    The problem with session variables is that they often get cached at the browser, and once that happens the browser won't see the refreshed values. See my post! in this forum for ideas on how to use window[] -variables instead of session variables to carry your data.


    • #3
      Re: Session variable in Open Grid Action JS

      Thank you very much. Now I understand why it doesn't work the way I want it to work. Thanks again.


      • #4
        Re: Session variable in Open Grid Action JS

        In your approach you are using an AjacxCB to receive the value from the parent grid and use it in an AjaxCB/Xbasic script in the child grid. In my case I need the value to just exist on the server side in the 2nd grid so I can use it for filtering purposes; I don't need need to execute an AjaxCB/Xbasic script per say. I am struggling to find a way to make it come alive in one of the server side events like OnGridExecute. Any pointer will be highly appreciated.


        • #5
          Re: Session variable in Open Grid Action JS

          Gaby --

          You need to create a window[] variable in JS, then pass it to your server-side Xbasic via an ajax callback from your server side event(s). window[] variables are nice because they persist and are visible across component calls, and they are not cached at the browser unlike session variables. Server-side local Xbasic variables do not have any persistence beyond the currently executing code, so you can't revisit them from one Xbasic call to another.

          You could use server variables to store persistent data for Xbasic, though. It's as easy as this:
          DIM server.myvariable as C
          server.myvariable = 'Hello!'
          This variable will now persist from one Xbasic call to another, and you can read it or modify it just like any other local variable:

          server.myvariable = 'Goodbye!'
          The problem with server variables (if I understand this correctly) is that they are local to the server and available to all sessions running on the server, so another session could come along and change your variables, so this is not ideal either.

          I actually thought about creating a "server cookie" database (DBF), which would store session -specific variable/value data and manage itself through timestamps.

          So, it would look something like this:

          1. Store a variable for another Xbasic call something like this:
          StoreServerCookie(session.sessionID, "MyVar", "ABC", "C",2) where "MyVar" is the variable name, "C" is the data type, and 2 is the lifetime of the cookie (in seconds)

          2. This function looks for a row in the cookie DBF with the session.sessionID in the session_ID and "MyVar" in the variable_name column.

          3. If sessionID/MyVar -combination is found, overwrite its values

          3. If sessionID/MyVar -combination is not found, look for expired session cookies for the current sessionID (cookie expires when time elapsed between now and the creation timestamp of the cookie is more than the "lifetime" value - which defaults to 24 hours if not specified)

          4. If an expired cookie is found, recycle it with the incoming values

          GetServerCookie((session.sessionID, "MyVar") would simply retrieve and return MyVar's value from the cookie database.

          This really is a somewhat complex way of getting around the fact that session variables Xbasic variables don't persist, but I don't know of any other way to persist Xbasic values in the server. So I might actually do this one of these days...