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

don't allow to edit the data in the past

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

  • don't allow to edit the data in the past

    Hi all,

    Please recommend me what command is the best to protect the data from user to edit it?
    I have table and user will key in it everday. Usually user can press Page up and PageDown to view and edit the data from form.
    How and what command I have to use to protect user to edit the previous data they key in yesterday or the day before yesterday. I don't want them edit the data in the past. They can create and edit only with in current day

    I know the modal and modeless but I don't know how to force form to modal if it's not today. (if it's not today and form will be setup to modal)
    I don't know other command that meet this requirement.

    Thanks
    Peter

  • #2
    Re: don't allow to edit the data in the past

    In the OnActivate event:

    Code:
    [COLOR=Blue]t =table.current()
    [/COLOR]
    [COLOR=Blue]If t.date < date()
    [/COLOR]
    [COLOR=Blue]This.allow_change(.F.) 
    [/COLOR]
    [COLOR=Blue]else 
    [/COLOR]
    [COLOR=Blue]This.allow_change(.T.) [/COLOR]
    [COLOR=Blue]end if[/COLOR]
    You might also need it in the OnFetch event if you allow fetching.
    Peter
    AlphaBase Solutions, LLC

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


    Comment


    • #3
      Re: don't allow to edit the data in the past

      In the OnActivate event:
      Code:
      t =table.current()
      If t.date < date()
      This.allow_change(.F.)
      else
      This.allow_change(.T.)
      end if


      You might also need it in the OnFetch event if you allow fetching.
      Peter
      AlphaBase Solutions, LLC

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


      Comment


      • #4
        Re: don't allow to edit the data in the past

        Hi Peter,

        Thank you for your quick response and your sample code

        Thank you very much
        Peter-th

        Comment


        • #5
          Re: don't allow to edit the data in the past

          Hi Peter,

          I have to define t variable and what kind of it ?

          Thanks
          Peter-th

          Comment


          • #6
            Re: don't allow to edit the data in the past

            Any variable that references a table like

            t =table.current()

            is a pointer (dot) variable.

            Dim t as P

            is proper but not necessary. The assignment statement implicitly defines it.

            Using the pointer variable you can reference the fields in the table like

            t.fieldname using an actual fieldname
            There can be only one.

            Comment


            • #7
              Re: don't allow to edit the data in the past

              Hi Stan,

              Thank you for your more details for the pointer variable.
              I have never used it before and I have to learn it more how to use it
              I think it's time to use it many places in my application

              Thank you for advise
              Peter-th

              Comment


              • #8
                Re: don't allow to edit the data in the past

                Hi Peter,

                Thank you for your sample I can do it now.
                Is it possible if I use more condition to allow user edit the data
                I use the save botton and add more command after save record to set the status of some field to t/f (to protect user change clock in PC)

                I have more a field for status in the table

                id date expense status
                001 3/3/2010 500 T
                002 4/3/2010 620 F

                when user key in the data within form and click Save botton then I have a command (next command to save record) to set the Status field to T

                so when user click save botton. He will cannot edit the data evenif he try to change clock of PC.

                The problem is I don't know what command I can use and add more in the Save botton to force the Status to T

                Thank you for your commandation.

                Peter-th

                Comment


                • #9
                  Re: don't allow to edit the data in the past

                  Originally posted by peterth View Post
                  The problem is I don't know what command I can use and add more in the Save botton to force the Status to T
                  Maybe in the CanSave event you put something like:

                  FieldObjectName.value = .T.

                  The CanSave fires before the Save event. It might work in the save event too, but I forget. Yow will need to put the field on your form, but you can hide it. Usually, Alpha automatically gives the field object the same name as the field itself.
                  Peter
                  AlphaBase Solutions, LLC

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


                  Comment


                  • #10
                    Re: don't allow to edit the data in the past

                    Thank you for your advise. I will try it again.

                    Thank you ver much.
                    Peter-th

                    Comment

                    Working...
                    X