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

Possible javascript dialog override bug

  • Filter
  • Time
  • Show
Clear All
new posts

  • Possible javascript dialog override bug


    Background info

    I am currently using Alpha Five Version 11 on a Microsoft Windows 7 desktop OS. I have recently run into what I believe may be a bug in the software related to customizing the buttons that appear on the javascript dialogs specified within a grid component.
    Attached to this email is a zipped web project database that consists of a Microsoft Access database that contains two tables: Customers & OrderHeaders. The Customers table is a fictitious list of dummy customer data while the OrderHeaders table contains a fictitious list of dummy order header data. The Alpha Five database also contains two grid components: OrderHeader & CustomerLookup. The OrderHeader grid is based on the OrderHeaders table, and has an associated updateable detail view that allows you to update the order header customer id, order header customer name, order header customer address 1, and order header customer address 2. The CustomerLookup grid component is a read only grid component based on the Customers table. It shows the customer id, name, and address fields. Please see screen shot 'CustomerLookup.png' for an example of what the CustomerLookup grid looks like. The CustomerLookupGrid component is invoked from the OrderHeader grid component via a lookup definition specified on the ‘Ordhdrcustid’ field on the OrderHeader component detail view. When the magnifying glass is clicked on for the lookup, the CustomerLookupGrid component gets displayed and provides you with the ability to select a customer via the ‘Select’ link. From there, the customer id, name, and some of the address information is automatically populated into the respective fields on the OrderHeader detail view. This is all working OK.
    Within the OrderHeader component, I have specified several javascript message overrides. This is normally specified under the ‘Javascript windows’ area of the ‘Customization’ section within any grid component. See attached screen shot 'JavascriptWindowsOptsShot.png' to see these overrides. In particular, I have also overridden the default OK/Cancel button options by replacing the ‘Ok’ button text with ‘Yes’ and the ‘Cancel’ button text with ‘No’. This is circled in red within the screenshot.

    Actual Problem
    The problem I am having is that whenever I invoke the CustomerLookupGrid for the lookup from the OrderHeader detail view, select a customer, and then decide for example, to cancel the changes by clicking on the detail view cancel button, the confirmation buttons that get displayed on the javascript dialog are not Yes/No as I was expecting but instead Ok/Cancel. Please see screen shot 'DialogbuttonsWhenUsingCustomerGridLookup.png' to see exactly an example of this. If I had deliberately specified “yes/no” on the OrderHeader grid, that is what I am always expecting to be displayed but that is not happening in all circumstances. This problem does not happen, however, if I manually type in the data into the OrderHeader detail view and refrain from using the CusomerLookupGrid. Please see screen shot 'DialogbuttonsWhenNotUsingCustomerGridLookup.png' for an example of this. Where is it getting the “Ok/Cancel” from when using the lookup ? The only explanation I can think of here is that the OK/Cancel is originating from the CustomerLookupGrid and “overlaying” the “Yes/No” from the OrderHeader grid component. Why is it doing this when each grid has its own separate set of options ? As a side note, the message dialog text overrides are always being correctly honored regardless of whether the lookup is used or not.

    I would appreciate it if other people, particularly the Alpha Technical support team, could attempt to reproduce this issue using my attached project files and let me know if they can reproduce it and whether it should be considered a bug. If not, why not ?


    Thank you.
    Attached Files

  • #2
    Re: Possible javascript dialog override bug

    Yes... I get the same results. If the Detail Grid is opened to an existing record and you type in a change, then undo the change, you'll get a Yes/No message box. However, if you pop up the Customer Select dialog then select and then undo the change, you'll get the OK/Cancel message box. That's a good one to submit. And thanks for submitting the perfect question... detailed, concise, and with a sample app.
    Last edited by Davidk; 01-27-2012, 08:00 PM.


    • #3
      Re: Possible javascript dialog override bug

      In case anyone is interested, Selwyn responded to a bug report I submitted on this. His response and explanation are shown below:

      "OK, I now understand the problem and it is technically not a bug. Getting A5 to do what you want, however, is easy. First, I'll explain what is going on.

      If you view the source of the OrderHeader Grid in the browser, you will see the following Javascript toward the bottom:

      A5.msgBox.buttons.ok = {html: 'Yes'};
      A5.msgBox.buttons.cancel = {html: 'No'};

      This is setting properties in the Global 'A5' variable in the browser telling it what text to use for buttons on a message box. This contains your customization text.

      Then, after you open the Lookup, if you were to examine the response that was sent from the Ajax callback, you would see

      A5.msgBox.buttons.ok = {html: 'OK'};
      A5.msgBox.buttons.cancel = {html: 'Cancel'};

      This is because you did NOT customize the buttons in the Lookup Grid.
      Since the A5 object is a global Javascript variable, the OK and Cancel button labels have been globally reset to their original values.

      So, your choices are:

      1. add the same customization to the buttons in the Lookup grid.
      2. if you do NOT want to to that, then add this code to the AfterLookupGridFillinValues event in the client-side events section of the OrderHeader Grid

      A5.msgBox.buttons.ok = {html: 'Yes'};
      A5.msgBox.buttons.cancel = {html: 'No'};

      this will reset the settings for the buttons to your customized values.

      Hopefully this is clear to you now."