Dennis, I will keep this in mind.
My plan is for this form to be a touch screen for each time parts are added. So it will be a simple touch and the same info will stay on the screen. I will use this either as assemblies are made or pallets filled. They would just change the number of pieces if needed for the nest entry on the same job. When they go to the next job, the information will change. The only editing to be done will be in another table that will not necessarily have this same field. James Belisle Making Information Systems People Friendly Since 1990 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dennis McGrath Sent: Wednesday, February 26, 2014 1:18 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: date time You could redfine that variable definition so that the column will only be updated in ENTER mode. DateTimeCol = (IFEQ(.RBTI_FORM_MODE,'ENTER', .#NOW, DateTimeCol)) BUT, if someone goes back to a row and modified it while still in 'ENTER' mode the timestamp would change. That, in fact might be exactly what you want. Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: Wednesday, February 26, 2014 1:05 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: date time Dennis, Would that be true if the editing takes place in the table? I do not think so! How about a separate form that would not equate the field with the variable #NOW? James Belisle Making Information Systems People Friendly Since 1990 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dennis McGrath Sent: Wednesday, February 26, 2014 12:59 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: date time James, If anyone goes back and edits the data, the timestamp will be updated. If that is what you want you are golden. Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: Wednesday, February 26, 2014 12:54 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: date time Karen, Sometimes the old fashioned way works better. Now I got what I want. Thanks for the tip. James Belisle Making Information Systems People Friendly Since 1990 From: [email protected] [mailto:[email protected]] On Behalf Of Karen Tellef Sent: Wednesday, February 26, 2014 12:38 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: date time Or you can do it the old fashioned way and define a form variable: DateTimeCol = .#NOW This will only update if the row has been modified or inserted Karen -----Original Message----- From: Albert Berry <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Wed, Feb 26, 2014 12:23 pm Subject: [RBASE-L] - RE: date time All right, let us put the two different pieces in one post. It might help clarify things. So that the user sees the time on the form, place the LED or analog clock on the form. It will click off the seconds, but won't do anything for the database entry. You need to use .#NOW when you insert the row as part of the data string when you post the row to the table. This is in the button eep that you use to save the row. Albert
