For some time now I have had a huge problem with my Windows 7 x64 installation. Almost making day-to-day work with Windows unbearable!!
For some reason Windows looses focus every 3-5 seconds, making for example drag and drop almost impossible. When I say “loose focus” it is not like “loosing focus completely”, like deactivating the current application. The currently active application is not loosing its application focus. It is more like the mouse is loosing it’s “hold”. The symptomes are typical that the mouse “releases” by itself during drag and drop, and this cause for example:
Read on to see how I found the culprit and regained control in Windows!
I love Wordles (for a free online generator see http://www.wordle.net/). Sometimes a word-cloud can say a lot about the content. For example, below you see a wordle for all Lotusphere (errh, Connect, errrh ConnectED) session abstracts combined from 2000 up to 2014:
Click on all images for a larger version!
Below you will find wordles for each year from 2000 to 2014. Fun to see how company name changes, and how the focus slighty changes from year to year. The wordles has been created by extracting the abstracts from all the session-databases I have archived, using the cool tool named Wordaizer.
Before diving into the wordles themselves, I thank Ben Langhinrichs from Genii Software which assembled all the abstracts into an easy-to-use Notes database for over a decade! You might even get the old session databases from the links I provide at the end of the article.
I also thank Mat Newman and more, which has taken over the last two years and created the session databases for 2013 and 2014.
Why are the session databases important?
For some reason IBM has created their own Session Preview Tool, which allows you to find sessions and their abstracts. Right now it looks like this:
I find the interface above un-intuitive and hard to use. Yes, you can get a list, but I can’t tweak it the way I want! Perhaps I am just too old…
I have allways liked the Notes-version much better – you know what you get when you have it in a Notes database!!
Long live Notes!
Click Read more below to see the wordles year by year!
This part 1 of 3 in the article series “Classic Notes: How to communicate with IBM Connections from LotusScript wrapping IBM SBT with LS2J”.
Read the others here:
… embark! …
- Ooops, but I am mostly doing LotusScript, you say … what now?
Perhaps you ask a question on StackOverflow to see if anybody has some advice for your scenario (just completely out of the sky – perhaps something similar to this question ). The chances are that you’d get a lot of advice abandoning your old and tired LotusScript in favor for the much more modern Java language. Your challenge is that you have a lot of LotusScript code that you would love to enhance with the new cool IBM SBT possibilities, and perhaps not the time to take the heavy plunge into learning a new language.
This article – which assumes a whole bunch of details are in place – will show you how to have this small piece of LotusScript code …
… put an entry into an Activity Stream in a specified community like this;
If you have seen error messages like “30061 - Error: Relational database BLABLA not found., Connector 'db2', Method -Connect- (-30061) - Relational database BLABLA not found.” or “Error: Communication error occurred on distributed database processing. See SQ30080 for invalid possibilities. A common error is that the password is case sensitive and is not being provided in the correct case” you’re not alone!
Read on how to see the bigger picture on how IBM i’s “Relational Database Directory Entries” should be configured based on what you see in the real target database. Finally you’ll see how to code Lotus Connectors LSX (LCLSX) to use this information to connect to the database.
Most of our Domino servers run on IBM i (aka System i, iSeries and AS/400). Since IBM i have DB2 natively supported, there is no need to install DB2 Client or DB2 Data Server Drivers (more on those below). The target DB/2 server is running on a remote Windows server, and I thought it would be a breeze to connect IBM i and the Windows machine together. Not so! First and foremost, there is sparse information on the net on how to exactly do this. You very quickly find sample code similar to this;
So how come the code above bails out at the Connect-method?