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

System date field

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

    System date field

    Hi. I'm using a simple form for name and address and want to input the system date at the beginning of each record. I do not want that field to change once it's entered. In other words, if I go back to review records the next day, I want the date to remain for the day the record was entered. I used "date" for the type of field and used "Calculated" field type in the field rules. Also used DATE() for the calculated field expression in field rules. The form still changes the date of previously entered records to the system date. And one more thing, the date does not display at all in the default browse mode. Just upgraded to Windows XP. Can anyone help? Thanks.

    #2
    RE: System date field

    "Also used DATE() for the calculated field expression in field rules." - not a calculated field, a user entered field, with the simple default expression - date().
    There can be only one.

    Comment


      #3
      RE: System date field

      Hi Stan - I started out with exactly what you suggest. It didn't work properly. It inserts the system date correctly, but allows the date to change every time the record is inserted. I found the tip about using the calcualted field for date on one of the old forum postings, but that doesn't seem to work either. Thanks. Karen

      Comment


        #4
        RE: System date field

        in field rules, do as Stan suggested, and also set the skip to .t. - this way a user cannot change the date.
        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


          #5
          RE: System date field

          Hello Stan. I have implemented your suggestion (had already tried this, by the way). It still doesn't work correctly. Puts the system date in but changes the system date every time the record is accessed. It does prevent me from entering anything into the date field, however. I think I mentioned we have just upgraded computers to Windows XP. I have to believe this caused the problem because my date field always worked perfectly before. Any suggestions for XP? Thanks for your help. Karen

          Comment


            #6
            RE: System date field

            Karen,

            The recommended approach to using A4V4.5 with XP is it to configure it (in Windows) to run in Windows 2000 compatibility mode.

            I suggest you verify that the field is no longer defined as a calculated field in field rules for the table. It should be "user entered". Then specify date() as the default value on the data entry tab of the field rules dialog. The default value is supplied to new records only. Will have zero effect on edits to an existing record. This is simply a long winded way of telling you what Stan said in fewer words.

            -- tom

            Comment


              #7
              RE: System date field

              Good morning Tom and Stan. Thank you so much, both of you. That did the trick - it was a compatibility issue I guess. Everything is working fine now. Thanks again, Karen

              Comment


                #8
                Re: System date field

                Originally posted by Tom Cone Jr View Post
                Karen,

                The recommended approach to using A4V4.5 with XP is it to configure it (in Windows) to run in Windows 2000 compatibility mode.

                I suggest you verify that the field is no longer defined as a calculated field in field rules for the table. It should be "user entered". Then specify date() as the default value on the data entry tab of the field rules dialog. The default value is supplied to new records only. Will have zero effect on edits to an existing record. This is simply a long winded way of telling you what Stan said in fewer words.

                -- tom
                Tom: John Linley here...
                I discovered the truth of this when I tried to write an automatic system->date
                entry for an existing record. It did not work of course...
                How then, can I do the following?

                In an inventory table, I recently added two fields, an "adj qty" field and
                an "adj date" field. Now when a new value is entered into the "adj qty" field,
                of an existing record and it performs the mathematical adjustements correctly,
                I could have the user manually enter the "adj date". However, I would like it to be an automatic entry field when the adj qty field is entered. There is no need to ever change the adj qty field for the same record.
                Kindest regards,
                John

                Comment

                Working...
                X