Sprezzatura have released an upgrade to their free Basic+ Source Code Publisher that I featured in my 30th March blog posting. If you are publishing Basic+ source code to the Revelation forum or your own blog, then I’d strongly recommend Carl’s utility – click here for further details.
Today saw the long awaited I18N (Internationalisation) meeting in Ealing. Revelation UK staff and Mike Ruane, over from the US, were joined by a handful of key developers from Europe involved and interested in better support for I18N within OpenInsight.
Following the usual introductions during which attendees highlighted their needs for I18N within OpenInsight, Mike touched on the position of OpenInsight when he took over the product and then the main I18N enhancements that Revelation have built into the product since version 4.1.3, through the 7.x series and into the recent enhancements in 9.x.
The day then followed a round table discussion format during which various topics were openly discussed. The idea was for Mike and Carl, to fully understand what our International clients need for enhanced I18N support in OpenInsight version 9.2, 10.0 and later.
Some of the topics discussed included; better support for UTF8 and possible future support for UTF16, collation sequences, LH4 to handle full UTF8 data, caching and performance implications following the necessary changes.
Collation sequences became a major topic of discussion and Mike showed how version 9.x can use Windows Collation. Attendees were invited to submit examples of their collation sequences to Mike.
Following a lengthy discussion, most of which was beyond my comprehension, the general consensus was that Revelation are almost there already, but that the proposed changes will address most of the things that our International clients need and that the enhancements should open up more doors and opportunities for us all.
I’ll not go as far as indicating what Revelation’s plans are following the meeting as it is too early and Mike has much to think about. However, the meeting generated five key areas to consider for 9.2 and certainly leaves the development team with a more clearly defined idea of what is needed for far better support for I18N in OpenInsight 9.2 and later.
Personally, I would like to thank Kerry Walter, Alexander Holliday, Stefano Cavaglieri, Neville Jones and Gary St Denis for taking time to meet with us and to contribute to this large and complex topic.
Well it is now official, I am a ‘Twit’terer!
I’ve had a Twitter account for a while, but never really got into the whole idea of using it in a business context – personally, I can think of nothing worse than spending a hour a day finding out what your contacts had for breakfast this morning, plan to do in their private time this evening or any of the other ‘twatter’ the service appears to generate.
In addition, finding time to maintain the blog, a couple of networking sites and Twitter was resulting in late evenings and an unwanted distraction.
However, I’ve had a slight change of thought recently and I’ve now begun adding Twitter’s ‘Tweet’ button to my blog postings and I have also begun to use Twitter for short information blasts with a Revelation topic. If you have a Twitter account, you can easily use the Tweet button to tweet the posting onwards to your followers. In addition, you can follow me (log into Twitter and search for mdp_revsoft) and receive small bite sized timely twitter postings about Revelation related topics – I won’t over burden you and I’ll be keeping my tweets on topic. In addition, my tweets will NOT be linked to or appearing on the blog, keeping the blog clean.
I’ll still be maintaining the blog as the main vehicle for technical information, news and other information coming from my desk. So please be sure to follow and/or subscribe to the blog.
Revelation have recently announced the release of a patch to OpenInsight 9.0 and 9.1 to correct errors with Quickdexes and Rightdexes whereby duplicate keys are returned. If you’re in the WORKS program you can get the update here.
However, if you are not a WORKS member please contact your local Revelation representative for further details about obtaining this patch.
Version 9.1 of OpenInsight has seen some fairly major changes with regards to .NET support, the new OIPI.NET print engine and more. However, these enhancements have found it necessary to include a separate client install, as detailed within the OpenInsight installation and upgrade instructions. Special attention must be made to these documents when installing (or upgrading) OpenInsight to ensure a smooth upgrade and installation process.
An unforeseen scenario has come up a couple of times recently for people upgrading to version 9.x. Whilst this will be documented for 9.2, I thought it best to blog the issue here for anyone working with 9.x versions prior to the 9.2 release.
Although the upgrade instructions are being followed, the activation code is not being accepted and OpenInsight presents the user with an error reading ‘Invalid authorization code entered. Please re-enter’.
This is a generic error message that is presented whenever the authorisation code fails to register on the system. This could be due to the code being typed incorrectly, an additional (usually trailing) space being included during a copy and paste and if the code has already expired. In addition, this error is produced if the installer does not have sufficient rights to create the temporary file that is required for the upgrade.
During a review of this issue by Bill Caisley, he found that the error was occurring before you navigate to the OpenInsight directory where you wish to apply the upgrade. During the installation the setup routine creates a temporary file with information necessary to validate and update the engine with unique license information, etc. Further investigation proved that, even though he was logged as a member of the administrator group, a rights (permission) issue meant that the temporary file could not be created and the installation failed with the resulting error message.
Rather than running the SETUP.EXE file over the network from the OpenInsight directory on the server itself, the resolution was to simply move the SETUP.EXE file onto the C:drive on the server and run it from there as he had full permissions to do so. It could just as easily have been moved to his workstation so long as the installer has sufficient permissions to complete the installation (create the temporary file).
If something goes wrong with any of your OpenInsight installations, please check for sufficient permissions as a first port of call. Insufficient permissions is becoming a likely cause of failure for installations and upgrades on some of the later operating systems.