>>Both Dragan's and Naoto's suggestions work. But I have to change the approach. I will create a separate field for the Time. The customer is using SFQUERY and it fails if I change the type of field from D to T. Not a big deal; it was a nice attempt though.
>
>The probable reason why it fails is that it uses some kind of data dictionary, where it says it's a date field. You'd need to refresh the record in the dictionary to make it work. Which may be more trouble than it's worth, as the same record may be used elsewhere, so you'd start a chain reaction for which you don't have the (date)time.
You are probably right that changing something almost always catches up with "you" later. Which happened to me yesterday. I changed the field from D to T and only this morning found that this new type (T) does not work with the SFQUERY. By adding a separate field, I am pretty much assured that the old bugs will remain the old bugs :) So far, adding a new field seems to work. At least the new added field works only in those reports and feature where I want it to work. So, it is easier to test for possible bugs.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
