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

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

Version 1749_4210

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Garry Flanigan
    replied
    Re: Version 1749_4210

    I just tried the new version and all grids and most UX's are fine, but my mission critical UX fails.
    When I open the UX on a record with the primary key set to a session variable, no fields load. When I try navigating it complains that primary keys are not loaded but the same UX works fine in old version. I tried making the UX dirty and re-publishing, all to no avail. Both developer and AppServer are same version. It fails in IE and Firefox.
    I have moved back to previous release and all is ok.

    Leave a comment:


  • allenj
    replied
    Re: Version 1749_4210

    I think that would be the last straw for me.....I have been waiting to see if there was any reason to resubscribe and this would be contrary to what I was told on the phone....

    Leave a comment:


  • compuaid
    replied
    Re: Version 1749_4210

    Just tried the full release version 1749_4210 with an April 2014 date and got the same message Peter saw...Important patches are required. Visit alpha downloads etc. and then it shuts down so it does look like Alpha is embedding a time expiration in their versions now to keep you from continuous use of the software without updating regularly (which you need a subscription for).

    Leave a comment:


  • DaveF
    replied
    Re: Version 1749_4210

    I installed build 1749_4210 on my staging server and everything looks good with the exception of a horizontal RadioButton control which I have set to "Render as Button List". The check mark was changed in build 1749 to appear before the text rather than after. There were some other minor changes made to the generated HTML for the RadioButton control. These changes increased the overall length of the radio button and caused the last button to overflow to the next line.

    Leave a comment:


  • mikeallenbrown
    replied
    Re: Version 1749_4210

    April Fools ....

    Leave a comment:


  • Peter.Greulich
    replied
    Re: Version 1749_4210

    FWIW: If you set your computer date to later in 2014 (I tried April 1, 2014) and run the latest (pre-release) patch (mine downloaded as 1749_4209) it loads telling you you need to update your patch and then shuts down.

    Leave a comment:


  • compuaid
    replied
    Re: Version 1749_4210

    You're right Mike. It looks like IE 10, 11 and Firefox were adding the final / while Chrome and IE 8 do not. Again, in prior versions of the server the ending / was optional. I'm going to have to have my clients update their web sites that link to their applications to add the ending / unless Alpha changes the behavior back.

    Leave a comment:


  • mikeallenbrown
    replied
    Re: Version 1749_4210

    Dropping the / from the URL's you provided doesn't work for me no matter what browser I try.

    Leave a comment:


  • compuaid
    replied
    Re: Version 1749_4210

    I figured out the bug (or at least breaking change) that was introduced. If you set your browser to the application directory and leave the page off (use the default page) and you don't place a closing "/" at the end of the URL in Chrome or IE 8 the application fails to load. This was not the case in the past nor is it in IE 10, IE 11 or Firefox. If you add the trailing "/" in Chrome or IE 8 it works but this means any hard links that were previously defined in other HTML pages must be updated.

    Example of one of our applications:

    www.compuaid.com:8080/paris/ - this works regardless of browser
    www.compuaid.com:8080/paris - works in IE 10, IE 11 and Firefox but fails in Chrome and IE 8

    Leave a comment:


  • Steve Workings
    replied
    Re: Version 1749_4210

    I just applied the upgrade to a relatively small and simple site. I was publishing to the site this morning using 1662-4182. After upgrading the app server, I loaded the site and ran through several of its features just fine in IE10, Firefox and Chrome. I did this with no further publishing or other adjustments. Exit the server, patch, re-start the server, go.

    I have reason to wait a couple days for other sites, but this gives me a good degree of confidence.

    Keep in mind that the upgrade downloads the new version of .NET can take a few minutes to download and install.

    Also pay attention to the note about the .NET install: If the .NET upgrade itself requires a reboot of the machine, the A5 patch will not have completed, and you'll need to run the patch again. You can most likely avoid this need to reboot by first exiting the A5 Server before running the upgrade patch.

    Update: I've also updated my development environment and been publishing, working with the updated site and all is well.
    Last edited by Steve Workings; 10-27-2013, 07:15 PM.

    Leave a comment:


  • compuaid
    replied
    Re: Version 1749_4210

    I've confirmed my findings on a development Application Server. Interestingly, this only seems to be occurring on my apps that use a Search/Grid on the index.a5w page and were originally developed in A5V11 but another app that I have that uses a login component and a tabbed UI and more complex UX dialogs developed exclusively in A5V12 is working.

    Further testing shows that if I republish only the index.a5w page it seems to correct the issue! I'll test further to confirm.

    Leave a comment:


  • compuaid
    replied
    Re: Version 1749_4210

    Hi Greg,

    I updated my findings (see above your post) and I'm forwarding this on to Selwyn. Whatever the issue, it appears to be browser specific with only Firefox working currently on all platforms.

    Leave a comment:


  • gregincolumbus
    replied
    Re: Version 1749_4210

    Wow Brad! Glad you were able to roll back.

    I am with you....hope they correct the issue before Nov 1st. I can't afford to have the WAS go down......currently in a time-sensitive window for registrations

    Thanks for letting us know about your experience.

    Leave a comment:


  • compuaid
    replied
    Re: Version 1749_4210

    I installed the update today on our Windows 2008 production server (it did require an install of .Net Framework 4.5 and a reboot) and after the install I could not access any of our web projects when using Chrome on any platform. The sites work with Internet Explorer 10 and 11 on Windows 7 and 8.1 respectively and Firefox on all platforms but also fails with Internet Explorer 8 on Windows XP. All I get is a message "NO DATA RECEIVED" and the error was ERR_EMPTY_RESPONSE. I installed the full version of 1749-4210 Server thinking maybe something didn't get updated in the patched version but still had the same issues. I finally went back to version 1620-4172 and everything is working again. If this is going to be a mandatory update then I hope they get this issue resolved as it appears that right now I cannot run the latest server version.
    Last edited by compuaid; 10-27-2013, 02:40 PM.

    Leave a comment:


  • mikeallenbrown
    replied
    Re: Version 1749_4210

    I see now ... I guess the other page hasn't been update yet.

    -Mike

    Leave a comment:

Working...
X