I am implementing some Domino served Web Based Applications that functioned quite normally under R5 but now that they are being served by R6 are having ‘difficulties’.
I’ve tried every search string I can think of and have posted a couple of questions but got no response. Is ANYONE ELSE out there experiencing any similar issues?
If yes, what problems have you encountered and what resolved them? So far I have script class change issues (Date/Time Hours) and differences in application appearance.
Subject: RE: Please provide details of any date/time related changes you have encountered.
Well, there’s this one that I reported ages back…
quote
I’m passing a LocalDateTime to the LSGMTTime function (ie LocalDateLime.LSGMTTime), which of course takes the local time zone into account.
Now, it works for almost any time I care to use - except one. 10am. This drove me crazy for ages, until I figured out that it was related to my time zone being GMT +10 (ZE10).
I looked at what was happening in the debugger, and if the time passed to the LSGMTTime function causes the GMT time to be exactly 00:00:00 the function doesn’t return a time component at all. Normally, you will get back something like (10/10/2002 02:00:00), with a DateOnly component of “10/10/2002” and a TimeOnly component of “02:00:00”
BUT!
If the GMT time ends up as 00:00:00 then what you get returned is (10/10/2002) with a DateOnly component of “10/10/2002” and a TimeOnly component of “”
This, as you might imagine, causes severe problems…
Subject: RE: Please provide details of any date/time related changes you have encountered.
That is not a change in Domino 6. It is a traditional peculiarity of Notes.It has nothing to do with LSGMTTime or zones. When you display a date/time value, the default conversion to a String removes the time if it is exactly 00:00:00. Cstr(Cdat(23456)) reproduces it. If you use Format to specify the conversion, it does not happen. Alternatively, add a centisecond when the time is zero: Cstr(Cdat(23456 + 1/8640000))
By the way, DateOnly and TimeOnly are not “components”. They are also String conversions. TimeOnly does format the time as “00:00:00” when I try it.
Subject: RE: Please provide details of any date/time related changes you have encountered.
Thanks for the explanation Rod - at least now I know what causes it and can account for it. BTW - I used the term ‘component’ possibly a little loosely - I was just referring to the parts of the whole, rather than to any specific usage.
I went with the “Add a second” route (we didn’t need that level of accuracy for this application.)
Subject: Problems with R6 web served apps (that were fine with R5)
Your “nav pane” problems are easily rectified by using outlines or just about any other “designed” navigation solution. You appear to be relying on the default navigator, and yes, it’s appearance may have changed. I don’t know – I would never have used it. The default display for views qua views is on a default view template sans navigation, save for Prev-Next-Expand-Collapse-Search.
Haven’t run across behavioural changes with NotesDateTime, except that one can create an array of them to populate a field in ND6+ (something R5 would choke on). Exactly what are you referring to?
I’m not relying on anything - as I said I’m implementing. I’m sorry that the developers of the application I am implementing did not have such exacting standards as yourself.
I’ve been told by the same developers that “Domino R6 treats the hours portion of a LotusScript Date-Time variable a little differently to R5”
I was merely looking for input from people who had experienced issues; what those issues were and any associated solution so that I could move my role to a more proactive and less reactive one.
Well, if you didn’t build it, it’s not your fault. Feel free to let your developers have it, though ;o). If they chose not to control the appearance of the application, then they can’t really claim innocence when the appearance of default elements change.
As for the date/time thing, I think you’re being had. The LotusScript Date/Time variable (not a class) is a Variant containing a floating-point number whose integer portion (everything to the left of the decimal point) is the number of days since the “epoch date” for LotusScript (December 30, 1899), and whose fraction represents the time expressed as a part of a day. The hour is just the fraction multiplied by 24, taking the integer. I haven’t had to touch anything written in R5 to make it work on ND6.