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

HELP - Rendering problem after server upgrade - TIME SENSITIVE

  • Filter
  • Time
  • Show
Clear All
new posts

  • HELP - Rendering problem after server upgrade - TIME SENSITIVE

    A couple days ago I upgraded my computer to the latest build.

    The first thing I noticed is I was now being asked if I wanted to pre-render my UX - this was the first time I had seen this. So for the new UX I said yes. I published it and found the arguments were not working correctly. I then upgraded the server and all worked well.

    This morning all the UXs that were working before are not working now, only my new one.

    I have a menu bar and it loads various UX components. At first if I choose my CUSTOMERS tab i get the Working... notice - as if there was no security. I figured it had to do with the pre-render property. So i turn it on and republish. Now the page loads, the working notice disappears, but everything is BLANK.

    Any idea what is happening? My UX are also blank in working preview.

  • #2
    Re: HELP - Rendering problem after server upgrade - TIME SENSITIVE

    You have to be careful using pre-rendering. Some of my uxes load fine and others do not. I typically do not pre-render any of my components. There is an explanation about pre-rendering however I have not been able to sort it out and understand why some work and others don't. I would re-save all of the components and turn off pre-rendering.
    Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO.


    • #3
      Re: HELP - Rendering problem after server upgrade - TIME SENSITIVE

      I can confirm that pre-rendering is hit and miss for me too. Sometimes it works great and other times it either renders the UX incorrectly or the arguments in the UX do not populate. Every time I've encountered this if I turned pre-render off my component runs fine. I haven't reported this to Alpha because I just don't have a lot of extra time to come up with a test case. This by the way spans many builds going back some time. It isn't a recent phenomenon.

      I'd turn off prerender and test your components again. Maybe "recalculate all controls" in the "broken" UX's.
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Independent Developer & Consultant


      • #4
        Re: HELP - Rendering problem after server upgrade - TIME SENSITIVE

        Turn off pre-render and it will turn itself back on. Make sure you turn it on then choose ask on each save. Then on the save choose no-never. However, it will keep asking you every time you save. I'm with Mike, I haven't reported this yet either. I don't know how to build a test for this one.


        • #5
          Re: HELP - Rendering problem after server upgrade - TIME SENSITIVE

          I know you said "build" but, if your talking about "pre-releases" read on...otherwise ignore.

          I wouldn't say that it is all related to the Pre-render either because I just reverted back a couple builds to the January 10th pre-release because of a rendering issue with a UX that has a very simple list control - it just would NOT render, the two builds after the one of the tenth, my other UX's wouldn't render so it was hit and miss. Google chrome said that there was a missing ) or something in a where clause in one of their a5 javascript functions but I really haven't had time to report the error either.
          The pre-render is interesting for sure BUT I would like to see some clearly written rules on making session variables work, etc. To get around a session var that my list control filters on, I created an arg based on a variable that is a session var this seems to satisfy the pre-render requirements but I have had a couple of issues where some args that are control defaults come up empty and nothing gets submitted to the database for the field that should be defaulting to an argument value.
          It is not every time - so it could be an issue I have introduced.

          The time saving of a pre-render though is amazing though <---double positive!
          So as I said,
          NWCOPRO: Nuisance Wildlife Control Software My Application: "Without forgetting, we would have no memory at what was I saying?"