Please help, removing date from a timestamp to only show military time

[mcmcd99]

I have a timestamp on my records that is called [tstime] and it is set to the format for 24 hours,
but when I go to edit it from a subform it shows "11/8/2017 6:39:06 PM" that format, and they have to erase all of
it to enter 19:20 or whatever time it is (in military time)

How do I have it store only the military time? It shows only the military time, but when I go to edit it.. all that extra makes it so hard to edit quickly.

[Minty]

You'll still have to store it as a datetime value.
On the form have you tried setting a format on the display control, and using an input mask?

[orange]

Here's a sample using your data, but as Minty said, you should store the date/time field.
You get the time using timevalue and then format it---For presentation

x=#11/8/2017 6:39:06 PM#
?format(timevalue(x),"hh:nn:ss")
18:39:06

Good luck.

[ssanfu]

As I asked in your earlier post:

Why are you editing a timestamp field? A timestamp is (usually) for knowing when a record is created/modified - nothing more.

[mcmcd99]

I am creating air traffic logs for a small general aviation airfield, and I have the traffic timestamped. But there is an edit subform so that if an incorrect entry is entered, they can go back and change it. And sometimes entries are timestamped *here and now* but are really older entries. I just wanted to get rid of the fluff for ease of use by people who aren't as tech savvy as myself. Which is pretty much everyone here lol.

[ssanfu]

Hmmmm....
Maybe I don't understand what you mean by "timestamped". In a past job life, we had paper log books, that eventually migrated to computer based logs. The paper logs had numbered pages and were filled out in ink, because they were legal documents. (used to assign blame ) You couldn't tear out pages or erase entries - could be fired if you did. Entries into the computer log were time stamped and had an audit log for adds & changes. There was the abilits to edit an entry for 24 hrs, then the entry was locked. But everything was recorded in an audit log (table). No way, no time, no how was a timestamped field allowed to be edited.

I would think that the FAA would also frown upon editing a "timestamp" field.

But, again, maybe I misunderstand what you mean by "timestamped".

[mcmcd99]

We have to enter a lot of old data, and we can't timestamp them "here and now" we have to input them with specific times and dates according to their paper written times. And this isn't a big airport. We don't have air traffic control here, or even a tower. This is a small general aviation airfield. The logs are only for the simplification of keeping track of how many aircraft land, what the field usage is, and basic transmission info that can help us provide a better service. So when I say they can edit timestamps, it's not like some big FAA regulated airport, you know? It's so we can count how many aircraft landed, what the busy times were, etc.

[orange]

mcmcd99,

What exactly is the current status of this project?

What is the report or output data that will be used by whomever? Do you have a sample?

You have paper records currently. What is the consistent data you have that can be entered into your proposed system/database?

Does your current paper data go under some review/edit/validate before data entry into the new system?

[June7]

I set the Date/Time field format property to Short Time and display is only the 24-hr time, no date part. Had no problem entering 19:20.

Make sure textbox Format property has Short Time setting.

Might want to disable the textbox date picker.