Sometimes you'll need to convert the number you're comparing to so it's also text (which you can do with prec(x,y) but normally there's no issue.
Was the wrong way around. You need to convert the text part back to a number in your comparison - which you can do with roundTo(x,y) or several other methods.
The easier way though is to put the time into a text attribute then nothing needs to be converted.
That aside, why is the number too big? Are you tracking time down to the milliseconds? If you're tracking time, padding each number to two digits, YEAR..MONTH..DAY..HOUR..SECOND should fit quite happily in a table as an integer. It's only if you tack on milliseconds that problems arise.
3absh
Member Posts: 601
Comments
Store them in text fields.
problem is i need to use them in functions
for example if current time in seconds > tblValue 1,1
Can text do that?
Sometimes you'll need to convert the number you're comparing to so it's also text (which you can do with prec(x,y) but normally there's no issue.
Was the wrong way around. You need to convert the text part back to a number in your comparison - which you can do with roundTo(x,y) or several other methods.
The easier way though is to put the time into a text attribute then nothing needs to be converted.
That aside, why is the number too big? Are you tracking time down to the milliseconds? If you're tracking time, padding each number to two digits, YEAR..MONTH..DAY..HOUR..SECOND should fit quite happily in a table as an integer. It's only if you tack on milliseconds that problems arise.
I found the best solution for me is to use a second count for the current day only instead of something similar to Unix time.
I don't require a Unix timestamp.. Thanks for your help.