Join 83 other subscribers
Thought-Provoking Commentary for the Lawson Software Community
If you haven’t discovered Ken Hamady, you need to check out his recent post on troubleshooting “duplicate records”. This is perhaps the most frustrating issue that report designers encounter when developing reports against Lawson tables.
The economy is on practically everyone’s mind these days. We know we’re in for a bumpy ride over the next several months, and perhaps even years. Everywhere we turn, organizations are “battening down the hatches”, learning to do more with less. One way to do that is to evaluate our tools as well as our approaches to some of the routine tasks that we perform.
First Hyperion gets acquired by Oracle (see http://www.oracle.com/hyperion/index.html).
Now more big news this week: http://www.businessobjects.com/news/press_release.asp?id=20071007_005046. The question I’m getting from a lot of you in the Lawson community is: “Where does this leave Lawson?”. And, of course, the answer is, “well, of course, I don’t know”. But I have my opinions/ideas. Read more of this post
Some thoughts as we start 2004:
I recently got a chance to see a pre-release version of Microsoft’s SQL Server 2000 Reporting Services, That’s a pretty long name, which is probably why it was formerly known as "Rosetta". I call it the "Crystal Killer".
For several years, I’ve consulted for a CIO who’s "tagline" is "The right information for the right person at the right time".
That phrase came to mind as I watched one of the most compelling product demos at CUE: Smart Notification. You may have seen the demo or heard about this technology, which Lawson acquired from Keyola (http://www.lawson.com/news/0417keyola.html) just days before CUE 2002.