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

Solution for passing variables between client and server in ajax callback!

  • Filter
  • Time
  • Show
Clear All
new posts

  • nlights
    Re: Solution for passing variables between client and server in ajax callback!

    Thank you, and I fully agree with your Wiki comment.

    Leave a comment:

  • peteconway
    Re: Solution for passing variables between client and server in ajax callback!

    Thanks for the excellent post, one of the best presented I have ever read. The Wiki could certainly use learn from your style and clarity.

    Leave a comment:

  • Solution for passing variables between client and server in ajax callback!

    Just in case someone else is struggling with the same thing as I've been struggling for a while, this explanation might save you some time and tufts of hair.

    Task: Grid1 row calls Grid2, and Grid2 needs to know the primary key (row ID) of the calling row in Grid1.

    First solution: Create a session variable during the call from Grid1, and store the primary key in that variable. Then pick up the session variable in Grid2

    Problem with the first solution: Session variables are often cached in the browser, so while the first call from Grid1 sends the right primary key to Grid2, subsequent calls that try to refresh the session variable with a new primary key don't show up in the browser, because the browser grabs the value from the cache, which is the previous value

    Second solution: Create a variable and attach it to the browser's window object. Then pick up the window object variable in Grid2. Since the window object is not cached, refreshing the value of the attached variable succeeds every time, and thus Grid2 receives the right ID every time

    Problem with the second solution:
    While it is easy enough to display window[] variables in a freeform HTML section, it is quite a different story trying to tell a server-side Xbasic function what those variables are. I've seen some pretty creative solutions having to do with storing a variable to a calculated hidden grid column etc., but they all had inherent problems for my purposes, so the search continued. And continued. And continued. Until finally I figured out how to...

    How to do it anyway:

    1. During the ajax callback call from a button on Grid1 row to Grid2 create a window variable in inline-javascript such as:
    window['wvE_EVENTID'] = {grid.Object}.getValue('G','E_EVENTID', {Grid.RowNumber});
    followed by "Open a Grid Component" Action Script

    2. In grid2 you can use an action button's javascript to call an xBasic function that receives the window[] variable as follows:
    var rowNum = {grid.object}._selectedRow;
    var additionaldata='vendorid ='+window['wvE_EVENTID'];
    The trick here, of course, is to use the "Additional data to submit" -feature of the ajax callback action javasript. And that is what allows Javascript communicate with Xbasic.

    When you examine the e. object properties in the InsertData Xbasic function with the debugger, you will see that one of the variables passed as its property is "e.vendorid_", which has the value of window['wvE_EVENTID'], which in turn was set in Grid1. So now you can have your parent grid primary key and eat it too!

    And who says an old dog can't learn new tricks?

    Thank you. Thank you very much.