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

AJAX Callback in clientSideEvent

  • Filter
  • Time
  • Show
Clear All
new posts

  • AJAX Callback in clientSideEvent

    I have a ux component that I would like to perform an ajax callback when the compnent is loaded.

    I've defined an xbasic function to perform an INSERT to a MySQL table.
    I've defined an action javascript to perform the the call back to the xbasic function, then I placed {dialog.object}.runAction('actionName') in the onInitializeComplete on the client side Events.

    My events fire as expected in working preview but not when I publish the component and run it in chrome. Can anybody tell me why this is not working? Any suggestions?

  • #2
    Re: AJAX Callback in clientSideEvent

    Well, first if your using a pre-release it could be an error/bug. If your NOT and are trying to figure out what's going wrong, try using the development tools in Chrome and look at the console to see if there are any errors there. Sometimes, it's an issue that you can spot that way, especially when it's working in "Working Preview" Also for further testing try running the server locally. If it works locally and by that I mean your URL should say something like local host:80 and not just in live or working preview.
    In doing some bug testing I was told to do that recently and sure enough I had an error when I published that worked in live and working preview. When I published to a local server the error was repeatable. Selwyn told me if it works on local host then there is an issue with your published version, perhaps not everything necessary was correctly published or something else like for instance code on the page or from a tabbed UI is interfering.
    At any rate, I would first look at the development tools in Chrome and inspect there.
    Good Luck!
    NWCOPRO: Nuisance Wildlife Control Software My Application: "Without forgetting, we would have no memory at what was I saying?"


    • #3
      Re: AJAX Callback in clientSideEvent

      I think you need to use this:
      {dialog.object}.ajaxCallback('','','ActionName','','',{deviceOfflineFunction: function() { }});


      • #4
        Re: AJAX Callback in clientSideEvent

        Thank you all for the helpful replies, I think my mistake was a lack of knowledge of how the security tables and connection strings work.

        I got it to work once I published the component directly to the folder I was using for testing it, Normally I had been publishing to a folder where I had published the web security files, then copy and pasting the .a5w, .a5wcmp and .a5rpt files to my test folder. I think the problem was that my test folder didnt know/have the connection string (correct me if im wrong here). I was dimming a connection string my event.