Only just realised that IBM has gone through the full trouble in order to not only provide us with an easy way to push location, but also Eclipse preference settings to the client via policy.
While I wouldn’t necessary pronounce that it was worth the wait, while applying the workaround in Lotus Notes and Domino 6 to 8, it’s definitely a feature that has been waited for a long time.
Guess this is widely published on the web but since I was searching for this like mad today I have to write it down for the next time I need it.
In order to enable the Eclipse update manager UI in Lotus Notes:
You can now find the Eclipse update manager under File > Application > Application Management.
Is anyone of you aware whether or not IBM is planning to support the set-up of Lotus Notes 8.5.x in a pure Windows 2008 Terminal Services environment (without making use of Citrix)?
IBM’s technote is stating quite clearly that it only supporting installations on Citrix. I am well aware that the installation is still possible; however, I would be far more confident to implement it on a large scale with a clear support statement from IBM.
IBM recently updated/published a technote Can you disable the Recent Contacts feature using a policy? explaining that this is currently being investigated. While it is true that there currently is no user interface component to disable that feature using a policy you could combine the information published in technote 1267115 and technote 1196837 to still achieve the same.
In adding a new field $PrefDisableDPABProcessing to the desktop setting and populating it with the value of “1″ you effectively disable the recent contact features for all clients whose policy is enforing the desktop setting with the added field. Please follow above technotes for more details.
Today was head scratching day again. Lotus Notes 8 was raising an error message that sounds so unusual for a Lotusscript developer:
Type mismatch in method CoerStrToNum: STRING found, double expected.
The only change to the environment has been the upgrade from Notes 7 to version 8. As it turns out, there are also a few notes about this message on Google, including a rather dubvious technote from IBM.
As it turns out, the source of the issue can be found in these two lines of code.
myDate$="17/01/2008 7:17"
var=CDat(myDate$)
Interstingly enough is the error message new to version 8 of Lotus Notes, obviously raised itself by the underlaying C++/Java code. All previous code streams, including the 8 debugger are raising the familar “type mismatch” error. This might create the impression that a regression bug has been introduced in Notes 8 – which is completely false.
Anyhow, who would have expected that the whole issue has been caused by a wrong regional setting on the underlaying operating system? In this case it has been set to US (American), with a date format of mm/dd/yyyy. As there isn’t a 17th month in a year the code fails.
I guess I would leave it open for discussion whether this has been an oversight by the developer, who couldn’t imagine that his/her code would ever been run in different region or a mistake by the persons setting up the laptop to not configure the (for New Zealand) proper date format dd/mm/yyyy.
