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

Debugger Crashes in both V8 and V9 Desktop

  • Filter
  • Time
  • Show
Clear All
new posts

    Debugger Crashes in both V8 and V9 Desktop

    Has anyone experienced debugger crashes in Desktop Version 8 or 9? If I open a db (Alpha .adb) in the File Open Dialog (in the debugger), the debugger hangs, and usually within 60 seconds I get the "...not responding" windows message. I then have to end the Alpha app.

    Scripts are involved, but minor (and run without error).
    The scripts are attached to form that basically prompts for a filename from the user, opens that file for read-only (shared), does a binary read (~3400 bytes), then closes the file.

    Some app/system info: I am running on Alpha V8 (build 1980, System Addins build 3163). Alpha V9 (build 2095, System Addins build 3264).

    V8 runs on an XP desktop and an XP Pro notebook.
    V9 runs on a Vista desktop and on the same XP Pro notebook.

    Any help appreciated.


    Re: Debugger Crashes in both V8 and V9 Desktop

    Nope. Though sometimes my own scripts can hang the system.

    suggest you post a sample for us to run on our machines, with instructions to follow so we are able to faithfully retrace the steps you take that lead to the hang.


      Re: Debugger Crashes in both V8 and V9 Desktop

      If I understand your sequence.

      You have a database open.
      You use the View menu, Debuggger, to open the Debugger.
      You use the File menu in the Debugger to select another database to open.
      Alpha hangs.

      It does for me but I am not surprised. I would never have thought to try that. What are you trying to do?
      There can be only one.


        Re: Debugger Crashes in both V8 and V9 Desktop

        All, thanks for your reply. Possibly my misunderstanding of the debugger in V8/V9, but since no code was displayed in the debugger pane, I presumed I had to open the (current) db using that dialog. I am doing some additional debugging on the Vista box. I've also changed the preferences settings to auto-run the debugger when a script runs, and so far (on the Vista box), using the auto-run hasn't crashed.

        I may have to re-install V8/V9 on the notebook.

        I'll update my post after additional testing.

        Thanks again for the replies.



          Re: Debugger Crashes in both V8 and V9 Desktop

          The general usage when you have a script that is having problems is to insert the line


          before the portion of the script that is likely causing trouble.

          The debugger will open when the script is run and you can watch the execution and any values you want.
          There can be only one.


            Re: Debugger Crashes in both V8 and V9 Desktop

            Thanks Stan,

            I'll put that in there...I should have done that in the first place.

            Interestingly, the debugger is more stable on the Vista box (but it does have more horsepower than the notebook and is dual core).

            A variables show up in the watch pane, but there are values assigned to them (e.g., filename, filename pointer, filename length, etc.) The variables are as defined are global and don't conflict with other variables.
            Last edited by Richard Kosick; 04-05-2010, 02:28 PM. Reason: Added post-script


              Re: Debugger Crashes in both V8 and V9 Desktop

              no variables show up in the watch pane
              Just to be sure we're on the same page.

              They don't just "show up". You have to enter the variable names you want to see in the Example area and the values will be shown in the Value area at the bottom of the debugger window.

              You can also create "examples" on the fly like

              There can be only one.


                Re: Debugger Crashes in both V8 and V9 Desktop

                and usually within 60 seconds I get the "...not responding" windows message. I then have to end the Alpha app.
                I hope you don't end Alpha or any other application just due to this almost meaningless Window's message---it will occur whenever anything is using almost all the cpu cycles--just means that it cannot be used due to other work being doesn't mean anything else. I have to wait sometimes quite a few minutes for something intense to finish and then, when it does finish, the "Not Responding" message disappears.

                Of course there are times when it really DOES mean that that Windows has frozen up completely with no hope of its returning on its own........ :)

                Just a FYI really......
                It is only when we forget all our learning that we begin to know.
                It's not what you look at that matters, it's what you see.
                Henry David Thoreau