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
Devcon 2020 Goes Virtual! LEARN MORE >

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

problems with 2944_3562

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    problems with 2944_3562

    After successfully using a number of new features with the build previous to 2944_3562, I upgraded once more to 2944_3562 so that the printHTML() function would work properly, something necessary for our needs.

    Yesterday I worked on one specific new area of the application that didn't have any direct ties to any other components, etc, so I didn't make many changes to anything that already worked. Last night, I opened every component in build 2944_3562, dirtied something in it, and saved it because I've had issues before with patches and this seemed to fix it. I then published everything to the production server, also running build 2944_3562.

    Today I'm seeing a variety of errors that weren't there prior to that publish. I've re-published it all this morning, then shut down the A5 App Server, reinstalled build 2944_3562, and restarted the server, but none of that has fixed it. Errors today that didn't exist yesterday:

    Checkboxes in the search/filter section cause the search to return all records regardless of other search criteria. I've confirmed this in multiple components, with multiple checkbox criteria.

    At least a few different, unrelated Javascript conditional show/hide expressions in multiple components' Detail Views, some of which are as simple as MD_Review="Yes" and have never given me problems, are showing up in the Firefox Error Console and causing JS not to work in the Detail View.

    Anyone else having these issues?
    Tags: None
    #2
    Re: problems with 2944_3562

    Alpha's Jerry just confirmed with me problems with show/hide on containers in Detail Views, which is what I'm dealing with.

    I also let him know of my further investigation on the checkboxes issue. Selection of any checkbox criteria options in the Search Part causes all records to be returned, regardless of other search criteria entered. This worked prior to build 2944_3562 and when dirtied, re-saved and re-published from IDE build 2924_3560 (but still using the App Server build 2944_3562), the filters work as expected.

    Comment

      #3
      Re: problems with 2944_3562

      Originally posted by christappan View Post
      After successfully using a number of new features with the build previous to 2944_3562, I upgraded once more to 2944_3562 so that the printHTML() function would work properly, something necessary for our needs.

      Yesterday I worked on one specific new area of the application that didn't have any direct ties to any other components, etc, so I didn't make many changes to anything that already worked. Last night, I opened every component in build 2944_3562, dirtied something in it, and saved it because I've had issues before with patches and this seemed to fix it. I then published everything to the production server, also running build 2944_3562.

      Today I'm seeing a variety of errors that weren't there prior to that publish. I've re-published it all this morning, then shut down the A5 App Server, reinstalled build 2944_3562, and restarted the server, but none of that has fixed it. Errors today that didn't exist yesterday:

      Checkboxes in the search/filter section cause the search to return all records regardless of other search criteria. I've confirmed this in multiple components, with multiple checkbox criteria.

      At least a few different, unrelated Javascript conditional show/hide expressions in multiple components' Detail Views, some of which are as simple as MD_Review="Yes" and have never given me problems, are showing up in the Firefox Error Console and causing JS not to work in the Detail View.

      Anyone else having these issues?
      There is a bug with show/hide expressions that are applied to Containers in the Detail View. That has been fixed and will be in the next update (later today). Show/hide expression that are defined for individual fields, however, DO work correctly.

      However, there is NOT a bug in Search with checkbox controls as the video shows.

      http://screencast.com/t/ZmZiZjcyZTg

      Comment

        #4
        Re: problems with 2944_3562

        Despite it proving me wrong, Selwyn, I really appreciate the time and effort you put into proving me wrong. :)

        Seriously, thanks for the quick updates that fixes the show/hide on containers and for responding to this as well.

        I just figured out that I had set all my checkboxes to Search Style 1, which may have been bad design on my part(?) but functioned correctly on the build I was using (prior to any release candidates for 10.5--I think 2814_3539) but doesn't in the build 2953_3564. With build 2953_3564, if I set the checkbox search field search style to 0, it works regardless if I set the default search style to 1 or 2 in the Search Properties; however, if I set the checkbox field property to search style 1 or 2 it still returns all records.

        I know how to make it work for my needs, so if you want to look at it as a possible remaining bug, great--if not, I'm not going to bother anyone at Alpha about it anymore.

        Thanks again.

        Comment

        Previous template Next
        Working...
        X