For simplicity sake, I would do as Jimmy suggest and use two fields, with the hidden calculated field.
The fields themselves could be regular text or numerals, since you will have to validate them if they change anyways.
EX:
2 Fields: HoursTB, MinutesTB
Both are default set to 0
Both have at least this data validation: This Field (HoursTB or MinutesTB) is not equal to 0 AND This Field (HoursTB or MinutesTB) does not match pattern Custom Pattern: 0 (See below)
How to get the pattern:
-
From the drop down, select Custom Pattern
-
In the Custom pattern field, clear the field
-
Type in the Custom pattern field: \d+
-
Hit the OK button
Add your screen tip to say something along the lines of "This field can only be a number"
What does this one data validation do?
It makes sure of two things: First, your field will always be a number and Second, it will always be a number.
From here you can do like Jimmy suggested and convert this into a decimal hour to figure out what you need.