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

Unhandled Exception

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

    Unhandled Exception

    I've reviewed the other notes on this topic but did not find a "fit." I've applied 1431-1038 and 1454-1042 (never saw 1420-1037 that I am aware of).
    I need to know what to look for. I've recently had some major hardware changes (mother board replaced after smoking, new hard drive added, faster cpu clock.
    I accessed my backup made just prior to my board failure and still have the same mesage. Also got a "Cannot open multiuser file .MUF" when running some dbf's off of the backup CD.
    This message is occuring only on one of my major sets. The others have been working fine.
    Could changing the disc/folder names have caused a problem. If so, how would I go about fixing that, other than moving all of the files back to their original position. Again, this fault only occures on one major set and not the other five.

    #2
    RE: Unhandled Exception

    Cliff,

    I don't know about the 'unhandled exception', but the problem with the Multi-User File (MUF) file may be related to the media. Tell us how you're '... running some dbf's off of the backup CD. ' ???

    As background, the MUF file is created and updated by A5 automatically. It's part of the system used to prevent more concurrent uses of the program than have been licensed. The error message you're getting suggests that the MUF file is locked. May be 'read only' if it's sitting on a CD platter. If so, A5 can't update it, so it errors out. Could this be what you're seeing ?

    -- tom

    Comment


      #3
      RE: Unhandled Exception

      Tom, sounds logical on the MUF. I normally don't access my backups; just copy them back in the two times I needed them. Backups are created by Easy CD Creator 5 by roxio.

      On my other problem, I seem to have lost my major .dbf file in that set. I do not recall if Alpha5 was on one of my screens when my mother board went out. I was specifically attempting to down load some pictures from my camera. Why my back up has the same missing data I do not know. I'll have to work on that problem again before I have further information. Thanks on the MUF.

      Comment


        #4
        RE: Unhandled Exception

        Tom, on my Unhandled Exception problem, my .adb file gives this message. The .dbf's seem to be there except for the major one. How can I take a copy of the missing .dbf from a previous backup and put into the assembly of the .adb?

        Doing this I would be trying to keep all of the set work I had done. I am guessing that If I start another database and import all of the .dbf's I'll lose all of the screen and report work I've done at the database level.

        One strange thing that happens, when I double click on a list of the files for an .adb, Alph5v4 comes up as the program to open up the file. These are the files that go Unhandled Exception on me when I try to access them from Alph5v5. They were created in Alpha5v5.

        Any suggestion on which way is the best to bite-the-bullet and salvage what I can?

        Thanks.

        Comment

        Working...
        X