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

Possible A2CRDSYS.DLL bug

  • Filter
  • Time
  • Show
Clear All
new posts

  • Possible A2CRDSYS.DLL bug

    Possible A2CRDSYS.DLL bug

    I have a form with 3 Radio Button objects on it:

    Object name: ChkSub
    Field: VAR->lclSubWhat (Character)
    Type: Radio buttons
    Choices: 4

    Object name: ChkDomestic
    Field: VAR->lclDShip (Numeric)
    Type: Radio buttons
    Choices: 2

    Object name: ChkForeign
    Field: VAR->lclFShip (Numeric)
    Type: Radio buttons
    Choices: 4

    All variables are Layout variables.

    I have xBasic code in the ChkSub.OnChange event that hides or shows ChkDomestic and/or ChkForeign based on which
    button is clicked.

    If I close the form with either one of these objects hidden, I receive the follow error message:
    ALPHA5 caused an invalid page fault in module A2CRDSYS.DLL.

    If I force both of them to be visible before I close the form, I do not get the crash.

    Has anyone else ran into this?

    Charles Kistler

  • #2
    RE: Possible A2CRDSYS.DLL bug


    I just set up a dummy form with the 3 radio buttons and used the value in the first to hide or show the other radio objects. I used layout variables for the fields. No problem closing the form with the two radio objects hidden. The only weird behavior was that I needed to add a refresh after show so both would be visible. This was with A5v4.5 build 266. What version and build are you using?



    • #3
      RE: Possible A2CRDSYS.DLL bug

      A search of the message board shows that there was an update to the a2crdsys.dll earlier this year for v4.5. If you haven't already done so, go to the Alpha support site and download the newest build update. This may fix your problem.



      • #4
        RE: Possible A2CRDSYS.DLL bug

        Reply to Jerry's 2 messages:

        1) I do not have to refresh to have the other radio objects appear.

        2) I am using A5V4.5 266. Just purchased it a week ago.

        I just checked A2CRDSYS.DLL for a version number using Explorer, but AlphaSoftware didn't include it. It is dated 7/31/2001 (the date I installed A5V4.5) with a file size of 437,248 bytes. It would be nice if all of the files for A5V4.5 would include version numbers in their property pages.

        Thanks for the quick reply.



        • #5
          RE: Possible A2CRDSYS.DLL bug


          Well that takes care of the obvious. I show the same size file. Maybe you can zip up a copy of the offending table and related files w/o data so someone can test it on another system and see what happens. One possibility is a corrupted data dictionary for the table. If you haven't already, compact the database and see what happens. Try creating a new form with just the variables and the radio objects and see what happens. Sometimes the best approach is to simplify the form down to the very basic elements and then add other fields, scripts, buttons, field rules, etc one at a time until it blows up.

          Another possibility is a conflict with a video card. Occasionaly, a video conflict will create some odd problems. I work with one system that crashes only when print preview is maximized. The same app works perfect on other computers. Others on the board have mentioned conflicts with HP print drivers. So much for Microsoft plug and play.



          • #6
            RE: Possible A2CRDSYS.DLL bug

            I've compacted. I've tried the copy-the-form-and-paste-it routine, too.

            I'm going to recreate it from scratch. In past problems with forms, this has almost always cured any problems I've had. At least I know where I'm going when I do this! Something about doing extensive form re-designing seems to push the stability of the form and its elements over a line that can't be undone. This is speculation on my part, however. I've had my share of crashes. I enjoy twisting A5 to see what it can do.

            Video card problems? I'm using an ATI Rage Fury Pro and it could very well be the problem.

            Thanks again.



            • #7
              RE: Possible A2CRDSYS.DLL bug

              I believe I found out what's going on.

              I was assigning both a VALUE and TEXT to my option buttons when the form loaded. (I do not know in advance how many options will be present nor what the text will be.)

              For example, on the form Form, option 'n' of option button 'optChoice' is:

              :Form:optChoice.choice.list(n).text="Some Text"

              The field name assigned to the option button was a numeric type. It has to be a character type. So this works:

              :Form:optChoice.choice.list(n).text="Some Text"

              All's well that ends well. I haven't been able to find this in the help or documentation, though. Am I right?