>TCL – Limiting commands by user


>

Revelation are gearing up for the release of 9.1.1 shortly and part of this upgrade will be a request made at the recent EMEA RUG meeting in London.

Changes have been made to TCL in the new version. These enhancements will enable developers to limit certain commands so that they can not be run by a particular user. For example, you will be able to expose TCL to your users and at the same time you could restrict access to the CLEARFILE command.

This neat change to TCL will enable users to make better use of TCL, without the application author having to worry about the integrity of the system being compromised in any way.

Advertisements

>Revelation User’s Conference 2010


>

Revelation Software is pleased to announce that our keynote speaker for our 2010 Conference is THOMAS J WILSON, president and CEO of Unisphere Media which publishes DATABASE TRENDS AND APPLICATIONS. Tom’s keynote presentation is titled “Ten Trends Shaping Information Management in 2010”.

Our 2010 Users’ Conference will be held at the Rio All-Suite Hotel and Casino in Las Vegas, Nevada on Tuesday, April 27th – Friday, April 30th, 2010.

Please drop me a line if you would like more details about this main Revelation event.

>Hardening OI Directory File permissions


>

Several of you have recently asked for details about ‘Hardening File permissions on the OpenInsight Directory’. I am pleased to announce the publication of a comprehensive knowledge base article that details this topic.

Locking down file level permissions on the OpenInsight directory is an important step to ensuring the stability of your application. Improper permissions can allow users to change or delete files – accidentally or intentionally. The ‘Hardening File permissions on the OpenInsight Directory’ Knowledge Base article provides guidelines to secure your OpenInsight directory.

Examples of securing the application at the share level and file level are provided within the article. Each example begins with the creation of the destination directory followed by installing OpenInsight into the newly created location. Establishing the destination directory permissions before installation ensures that the administrator installing the application will have rights to modify it later.

>RSS feeds on www.revelation.com


>

The US web site has maintained a number of RSS feeds for sometime, but they have been largely under utilised. This was primarily owing to a login being required to retrieve the feed and, as many RSS readers do not support authentication, this resulted in the feeds being somewhat difficult to access through people’s preferred RSS reader.

Earlier this year, Jared took a look at this issue and he has made changes to the feeds so that they can now be retrieved without the need to login, although a login is still required to view the message content.

At the present time there are feeds for ‘News and Information’, the ‘Online Discussion Forum’ and the ‘OpenInsight WORKS Discussion forum’.

Please also remember to include the RSS feeds for this blog’s posts and comments.

>Troubleshooting REAUTH.EXE & NETDRV.EXE


>

As many people cross-grade existing ARev and OpenInsight systems to version 9.x and deploy new systems on the new version, we have had a few support questions posted with regards to using the REAUTH.EXE file and also NETDRV.EXE.

Both of these files require single user access to key OpenInsight files and, in addition, the renaming or installation of a new OENGINE.DLL file also requires single user access.

Key files can remain locked when a user leaves OpenInsight open on a workstation, and this results in error messages when the above files are utilised. Furthermore, if errors occur but everyone is out of the system, the issue can usually be traced to a hung engine that is still running in memory.

Revelation US have written a very useful article that covers some common steps and includes a utility to resolve the issue of locked files. Please click here to access the article.

From the desk of Bill Caisley


There are a few instances reported that if utilising ARev tables in OI ‘I have to maintain my indexes in ARev, OI does not work!’

If you are using/attaching legacy tables from ARev in OI and there is a Quickdex.mfs on the DICT. you are unable to create a Btree on any of the fields. It will appear to have worked but the index will not exist and it will not work. If you attempt to re-add the index you will receive a message that the ‘index already exists’. What has happened is that the DICT. now has a one (1) in field six which indicates the existence of a Btree on that field.

Revelation are going to produce a meaningful error message in a future release to warn you of this problem.

To successfully maintain indexes from OI you must first remove the Quickdex.mfs from the DICT. by means of a SET_MFS. You should also edit the row in the Dict and remove the one (1) in field 6 if you previously attempted to create an index.

Please also note that Sprezzatura have begun a blog thread regarding ‘Indexing in OpenInsight – Part 1 –What is indexing?