I e-mailed revelation asking them where to send bug reports and they said to the online discussion. I would have thought they'd have an e-mail address for bug reporting but I guess not. Anyway, here is a list of bugs in OpenInsight that I have found:

1. I have a form that allows a person to select data for btree searches. The data is displayed on a pop-up. The user performed the search which returned about 10000 records. By mistake (or for fun) he attempted to select all records. An error was displayed as follows:

  Unrecoverable OpenEngine Error

  String space format error has been detected

The computer had to be re-booted before OpenInsight would run again. I think some checking should be done for buffer overflows or however the keys get read. I don't think the OpenEngine should die like that.

2. Attempting to send two events in row to the same window in a stored procedure will kill OpenInsight. I would have thought that events would have been queued but it's OK that they aren't. However an error message should result of some sort. It took me a while to find out what was going on since once again I had to re-boot my computer to run OpenInsight again.

3. When creating a table, try this:

- type in the name of a column

- without hitting return move the mouse to the calculated columns area and type in a new column name. There is now way to get out of the calculated columns area after that.

Attempting to send two events in row to the same window in a stored procedure will kill OpenInsight.

I do this all the time

UnUsed=Send_Event( WindowName, PSEVENT_WRITE$ )

UnUsed=Send_Event( WindowName, PSEVENT_CLEAR$ )

or various things like that and I've never had a problem.

I only ask, since perhaps this is something else and we can fix it.

It might do this if you end up in a recursive situation. Sooner or later, and usually sooner, the engine will bomb.

akaplan@sprezzatura.com

Sprezzatura, Inc.

View this thread on the forum...