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

Debugger doesn't

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

    Debugger doesn't

    Hello,
    Does anyone have any insight on the strange debugger behavior. Debug has ceased to work in any meaningful way for me. The debug(1) does not bring up the debugger anymore, causes a large pause in the script execution, but no debugger. I can bring it up in view mode and select trace into, but it usually comes up with a blank screen when the next script is run. I will reload everything and see what happens, but his is tedious. I'm using build 230.

    Thanks,
    Jim

    #2
    RE: Debugger doesn't

    Script Debugger shows up on my start menu as a separate executable. Possible yours is damaged. Suggest reinstall.
    There can be only one.

    Comment


      #3
      RE: Debugger doesn't

      Discover something that may be of interest.
      I uninstalled and reinstalled A5. Now inserting debug(1) brought up the debugger however there was no sourse script in the debugger window, although you could press the 'step over' button and it appeared to be stepping through the script, but again nothing was showing in the debugger window. There were some old variables in the watch window from a previous script. Removing them caused the current script to appear in the debug window. Curious.

      Jim

      Comment


        #4
        RE: Debugger doesn't

        Hi Stan,
        Thanks for your reply. I could get debug to run, I just couldn't call it with debug(1), and it would come up without any source in the window when I ran it from the view menu. After reloading I found that old variables in the watch window caused my debug window to be blank.

        Jim

        Comment


          #5
          RE: Debugger doesn't

          Are your scripts password protected?

          I discovered that password protection can cause problems with debug. I think it can cause a problem if ANY one of your scripts is protected but I'm not sure about that.

          At first this bothered me but it's actually better protection for the developer.

          Comment


            #6
            RE: Debugger doesn't

            Hi Cal,
            Thanks for the quick reply. No I don't have any scripts in this database password protected. Are you saying that if any scipt in the database is password protected, debug() will not run on any scipt in this database?

            Jim

            Comment


              #7
              RE: Debugger doesn't

              Jim:

              I don't think that happens. If the first line of the script in which you have the debug(1) command begins with 'PASSWORD ABCD then the debugger does not fire. But this doesn't affect any other script as far as I know.

              I had a similar experience with my old machine in the office (running NT); the debugger failed all the time, and many times caused a program lockup. It was a real pita. I have another machine now (also NT) and the debugger never fails!

              Previously, I had to run the debugger from the menu (View/Debugger) then start the process I wanted to debug. When I did that the debug(1) command would pop up the debugger window. I never figured out what the problem was.

              Finian
              Finian

              Comment


                #8
                RE: Debugger doesn't

                Jim -- I had the same problem. I uninstalled and reinstalled twice. The second time fixed it.

                - Steve
                -Steve
                sigpic

                Comment

                Working...
                X