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

Default at end of enter.

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

    Default at end of enter.

    Does anybody use the "At end of enter, set default value if field not touched by user" setting for a default field value? If so, can you confirm that it doesn't work in forms? (I suppose I shouldn't have asked the first question but I'm finding it hard to believe anybody else in Alphadom is using it since it doesn't appear to work in forms. If anybody else is using it, I would think it would have been brought up a long time ago.)

    I set a field's default value to "At end of enter, set default value if field not touched by user" and it works perfectly in the default browse.

    (Well, sorta perfectly - the function that defines the default is triggered at the beginning of data entry also but it doesn't seem to enter the value at that point so I guess it's OK. I wanted to mention this "also at the beginning" issue because you'll probably run into it yourself if you test it.)

    However, in the default form it triggers at the beginning of the enter operation (just as in the browse) but NOT at the end. The obvious result is that the default value isn't set.

    FWIW: I confirmed the above by creating a user defined function to determine the default value - it was a complex calculation. I simply added a Debug(1) to the function to find out what was happening. As soon as I clicked the icon to start a new record in either the default form or default browse, the debugger started. When in the default browse, the debugger started both when starting the record and when saving the record. However, the debugger only triggered at the beginning when in the form.
    Tags: None
    #2
    Re: Default at end of enter.

    Tried it on my database where I have been using default value at beginning and can confirm that the default value does not record if "At end of enter, set default value if field not touched by user", when used on my default form.
    "Ollie, remember how dumb I used to be? Well, I'm much better now."

    Pete

    Comment

      #3
      Re: Default at end of enter.

      Thanks. I'll submit a bug report.

      Comment

        #4
        Re: Default at end of enter.

        Hi Cal,
        I'm finding it hard to believe anybody else in Alphadom is using it since it doesn't appear to work in forms.
        It just so happens I have used this in a recent mini-app on a form in version 8 and it works....so Thanks for finding this now as when this little app is moved to v9 (or later) it would have been broken. :)
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment

          #5
          Re: Default at end of enter.

          In case it takes awhile to get fixed, my solution was to just move the function to the CanSave Record event - with a little extra code to find out if we were in Enter mode and if the field was still blank:

          Edit: Oops. I forgot to include this line: (and, yes, I could have combined the IFs)
          tc = table.current()

          Comment

            #6
            Re: Default at end of enter.

            Cal:
            it works using an older build 1591-3193 so I don't know when it got broken

            Comment

              #7
              Re: Default at end of enter.

              I just heard back from my bug report. They've fixed it and it should be in the next patch.

              Comment

              Previous template Next
              Working...
              X