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

Field Rules - Field Events

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

    Field Rules - Field Events

    This from the Help file on Creating Field Rules
    When you click on a field, form or browse, a series of events happen.
    Evidently, the OnWriteField and OnWroteField field events DO NOT fire when editing in a browse, only a form. Have tried it on a default browse and a default form. I put a msgbox and debug() in both of these events to test. It seems to only fire from a form, not when editing in a browse.
    Is this the case or am I missing something???
    Ernie

    #2
    Re: Field Rules - Field Events

    Also found this in the Browse Object Events.
    The following sequence of events were generated when an operator moved the cursor to a embedded browse, selected a row, changed one of the entries, and moved the cursor off the embedded browse.

    Sequence of Events for Embedded Browses

    Occurance - Event - Type

    15 - CanWriteField - Field

    18 - OnWroteField - Field
    This DOES NOT occur in my testing.

    Have attached an app with one table. There is a form and a browse that have two fields on each. Each have a msgbox in the CanWriteField event. Change field values in both form and browse. You get the msgbox only when changing values in the form.
    Also put an OnChange event in the "Events" method of the browse just like the help says you can do, but it doesn't do anything either.
    Ernie
    Last edited by enstorms; 02-23-2010, 12:46 PM.

    Comment


      #3
      Re: Field Rules - Field Events

      Testing only the CanWriteField event everything seems to work the same in vers 10 as it did in vers 9. I get the message box whether the change occurs in a field on the form or whether the change occurs in the embedded browse.

      My sample kit is attached. I changed your message box statement a tiny bit. Not sure it makes a difference, but wanted to alert you.

      Comment


        #4
        Re: Field Rules - Field Events

        Hi Tom,
        This is kind of strange. If I open the form, click on the calendar, select another date, it doesn't fire. If I type in a date such as 021510, then tab out of the field, it fires. Now I can use the calendar button and it does fire. But I have to type in a date first in one of the fields.?????
        Ernie

        Comment


          #5
          Re: Field Rules - Field Events

          Ernie, I do very little with the CanWriteField event so I'm unable to comment on what you're seeing. When I need the degree of control you seem to be striving for I never use the embedded browse object. Good luck with your project.

          Comment


            #6
            Re: Field Rules - Field Events

            Thanks for your efforts, Tom. To me, this seems to be a straight forward event, based on the Help file. Alpha's browse features leave a lot to be desired. On the surface, they seem to be very flexible, until you try to use some of that flexibility.
            Ernie

            Comment


              #7
              Re: Field Rules - Field Events

              Well, I may have discovered what does seem to work. My date fields are generally set to Control Type "Type in". I changed the Control Type property in the browse to "Calendar". Now the events seem to be firing as advertised.
              Ernie

              Comment

              Working...
              X