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

A5 Crashing "Default form full. Not all fields will be displayed."

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

    A5 Crashing "Default form full. Not all fields will be displayed."

    Out of the frying pan, and into the fire.

    Running latest patch Build 1772-3208 7-Oct-2008

    Open A5, open my DB, go to Control Panel, select tab Tables/Sets, double-click on a SET (one of two sets currently defined)... first ERROR1 (screenshot attached), then ERROR2 (screenshot attached), then A5 abruptly closes. The set is not overly complex, with five tables making up the set. The other defined set does not cause this.

    A third error is sometimes generated, before A5 closes, something about at XBasic error.

    #2
    Re: A5 Crashing "Default form full. Not all fields will be displayed."

    Jon,

    Can you create a new blank form using the set? And from there add fields and such?

    By double clicking on the set, the default form may not be able to show everything, depending on how you have constructed the set.

    Regards

    Ed

    Comment


      #3
      Re: A5 Crashing "Default form full. Not all fields will be displayed."

      The first message has always been a part of the default form handler. I have never bothered to determine the actual count of fields that can be shown on the default form. Whatever the max is will be shown, with the rest left off. And also, the v9 max is greater than the v8 max. On one set I get this message in v8, but not in v9.

      As Ed suggests, just create a custom form for the set. This does not have the same limitation on field count.

      The second error is an "error". I would reboot to make sure your system is "clean" and see if error persists. Maybe download patch again.

      Bill.

      Comment


        #4
        Re: A5 Crashing "Default form full. Not all fields will be displayed."

        Fsi

        I have a form with a tabbed object with 8 tabs 11 linked browses, 30 calculated fields, 15 typein fields, 14 buttons and about 35 text blocks.
        Once I got the form filled message and when I went in to design mode
        everything was gone. Restored from a backup and everything was fine.
        Could not duplicate the message again. Even added a few items to the form
        with no problems. It would be interesting to know just what (in regards to what) the limits are.

        Comment


          #5
          Re: A5 Crashing "Default form full. Not all fields will be displayed."

          jon, as others have noted, the first error occurs when you have more fields in your table(s) than the "default form" can handle. It will not crash Alpha Five. It's simply a warning that not all fields are being displayed.

          As for the second error I suggest you build a simple form based on same set. Don't bother to populate it with all the fields. Does the form behave correctly or do you get the unhandled error exception? There are two areas that could be causing this: (a) the set definition itself; or (b) a table field rule that is misbehaving or was incorrectly defined. I'd trouble shoot this by opening the default form for each table in the set to verify that each will work correctly, independently of the set.

          Comment

          Working...
          X