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

Follow / Track Changes

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

    #16
    RE: Follow / Track Changes

    Allen

    It must have been broken a very long time, as I went back to the oldest A5 build I have and it doesn't do anything there either. I guess it wasn't a very popular feature if no one noticed it didn't work.

    Jerry

    Comment


      #17
      RE: Follow / Track Changes

      Jerry when I wrote that post I was working in V4 it works fine there. I didn't check it in V5.

      Comment


        #18
        RE: Follow / Track Changes

        Jerry
        It does work in a V5 browse

        If I recall, in previous versions the menu showed a tick if it was switched on, and also appeared to be the default - in other words if you didn't want that situation you had to go into the menu to switch it off. In V5 you don't know whether its on or off, but the default seems to be Off.

        Could be useful when switched on in a large table so you can 'hang-on' to the record in case you need to make further immediate changes without have to search for it. Obviously if all enters/changes are made on a form and not in a browse the whole thing becomes redundant.

        I believe the original question was to the effect "does it keep a log of enter/change activity". Now that's a whole new ball-game, and far beyond my capability to even contemplate.
        Colin

        Comment


          #19
          RE: Follow / Track Changes

          Please disregard my last paragraph - I see that Cal has already answered that one.
          Colin

          Comment


            #20
            RE: Follow / Track Changes

            Colin

            Thanks. I thought I was losing my mind, but it was stuck in the mud. I went back to V4 and tried it (never knew it was there either), and it does work in V4. A test in V5 shows it works there too. I guess I managed to turn it off every time I tried to test it. Since there is no checkmark to show its state, there is no way to know if it is on or off.

            It took some experimentation, but I think I see how it "works". I does seem to work only in browse layouts. I couldn't see any effect in embedded browses. As you indicate, it seems off by default. When ever a browse opens, it is off. Selecting the option turns it on and then it seems to work.

            Frankly, I don't see much purpose in it, since to make an edit, the record must already be visible.

            Jerry

            Comment


              #21
              RE: Follow / Track Changes

              Jerry,

              I remember now that I used it in v.4. I believe I only used it in embedded browses, as I rarely used plain browses, but then again, memory is a fickle thing. In my case I had an index: Status+Project_No. The status of a project would be adjusted at least once a week. If follow_changes was checked, when I changed the status, the pointer was still on that project when I saved the record. If unchecked, the pointer moved to the next record in the index order, and the project that I just changed the status of, "disappeared" from the current view (i.e. dropped to its corresponding slot in the index order). I found it very useful in that kind of circumstance. Make sense?

              Peter
              Peter
              AlphaBase Solutions, LLC

              [email protected]
              https://www.alphabasesolutions.com


              Comment


                #22
                RE: Follow / Track Changes

                Peter

                Thanks, that does make sense. I hadn't considered that scenario.

                Jerry

                Comment


                  #23
                  RE: Follow / Track Changes

                  I need to experiment with this, but I have had problems where I would make changes to a parent via xbasic, and it would move to a different record. I have been using xbasic to repositon it back, but this might account for the behavior.
                  Cole Custom Programming - Terrell, Texas
                  972 524 8714
                  [email protected]

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

                  Comment


                    #24
                    RE: Follow / Track Changes

                    THANK YOU FOR THE GREAT RESPONSES. I WILL WORK WITH IT THIS WEEKEND.

                    IT IS GREAT TO SEE SO MANY WILLING TO SHARE AND ADD IDEAS.

                    LYNDA

                    Comment

                    Working...
                    X