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 Record events mix up

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

    Field Rules Record events mix up

    1-The Onchange event in field rules fires up on delete as well!
    2-If you have an OnEnter or CanEnter event and if you are in "change" mode, on saving you get a message "Must be on Entry Mode".

    Anyone with similar experience? any explanations?
    Thanks

    #2
    Re: Field Rules Record events mix up

    Have not seen this. Might help if you post a working example.

    When a record is "deleted" in Alpha Five it's not physically removed from the table. Instead a hidden field is changed, and the record is saved to disk. I believe this is why the OnChangeRecord event will fire when the record is marked for deletion.

    -- tom

    Comment


      #3
      Re: Field Rules Record events mix up

      Tom:
      That makes sense, but then why have an Onchange event and an OnDelete event?
      Here is an example...
      Last edited by G Gabriel; 05-11-2007, 05:18 AM.

      Comment


        #4
        Re: Field Rules Record events mix up

        Gabriel, I guess because not all changes are deletes, but some are. I think OnChangeRecord fires when the change begins, but has not yet been commited. I think OnDeleteRecord fires when the record has been deleted.

        From the help file:

        The A_DELETING_RECORD Variable - Useful in Change and Save Events

        To Alpha Five, changing the value in a field, and deleting a record, are both changes to the current record, and both actions trigger the Change and Save record events. This makes it impossible to distinguish between an effort by the user to change a record, or delete the current record. The reason for this is that a record is "deleted" by changing the value in a special "hidden" field in the record.

        The A_DELETING_RECORD variable allows you to distinguish between deleting and changing a value in a field. A_DELETING_RECORD is set to .T. during a record delete, and to .F. when the record is being edited.

        With this variable, you can write scripts that do something when the user makes a change to a field value, but not when they delete the record.

        Comment


          #5
          Re: Field Rules Record events mix up

          I think OnChangeRecord fires when the change begins, but has not yet been commited
          Wouldn't that be: CanChange?

          I think it's a bug.

          Comment


            #6
            Re: Field Rules Record events mix up

            Don't know what "it" you may be referencing but I think things are working as designed.

            My language has been a bit sloppy. "When the change begins" can be interpreted several different ways I suppose.

            I think CanChangeRecord event fires before the change begins. (before the field value changes in the record buffer but after the user has struck a key)

            I think OnChangeRecord event fires when the change begins. i.e. when the field value is changed in the record buffer but not yet committed to disk.

            Perhaps I'm wrong, but I've always assumed the table goes into change mode when the record buffer is changed by the user. When the table goes into change mode I'm used to thinking of this as the change having begun.

            -- tom

            Comment


              #7
              Re: Field Rules Record events mix up

              Don't know what "it" you may be referencing
              The fact that the onChange event fires also when you delete the record, as in the example attached.

              Comment

              Working...
              X