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

Crashes following upgrade to 4.5

  • Filter
  • Time
  • Show
Clear All
new posts

  • Crashes following upgrade to 4.5

    I have experienced the following problem since upgrading from Version 4.03 Build 230 to Version 4.5 Build 263.

    I have a form, which has an order of PICKING_NO and a Print button on it which prints the current record. It has the following Code attached to it.

    dim A_ASK_PRINT as c
    A_ASK_PRINT = ui_get_radio("Print Picking Ticket No.:"+space(1)+PICK_HEAD->PICKING_NO, 1, "Print", "Preview")
    if A_ASK_PRINT = "Print"
    goto print
    elseif A_ASK_PRINT = "Preview"
    goto preview
    goto cleanup
    end if
    current_record = alltrim(str(recno(),10,0))
    :Report.print("Pick Ticket(Current)","BETWEEN(RECNO(),"+ current_record+ "," + current_record+")")
    goto cleanup
    current_record = alltrim(str(recno(),10,0))
    :Report.preview("Pick Ticket(Current)","BETWEEN(RECNO(),"+ current_record+ "," + current_record+")")
    goto cleanup

    I have a second form ("Create ConN") which has an embedded browse in which I want to display only records where a field (CONSIGN_NO) is blank. I have created an ON ACTIVATE event which is:
    tbl = table.current()
    indx = tbl.index_get("noCN")

    After I have used the Print button on the first form and then tried to load the second form with the following code:

    if is_object("Create ConN") then
    Create ConN.activate()
    :Form.view("Create ConN")
    end if

    I get both the following messages and Alpha will not let me continue or re-load the application without re-booting the PC.

    ALPHA5 caused an exception 10H in module A2ENGINE.DLL at 0167:005e78b1.
    EAX=00000044 CS=0167 EIP=005e78b1 EFLGS=00010212
    EBX=00da7290 SS=016f ESP=00da6dec EBP=00da6e04
    ECX=00000000 DS=016f ESI=00da7690 FS=4a8f
    EDX=03b428dc ES=016f EDI=00da726c GS=0000
    Bytes at CS:EIP:
    dc 1d d8 90 63 00 53 56 57 df e0 9e 0f 82 fe 00
    Stack dump:
    00da726c 00da7690 00da7290 00000000 00000000 00000000 00da7274 005f0151 000003ff 00000000 03a213f1 00da76e2 00da7690 00000000 4145485f 00000044

    ALPHA5 caused an invalid page fault in
    module MFC40.DLL at 0167:5f8012b6.
    EAX=00000071 CS=0167 EIP=5f8012b6 EFLGS=00010207
    EBX=00000004 SS=016f ESP=00dafa94 EBP=00dafae0
    ECX=00000000 DS=016f ESI=0000071c FS=4a8f
    EDX=00000000 ES=016f EDI=027fdfc8 GS=0000
    Bytes at CS:EIP:
    f7 71 08 8b 44 24 0c 89 10 8b 41 04 85 c0 74 12
    Stack dump:
    027fdfa8 5f8012ef 0000071c 00dafaa4 ffffffff 5f8048a8 0000071c 00dafac0 00c80288 00000000 00000004 5f80129f 5f82c034 00c802d0 00c801b8 00c801b8

    Any ideas?? Thanks.
    Jenny Earnshaw
    BusinessPlus (Letchworth) Ltd

  • #2
    RE: Crashes following upgrade to 4.5

    My first check would be on the table containing the index 'noCN'. Make certain the index does still exist. If it does delete it and re create it.



    • #3
      RE: Crashes following upgrade to 4.5

      Thanks for your help. I think I may have discovered what is causing the crashes. The crashes occur after almost every print preview when using my HP Deskjet 990cxi printer as the default printer. If I change the default printer the crashes appear to stop.

      I have tried several of my applications and all crash after a Print Preview using the HP Deskjet 990cxi.

      I did check all the indexes and even deleted and rebuilt the index file before I discovered the link with the printer.
      Jenny Earnshaw
      BusinessPlus (Letchworth) Ltd


      • #4
        RE: Crashes following upgrade to 4.5


        Glad that you have discovered the cause, but the cure would be of interest, I have come up against this problem myself in the past after opening a print preview. Switching the default printer often stopped the problem but was not a satisfactory solution.

        I am curious to know if the same printer and settings triggered the crash before V4.5



        • #5
          RE: Crashes following upgrade to 4.5

          I think this printer was causing problems last week. I only installed it last Monday and was working on one of my applications last week on Version 4.03. and was having the same crash. As I only tested Print Preview a couple of times I didn't link the crashes to the printer but am sure they were the same two messages.

          Therefore, I think it is the printer not the upgrade. It ia brand new HP Deskjet 990cxi. I am designing it for a client who will be using an old Brother laser so don't think I'll have the same problem there!

          Wonder if any one else is trying to use this printer with Alpha Five. By the way it crashes Alpha Five when printing to it as well as Print Previews and as it is the printer that wins all the review tests (in UK anyway!) this might be a problem for Alpha.
          Jenny Earnshaw
          BusinessPlus (Letchworth) Ltd


          • #6
            RE: Crashes following upgrade to 4.5


            Strange but I had a simialar experience only last week. I visit a potential client who wanted a second look at my application and installed my app with V4.5 runtime and experienced embarassing crashes.

            I imediately blamed V4.5 since I had demoed the app previously on his computer loaded with V4.03 with no problem. But on reflection the client had just installed a new printer and this may well have been the cause of crashes. Unfortunately, I do not know the make of his printer, all I know is, it incorporates, copier, color and is huge. After the embarrasing crashes, I am not that welcome to enquire further.

            I would loke to hear of other encounters with printer conflicts and their cures so that I can be prepared.



            • #7
              RE: Crashes following upgrade to 4.5

              I am going to do some more testing tomorrow but I have about 6 applications that I have designed which have never caused crashes before. Now if print and then load a form A5 crashes and it is since I installed the HP Deskjet last Monday.

              I thought it was Version 4.5 at first but I remember having the same messages last week after installing the printer and before the Alpha upgrade.

              Maybe your client's printer was one of the combined HP printer/scanner/copiers.
              Jenny Earnshaw
              BusinessPlus (Letchworth) Ltd


              • #8
                RE: Crashes following upgrade to 4.5

                I asked this board about printers before buying an HP2100. I had a horrible time as I wanted to print some reports for a board meeting (I was treasurer, now secretary, for a contractors association). I used Excels print to fit option on a landscape page and the whole thing locked up. Next I had a landscape report from A5 lock up. I spent a LOT of time checking cables etc, talking with HP support. The printer properties paper source was set to tray1 (which had paper, and was the correct source) but at best it would print as manual - which requires a button pressed on the printer on each page. By setting this paper source choice to Auto it usually works. I haven't figured the other issues yet.

                Cutting through the fat - I think HP printer drivers are not too rugged. Probably trying to please too many machines under too many circumstances...