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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Dialog box with Date Field with Printer Crashes

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Dialog box with Date Field with Printer Crashes

    To All,

    Attached is a sample file that will cause crashes with dialog boxes for all A5 versions (Ver 4.x and 5) when used with Adobe Acrobat (and also seems to crash with the HP2100 printer driver).

    Operating System most tested is Win 98, but should fail on all OS's

    It assumes you have the Adobe Acrobat Distiller installed (I have version 4.0)

    Here is the sequence to create the failure.

    1. Set Windows printer to default to something like an HP
    2. Start A5 (any version)
    3. Open the DialogTest database
    4. Run the Test script
    5. Just click OK on the dialog box
    6. Select Acrobat PDFWriter printer choice
    7. Now click OK to print file
    8. On save dialog box, just click on Save (the print file)
    9. Run the Test script again
    10. Alpha 5 should crash as you open the dialog box.

    To repeat, just close A5 and try again.

    An "apparent" cause is the presence of the date field on the dialog box. Change it to a character field and the problem goes away.

    One client with an HP2100 driver says it crashes everytime even without changing the default printer.

    John Zaleski has indicated a similar problem in the thread
    A5 crashes - solved???

    I sent Alpha Software on Feb 12th, 2001 a copy of the attached, but they had trouble reproducing the error (although had not tried it on a win 98 system).

    I'd be interested in what other people get for a result.

    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
    Tags: None
    #2
    RE: Dialog box with Date Field with Printer Crashe

    Ira,

    I tried it and it and on the second attempt it produced the following:

    ALPHA5 caused an exception 10H in module A2ENGINE.DLL at 015f:005e78b1.

    Windows 98
    4.10 1998

    John

    Comment

      #3
      RE: Dialog box with Date Field with Printer Crashe

      ME with Adobe 3.02
      I had to use the reset button - total freeze
      Cole Custom Programming - Terrell, Texas
      972 524 8714
      [email protected]

      ____________________
      "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

      Comment

        #4
        RE: Dialog box with Date Field with Printer Crashe

        Hello Ira,

        I ran your script then clicked OK then re-ran using my default printer. OK

        I ran again selecting a known rogue print driver HP840c and all kinds, lockups, and crash messages.

        I added one record to your table, created a form and edited your script to print preview only. The script runs fine on my default but bombs after a print preview when the 840c is set as my default printer.

        I shall test again after I have rebooted to get rid of that pesky .muf file.

        This would point to the crash problems that I have been experiencing with my distribution app on selected machines.

        Michael

        Comment

          #5
          RE: Dialog box with Date Field with Printer Crashe

          Michael,

          Would it make sense to test Ira's script with and without the numerical coprocessor activated?

          -- tom

          Comment

            #6
            RE: Dialog box with Date Field with Printer Crashe

            Ira,
            It didn't crash with the numeric data processor turend off.
            John

            Comment

              #7
              RE: Dialog box with Date Field with Printer Crashe

              Ditto,

              I have just tested my modified version of Ira's dbase on my laptop and it ran smoothly with the numeric processor disabled. I enabled the processor and rebooted twice and the A2 Engine crash was forced and the .muf file locked me out again with no sign of A5Halt.

              Michael

              Comment

                #8
                RE: Dialog box with Date Field with Printer Crashe

                And I bet if we turned off the CPU, Windows would never crash!!!

                {:?)

                -Ira
                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

                  #9
                  RE: Dialog box with Date Field with Printer Crashe

                  Ira,

                  I don't think that the form being opened as a dialog forces the crash, I never use dialog forms and have still experienced this crash scenario.

                  If we do disable our CPU's does that mean we can sleep at nights?

                  Michael

                  Comment

                    #10
                    RE: Dialog box with Date Field with Printer Crashe

                    Did not crash using an HP2100 on an HP Laserjet 2000 driver.

                    Crashed after printing (it printed fine) using HP laserjet 2100 Series PCL 6 driver (which is the automatic install with the HP 2100)

                    Windows 98
                    4.10.98

                    Comment

                      #11
                      RE: Dialog box with Date Field with Printer Crashe

                      Ira,

                      In Win 98 SE my A5 v4.03 crashes as you indicated, sometimes with an A2Engine.dll message and sometimes with both A2Engine and Mfc40.dll messages. Turning off the numeric processor does get rid of the crashes, but of course that is hardly a solution.

                      Interestingly, after I turned the numeric processor back on and rebooted with just a restart, I couldn't it to crash again until I did a cold boot. I used an HP4 with Postscript as my default printer. I thought the problem might have something to do with the fact that following your instructions meant there was nothing to print, but it crashes even when text is entered in your table, and even if a date is entered for your variable on the form.

                      I certainly hope this apparent bug cause someone to dig deep into A5 handling of dates in general, as I had a serious problem with date fields in the past. Specifically, when I indexed date fields in an intensive network environment with a large table I got all kinds of unable to add tag and record lock errors that went way when I got rid of the date indexes. Trouble was, the app needed the date indexes. By the time I did a work around with indexed character fields the client had give up and I could not thoroughly test the new scheme. The only sure thing was that the date indexes were the culprit. To make matters impossible, the errors only occurred when at least several users were doing lots of record updates to fields in existing records. I could never reproduce the problem on a single user environment. It seemed to require several users banging away on a 500,000 plus record file. I tested the network extensively and could never find anything wrong.

                      Ray

                      Comment

                      Previous template Next
                      Working...
                      X