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

Quirky Browse behavior

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

  • Quirky Browse behavior

    I’m baffled. Can anyone explain the following quirky behaviors?

    Quirk 1:
    Design a simple table comprised of two character fields. Open the empty table using <default browse> (i.e. double click the table) and then immediately try to exit without entering/creating a record and Alpha displays a warning dialog window asking “Save enter in progress?” even though no data is entered.

    Design another table with 3 fields. Open this empty table in <default browse> and Alpha doesn’t display the warning dialog window when exiting unless content is actually entered into the record and the exit action is invoked without having first saved the record. Just Hmmmm…..

    Now actually enter/save a record in each table as above. Then click on <new record> as if to add another record, but don’t enter anything and simply try to exit. Same odd results.

    Bigger Quirk 2:
    Use the same two-field table design and actually add/save a record, then click on <new record> and attempt to exit without entering data for the new record. Alpha again generates the warning confirmation dialog. Try the same thing with a browse displaying three fields and Alpha only generates the warning dialog when exiting after clicking on <new record> if data is entered and not saved. Now create a stored browse displaying only one field. Things really get weird. Alpha permits <new record> to be clicked even though the table is empty. If an exit from the browse is invoked Alpha will generate the warning dialog (even though no data is entered) but if one simply moves focus off the empty new record line back to a previously stored line, Alpha creates and saves a null record (i.e. one with no field contents) with no warning dialog displayed. Huh?

  • #2
    Re: Quirky Browse behavior

    this is normal behavior - if you open an empty table it is by default in enter mode, unless it is opened in a modal form

    it is normal, when you begin entering a new record, and try to exit for Alpha to ask what you want to do with the record - save it as blank? cancel it?
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    martin_w_cole@msn.com

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

    Comment


    • #3
      Re: Quirky Browse behavior

      Martin,

      Read his post a little closer. What he said was that if the table had 2 fields in it, it would create the message BUT NOT if there were 3 or more fields. I just tried it and he is correct. It should be the same both ways in my estimation.

      Comment


      • #4
        Re: Quirky Browse behavior

        I see what you mean
        Cole Custom Programming - Terrell, Texas
        972 524 8714
        martin_w_cole@msn.com

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

        Comment


        • #5
          Re: Quirky Browse behavior

          Thanks for the replys.

          Most bothersome to me is the behavior with only one field displayed in the stored browse. Click on <new record> and then click off to another row (stored record) and see what happens. New blank records are created with absolutely no warning.

          In the absence of an explanation pointing to something I'm missing, I am left to conclude these behaviors are bugs. Just surprised that a bug(s) of this nature have been run into and fixed eons ago with a product that's been out as long as Alpha.

          Guess I will have to prepare some samples and ship them off to Alpha for their response.

          I also have a some other quirks that consistently encounter but can't explain or resolve and will submit those for anyone's comment when I get done preparing some examples and expanatory text.

          Thanks again guys for your time and attention.

          Comment


          • #6
            Re: Quirky Browse behavior

            Douglas, the normal behavior for the browse object embedded in a form layout is to save pending edits when the user moves the record pointer in the browse or shifts focus to a different object in the form layout. I understand you to be saying that the new blank records are occuring in the single column browse even when no "edits" have been started. I share your concern. FWIW an easy work around for this is to cancel the save if a key field or group of fields is blank. You can do this in the CanSaveRecord event in field rules for the table.

            Comment


            • #7
              Re: Quirky Browse behavior

              That's precisely what I have experienced but only in cases of browses displaying one and only one field. Thanks for the suggestion about using a cancel in the CanSaveRecord event. That will probably suffice as a work around, but my thinking is that this behavior ought to be automatically trapped by Alpha and the developer shouldn't have to be bothered by having to define event rules to prevent it from happening.

              Comment

              Working...
              X