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

Method to 'see' if new record has been touched

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

    Method to 'see' if new record has been touched

    When entering a new record, how can I tell if the record has been touched, ie. data entered in fields by the user.

    I can use the OnChange event on EACH individual field to change a session or layout variable, but was wondering if there would be a more all inclusive/less laborious way to accomplish this.

    For example: if you open any default browse, and click on a new record at the bottom, and then click back off, it just goes away. But if you click on a new record, and then type something in one of the fields, and then click back off of it, alpha saves the record. How does alpha know the difference, and how can I intercept this info in a form?

    Thanks for your time. Dan
    - Dan Hooley
    - Custom Desktop or Web database development -

    #2
    Re: Method to 'see' if new record has been touched

    Dan,

    Look at the bottom of this web page. There is a pretty good discussion on this subject. "Similar Threads"

    Regards

    Ed

    Comment


      #3
      Re: Method to 'see' if new record has been touched

      Ed thanks for the reply! If this is what you mean, its not exactly what I am talking about (although there was some good information there that I used).

      What I am trying to figure out is the difference between these two scenarios:

      1. If you open up a form (any default form), and click on the 'new record' button, now your curser is blinking in the first field of a brand new blank record - nothing has been entered in any of the fields yet. Now, without doing anything else, you close the form (click the red X), I get no message and nothing is saved.

      2. But, if you open the form and enter anything in any field, and then close the form, Alpha will ask if I want to save the record.

      How does it know the difference? Obviously, in the second case, Alpha knows the 'new' record has been "touched". I would like to be able to click a button and tell which of the 2 above modes I am currently in without saving the record.

      Thanks, Dan
      - Dan Hooley
      - Custom Desktop or Web database development -

      Comment


        #4
        Re: Method to 'see' if new record has been touched

        If you have no default or auto-increment fields or numeric or logical

        alltext(table.current(1).name_get())

        will be blank for a new record ("") and will hold some character value(s) for a record where entry has begun.
        Last edited by Stan Mathews; 10-29-2009, 02:51 PM.
        There can be only one.

        Comment


          #5
          Re: Method to 'see' if new record has been touched

          Thanks Stan. I do have both default and auto auto-increment fields.

          Very interesting idea, though. I would have thought the .name_get() function would have returned the name of the table.
          edit: I see now it is the 'alltext' function that is returning the text...

          Dan
          - Dan Hooley
          - Custom Desktop or Web database development -

          Comment


            #6
            Re: Method to 'see' if new record has been touched

            Test this on a form as the script for a button.

            ui_msg_box("",alltext(table.current(1).name_get()))

            and see what is returned after creating a new "blank" record.

            Then you can test whether data entry has begun by comparing

            alltext(table.current(1).name_get()) to that string.

            I would have thought the .name_get() function would have returned the name of the table
            It does.
            There can be only one.

            Comment


              #7
              Re: Method to 'see' if new record has been touched

              I just thought of that too...

              I'm thinking of putting the first string into a session or layout variable when the form first goes into enter mode (new record button pressed) and then comparing the value in that variable with the current 'alltext' string. If they match, the record has NOT been touched, and if they do not match, the record HAS been touched.

              Will test and let know if I have any more questions.
              Thanks, Dan
              - Dan Hooley
              - Custom Desktop or Web database development -

              Comment

              Working...
              X