A family of Microsoft relational database management systems designed for ease of use.
It's not clear whether your ObsTime values include a date, and are formatted as hh:nn, or whether they are the 'time value' only. If the former I'd suggest the following amendment to Scott's code:
strSQL = "INSERT INTO tablename (ObsTime, ImageNumber, field3, etc.) " & _
"VALUES(#" & Format(DateAdd("n",1,Me.ObsTime),"yyyy-mm-dd hh:nn") &_
"#, " & Me.ImageNumber+1 & ", " & _
Me.control3, etc. & ");"
As written the code would fail in the UK and elsewhere not using the US short date format. Formatting the value to the ISO standard for date/time notation internationalizes the code.
If the latter, then you should understand that there is in reality no such thing in Access as a 'time value' only a date/time value; it is really the time on 30 December 1899, which is 'day zero' in Access's implementation of the date/time data type. So the code would then be:
strSQL = "INSERT INTO tablename (ObsTime, ImageNumber, field3, etc.) " & _
"VALUES(#" & Format(DateAdd("n",1,Me.ObsTime),"hh:nn") &_
"#, " & Me.ImageNumber+1 & ", " & _
Me.control3, etc. & ");"
I have one question, however. What happens when the time reaches 23:59? In scenario 1 above, where the values include a date, then the value would increment to midnight, 00:00, at the start of the following day; in scenario 2, where the values are 'time values' they would revert to 00:00 at the start of 1899-12-30.