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

Automatically inserting date

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

  • Automatically inserting date

    I have an A5V5 database of videotapes in which I would have available the date of the LAST time the form was opened, so I have a reference of when the tape was last used. Ideally, the date should insert as the form is being closed so that the next time it is opened, it will have the previous date, and so on and so on.

    Perplexed beyond my abilities. thanks for the help. mv

  • #2
    Re: Automatically inserting date

    Originally posted by mikev View Post
    I have an A5V5 database of videotapes in which I would have available the date of the LAST time the form was opened, so I have a reference of when the tape was last used. Ideally, the date should insert as the form is being closed so that the next time it is opened, it will have the previous date, and so on and so on.

    Perplexed beyond my abilities. thanks for the help. mv
    Database Design Forum for questions about general database design. Specific questions related to Alpha Five should be placed in the appropriate Alpha Five forum
    To answer your question, anyway, what you are probably wanting is that when a record is edited/changed the date is recorded. This is generally done through the onchange for a form field. In your case the syntax would be something like

    datefieldobjectname.value = date()

    where datefieldobjectname is the object name of the date field you want changed as it appears on your form. This is usually the same as the table field it represents but can be different. You will find the actual object name by examining the field's properties.

    I say, "what you probably want" because I can't understand why you would want to change the date if a record was merely viewed, not changed. You probably don't mean "date of the LAST time the form was opened" because at that point you don't even know what record is being displayed.
    There can be only one.

    Comment


    • #3
      Re: Automatically inserting date

      Thanks Stan. The reason I want to change the date, even if the form has not been changed is because, while the foprm wasn't changed, teh videotape whish is repreesnted by the record was used for a purpose, and I want to know the last time the tape was used. I'll try to work through your idea.

      Comment


      • #4
        Re: Automatically inserting date

        You need to put some xbasic in one of the form's events, perhaps the CanExit event:

        parentform.commit()
        tbl=table.current()
        tbl.change_begin()
        tbl.date = Date()
        tbl.change_end(.T.)
        END
        Peter
        AlphaBase Solutions, LLC

        Peter@AlphaBaseSolutions.com
        https://www.alphabasesolutions.com


        Comment


        • #5
          Re: Automatically inserting date

          Originally posted by mikev View Post
          Thanks Stan. The reason I want to change the date, even if the form has not been changed is because, while the foprm wasn't changed, teh videotape whish is repreesnted by the record was used for a purpose, and I want to know the last time the tape was used. I'll try to work through your idea.
          Still doesn't make sense to me. I think you are using the terms form and record interchangeably when they are not.

          What must be happening is that you are in some part of your application, you search for and display the desired record in the form of which you are speaking. At that point, no matter what action is taken, you want to update a date field in the visible record to the current date. I would suggest you use the code supplied for the onexit event for this form rather than the previously suggested onchange event for a field on the form.

          This should do what you want if the form is not used for any other purpose.
          There can be only one.

          Comment


          • #6
            Re: Automatically inserting date

            Thanks. You are right. I am using the terms form and record interchangeably, when they are not. I'm out till the new year but will try your latest idea when I get back. Happy holidays! mv.

            Comment


            • #7
              Re: Automatically inserting date

              Originally posted by Peter.Greulich View Post
              You need to put some xbasic in one of the form's events, perhaps the CanExit event:

              parentform.commit()
              tbl=table.current()
              tbl.change_begin()
              tbl.date = Date()
              tbl.change_end(.T.)
              END
              This works for me thanks. One small thing. I had to eliminate the line of code
              tbl.date = Date() because it also changed the date on the record as well as the field date last accessed. thanks for your help. mv

              Comment


              • #8
                Re: Automatically inserting date

                along the same lines but a bit different. One app I have has the user(logged in) and on change/add it takes the username, datetime and the account number of the record and stores it in another table I call log.dbf. More information(such as amounts and other field changes could also be stored) could be added to the log.

                It is easy to set up this one.

                Dave
                Dave Mason
                dave@aldadesktop.com
                Skype is dave.mason46

                Comment

                Working...
                X