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

Can't A5 be more specific about error codes?

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

    Can't A5 be more specific about error codes?

    I am running Steve Workings' error code script and it is wonderful but I noticed a curious thing about the error_code_get() function. I was trying to build different responses to the error handling scrip. The idea was to get different CASE commands to run depending on what error was captured by error_code_get().

    One case is when a database file was already opened and the script needed to open it RW_EXCLUSIVE. For some reason the error_code_get() function returned 1000 but the error_text_get() function returned "The process cannot access the file because it is being used by another process...c:program filesa5v4customer .dbf". This was the correct text for the error but try as I might I couldn't find this specific response anywhere, I traced every error message from 1 to 9000. So does anyone know what number is associated with this error text? I know that a work around for this problem is to use the text output from the error_text_get() function but a number would be better.

    The other case is when a database file doesn't exist. The text message I get is "the system cannot find the file specified", this is correct. But the error_code_get() function gives me 1000! How does it know the difference? And what number should a "file not found" be?

    the system cannot find the file specified

    #2
    RE: Can't A5 be more specific about error codes?

    Hi Greg --

    I haven't tested every code and msg the way it appears that you have. But my perception is that Alpha can't anticipate every error and code that will occur, but that they've built the best library they could at the time. When something happens that doesn't exactly hit one of the library entries, you get sort of a closest match.

    Keep in mind this is sort of a SWAG on my part. Maybe someone else knows otherwise.

    - Steve
    -Steve
    sigpic

    Comment


      #3
      RE: Can't A5 be more specific about error codes?

      Greg,

      I'm recalling this from memory, but I believe it is stated in the A5 manuals that DOS errors return 1000.

      Since DOS enduced errors map to Alpha 5 's error 1000, you must use the text error message to ascertain the differences. It would be nice if they did have different codes, but they do not.

      Regards,

      Ira J. Perlow
      Computer Systems Design & Associates
      [email protected]
      Regards,

      Ira J. Perlow
      Computer Systems Design


      CSDA A5 Products
      New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
      CSDA Barcode Functions

      CSDA Code Utility
      CSDA Screen Capture


      Comment


        #4
        RE: Can't A5 be more specific about error codes?

        What I don't understand is that the error code descriptions don't match what is in the book as well as what you see when you do an error_text_get(). In chapter 31 of the Reference manual there is a "general format for an error handler"

        error_handler:

        err= error_code_get()
        SELECT
        CASE err=
        message=error_text_get(err)

        RESUME NEXT
        CASE err=
        message=error_text_get(err)
        END SELECT
        END

        My problem is that I always get the value of 1000 in the err variable but for either case the message variable will have the correct value. Is there a way to get Alpha to reveal what it knows to the programmer? The error code values that I am looking for are really common...file is not found, table is opened exclusively by another user.

        Comment


          #5
          RE: Can't A5 be more specific about error codes?

          Thanks Ira for the heads up, I don't think that I will blow any more time chasing this one. Anyway I am getting a lot of success using the text generated by the error_text_get() for my SELECT CASE statements.

          Comment

          Working...
          X