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

Anyone else experience this?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Anyone else experience this?

    OK, I know I've been posting a lot lately but this all came about because, as I've mentioned, an application which has been running fine for at least as long as I can remember suddenly went crazy when I made a small change to the code in a grid (and updated Build versions of both Development environment and Application Server).

    I've been tearing what little hair I have left out trying to troubleshoot this and I've come across a curious situation: I have an archive of code from February, 2018, before all the s**t hit the fan. I expanded it into a test directory, pointed my Development environment to it and then published it to and tested it on the test server. Everything went fine, worked great. Now here's the rub: If I go into the problematic component and make ANY change, say I comment out a line in a client side event handler (doesn't change any of the code) and then re-Publish, the grid starts to freeze. EVEN IF I GO IN AND ERASE THE CHANGE, the grid continues to freeze. If I make a change to other components I have no issue.

    So my question is: Has anyone had an experience like this? If so then, please, did you find out what it was? If not then do you have any idea why I can publish the original files but if I make the slightest change to the problem component all hell breaks loose? What does the Alpha Development Environment do differently in republishing a component than when it simply publishes an untouched one?

    I guess one possible answer is that the component is somehow "corrupt", but I don't want to have to rebuild it from scratch if I don't have to. I have actually tried reverting my development environment to versions that were released at the end of 2017 and still the same behavior.

    Any ideas welcome, as I say, I'm reluctant to rebuild the whole thing but I may have no choice.

    Edit: Well, for some reason, the issue appears to have been from the beginning the Conditional Row Coloring in the grid. Once I modified/removed that the grid came back alive (I had code to emulate alternate row shading and the condition which tried to determine whether the current row was even was hanging). I'll worry about the aesthetics later. Just in case this helps anyone else plagued with sudden, unexplained grid hanging. :)

    Norman
    Last edited by nlk10010; 07-04-2018, 03:02 PM.

    #2
    Re: Anyone else experience this?

    Same can happen (from time-to-time) with the list control when saving a row, if Conditional Row Coloring is on. - Worth remembering.
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)

    Comment


      #3
      Re: Anyone else experience this?

      The mystery is why the grid worked fine originally and when I published it after retrieval. It was making ANY change to the component's code and then re-Publishing that set off the freeze and there was no going back. Even when I used an old Build of Alpha.

      I still have issues with the grid not refreshing directly after an insert, but I'll do some more research on that.

      Thanks very much for the commiseration and info, Pete.



      Norman

      Comment

      Working...
      X