Helen wrote:

>Normally, no. But I suspect this thread might be concerned with the problem that happened with compound indexes in v.2.5.1, that was >corrected in 2.5.2. If you had a database with compound indexes that was created or restored to 2.5.1 you need to do either a full restore or at >least a rebuild of compound indexes in 2.5.2. Created or restored under 2.5.0 or prior, no problem.

>AFAIK, the only way you can determine that is by checking the creation date with gstat -h and knowing the FB version that was running at the time.

Uh, oh, I had just assumed that 2.5.2 would have an updated ODS version number.

If you fail to do the rebuild, and you run into the bug, what actually happens? Do you get some kind of error message that can be recognised by my software, and added to to tell the end user what to do to fix it?