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

Avoid Latest Update?

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

    Avoid Latest Update?

    I have run into several problems after running the latest update:

    1) On Oninit of a form I refresh the layout:
    topparent.Commit()
    topparent.Resynch()
    topparent.Refresh_Layout()

    and get an error "An unhandled exception was generated"

    2) My Multistate Buttons no longer work.

    Anyone else have similar issues?

    Don

    #2
    Re: Avoid Latest Update?

    No - haven't tried it yet. But, assuming that OnInit code is trying to do something to the form the OnInit is attached to, I see two issues with it:

    (1) "topparent" might be rather confusing or even refer to the wrong form since the form that is opening hasn't opened yet. You would probably be better off using "this" rather than "topparent". (That may be the source of your error message.)

    (2) That code, to the best of my knowledge, is completely useless. At that point the form isn't in Enter/Change mode so doing a Commit() shouldn't hurt anything but won't do anything either. Same for Resynch and Refresh_Layout - nothing has changed in the form or underlying table since it was opened (it isn't even really open yet) so there is nothing to Resynch or Refresh.

    I would recommend removing that code to see if that eliminates the error message. If so, try leaving it out and see if it doesn't work just fine without it.

    If you have a situation where it actually does do something, please let me know. I've been known to be wrong before. (Of course, it as a few years ago but it could happen again.:D)

    As for the multi-state buttons, I don't think I've ever used them in a finished app so I can't help you there.

    Comment


      #3
      Re: Avoid Latest Update?

      Cal,
      Cian at Alpha was able to reproduce and fix the error. One of the reasons I refresh the layout using the below code (produced also by action scripting) is to correctly display the order of my browse from multi-state button etc. I found that without refreshing it wouldn't display correctly (more code precedes the refresh layout code so I wanted to make sure the form refreshed). I agree though that there is no point in doing a topparent.commit(). I produced much of this in my infant stages of programming. Problem now is it may be in many other forms and I don't have the time to tidy things up. More importantly to me, it's an error that shouldn't be happening even if it is useless. Thanks for the input... once again, you've made good points that will prompt me to improve my programmings skills.


      Don


      topparent.Commit()
      topparent.Resynch()
      topparent.Refresh_Layout()

      Comment


        #4
        Re: Avoid Latest Update?

        Thanks for the info, Don. I wouldn't have expected that - especially in the OnInit event. The OnActivate would have seemed a better/more likely place to me. That way it would also happen if the user opens another form (or xdialog?) then returns to the original form. Of course, you may or may not want that to happen in those situations because I believe a Resynch might wreak havoc if the original form was in Enter/Change mode.

        Comment


          #5
          Re: Avoid Latest Update?

          the problem I have with resynch() when returning to a form (onactivate) is that it will frequently cause it to jump to a different record - sometimes, if I use it anyway, I will get the current record number, and when I come back and resynch check to see if its still the same recno and if noit fetch/find to it
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #6
            Re: Avoid Latest Update?

            Same problem here. I now recieve a "topparent.Commit()" error on OnInit during a form load and also my Close button no longer closes the form.

            Comment


              #7
              Re: Avoid Latest Update?

              Correct... close button didn't work for me either. Hopefully, Alpha will put out fix soon.

              Comment

              Working...
              X