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



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

Save Changes by Different Users

  • Filter
  • Time
  • Show
Clear All
new posts

  • Save Changes by Different Users

    I am one of three Supervisors of a Town's Voting List and I would like to know if there is a way to save changes by each individual

    Any help will be apprecited

  • #2
    RE: Save Changes by Different Users

    Please explain.

    Do you want to track the changes made by each individual like an audit trail?
    There can be only one.


    • #3
      RE: Save Changes by Different Users

      Hi Steve

      I want to track the changes made by each individual.

      Nip Lewis


      • #4
        RE: Save Changes by Different Users

        Hi Stan

        Yes, I want to track the changes by each supervispor.


        • #5
          RE: Save Changes by Different Users

          Two possible scenarios.

          Each user has their own computer attached to a network.

          Use Dr. Wayne's "getmachinename()" function, add a field to the tables in question, choose the critical field(s) that you want to track, add onChange event actions which store the result of the getmachinename() function to the field you have added.

          All users use the same machine to access Alpha.

          Add a global variable to your startup form, capture the person's name/initials/whatever to this variable before allowing further actions, proceed as above, substituting this result for the getmachinename() result.
          There can be only one.


          • #6
            RE: Save Changes by Different Users

            Another alternative is to create a new table to store the audit trail. The same answer would apply insofar as capturing the "changer's" identity. Then you would open the audit table and store the information about the change being made.

            I use the following attached to the onChange event of a field called "wtrpage" on a form based on a set:

            par = table.current(1) '- obtain pointer to parent table of set
            thisun = par.itm_cd '- capture the item code of the record being changed
            tbl ="moduser") '- open the audit table
            tbl.enter_begin() '- start a new record
            tbl.chgdt = date() '- store today's date to this new record
            tbl.user = getmachinename() '- store user info to this new record
            tbl.chgtm = time() '- store the time to this new record
            tbl.chgfld = "Wtr page" '- store the description of the field being changed (not the field name, just clearer)
            tbl.chgitm = thisun '- store the item code of the record in the main table being changed
            tbl.enter_end(.t.) '- end the enter
            tbl.close() '- close the audit trail table
            There can be only one.


            • #7
              RE: Save Changes by Different Users


              I am writing a program where my customer would take payments from his customer. Each payment will have a taken by filled out and stored in at least 2 places.

              I chose the second method and added a password. When my customer or his help start up, they have to sign in with a password. If they take a payment, their sign in name is attached and copied to another file that is encrypted. Their sign in name is attached to every sensitive thig they do.

              It is not that hard to set up



              • #8
                RE: Save Changes by Different Users

                I didn't mention that the main drawback to this method is that only the identity of the most recent "changer" is captured. Prior changes are overwritten.
                There can be only one.