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 never hits debug point

  • Filter
  • Time
  • Show
Clear All
new posts

  • Debugger never hits debug point

    I have a function that looks like this:
    FUNCTION importXLSFile AS P (fileName AS C, batchNo as N)

    I use interactive window to call the function
    ?importXLSFile("filename", 1)

    The debug point is never hit, and the application runs as usual. How can i debug this function?

    Any help is appreciated. Thanks.
    Scott Moniz - Computer Programmer/Analyst
    REA Inc.

    REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
    If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
    contact us to discuss options.

  • #2
    Re: Debugger never hits debug point

    You might try commenting the Option statement out until you have it working, then see if it still works with the Option statement in effect.


    • #3
      Re: Debugger never hits debug point

      When creating a function, NEVER put any commands above the FUNCTION line. The only thing that should ever be above the FUNCTION line is comment lines. (Which includes the date/time info Alpha adds and a password line if you use one. You can also add all the comments you want but NOT any code.)

      Whenever there is any code above the FUNCTION line, Alpha won't recognize any changes made inside the function until you either rem out the stuff above the line or close the function in the code editor and re-open it. (Or maybe you have to close Alpha and re-open it. It's been so long I don't remember.)

      There is one situation where the changes will be recognized - if you click the lightning bolt in the code editor itself. BUT there is a better way....

      I used to put code above the FUNCTION line for testing purposes during development. This worked great when I clicked the lightning bolt (or pressed Ctrl-F5) but was a real pain because I kept forgetting to rem it out when testing in the Interactive Window or from a form.

      is very simple - put any "test code" below the END FUNCTION line.

      Your OPTION Encrypted_Tokens should be the first line of code inside the function. And note that I said the first line of code because it must come after any "Description:" line. You do know about description lines don't you?

      Oh, OK, since I can't find it in the Help files anywhere I'm sure most people don't know about description lines so here's the info:

      If a description line immediately follows the FUNCTION line in a global function, the description text will be displayed with the autocomplete text. (Although I don't believe it will display until A5 has been shut down and re-started. Again, I'm not sure if it's after the code editor is closed or A5 is closed.) The syntax for the description line is:

      FUNCTION myfunction as c (<arguments>)
      'Description:<description text>

      The description line is a comment line immediately following the FUNCTION line which must start with the word description followed by a colon. (Capitalization of the word description does not matter.) Any text after the colon will be displayed. In other words, it's usually best NOT to put a space after the colon - especially if the description text is long enough to word wrap. Only one line is allowed but if it is longer than one screen, it will word-wrap. (And, fwiw, I've created some that wrapped to 5-6 lines on a 1440x900 screen.)