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

Cleaning up variables

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

    Cleaning up variables

    Hi,

    I was having problems with forms crashes upon entering. I read here that one thing that might cause this is entering forms with variables not filled. So I defined some variables in an autoexec script, others I filled upon entering forms with the same button that called the form. Some of the variable are defined on the form with the "V" button and duplicate names are used in global variables dim'd in other places.

    You see the problem - now I have variables defined in different places and I see a message in the trace window that a variable has been defined at a higher level.

    Overall, my crashes occur less often. But I still get some spontaneous crashes - or not predictable anyway.

    So here is my question, do I need to go through and be sure to only dim variables in one location? Does it hurt to dim them in multiple places? I cannot associate any new crashes with this mess! I assume variable are filled with different values, but this is okay, or a common practice.

    What are others suggestions and experiences.

    thanks

    Tom

    #2
    RE: Cleaning up variables

    I create must of my global variables in the table that contains the main menu, this way It is easy to check the names of all existing global variables ether in that table or by opining the xbasic explorer which will always show all global variables because it was started when the app was opened. Also for global variables I try using names that have some meaning to it as for local ill use short names that I would never use in a global variable.

    For Layout variables that I want to use on forms ill put them form using the "V" button and leave the value empty or enter a value that I want it to contain when the form is opened, the values can also be set on the oninit event of the form.

    For other local variables used in scripts must of them don�t need to be dimmed only the ones used for expressions, etc. and if you stick naming structure I mentioned above you should no conflicts

    I run problems with my apps but I don�t remember running into variables conflicts
    Daniel Weiss
    Daniel Weiss
    EZ Link Software

    Comment


      #3
      RE: Cleaning up variables

      Sorry!!
      and if you stick to the naming structure I mentioned above you shouldn�t have any conflicts
      Daniel Weiss
      EZ Link Software

      Comment


        #4
        RE: Cleaning up variables

        Thanks for your comments, I find them very helpful.

        Tom

        Comment


          #5
          RE: Cleaning up variables

          Thomas,

          In my experience I find that it is only when date variables have a null value that a form will crash, and this is only when certain rogue printer drivers are set as the default via Windows control. Also the crash will only occur if you have performed a print preview of any saved report, letter etc.

          Michael

          Comment


            #6
            RE: Cleaning up variables

            Thomas,

            In my experience I find that it is only when date variables have a null value that a form will crash, and this is only when certain rogue printer drivers are set as the default via Windows control. Also the crash will only occur if you have performed a print preview of any saved report, letter etc.

            Michael

            Comment


              #7
              RE: Cleaning up variables

              Michael,

              Thanks for your information. And that is a problem I have been having, but how to avoid it. I mean, I can set date variables in advance, but I always allow a choice of print or preview. Do you suggest I eliminate this option, and go direct to print. I would see this as a serious limitation.

              Thanks

              Tom

              Comment


                #8
                RE: Cleaning up variables

                ", but how to avoid it."

                Actually, it is simple to avoid.

                In the variable definition screen which you call by clicking the "V" in the form layout editor there is a space to give a default value to a variable. Put in Jan 1 1900 or whatever and the problem is solved.

                Hats off to Michael for figuring this on out a while back. We all know how much trial and error it took.

                Bill
                Bill Hanigsberg

                Comment


                  #9
                  RE: Cleaning up variables

                  No,

                  Bill is right, just give the date variable a default date so that it will never be a null value.

                  Michael

                  Comment

                  Working...
                  X