1. Possible bug. The GradientFormHeader in a maintenance form keeps forgetting the value of it's Title property. I've worked around it for now by setting the property manually in the Load event.
You have something else going on here. This control is used everywhere, so I know that it is not a bug. The problem you are having is that the form designer is not properly serializing that property...which can stem from a number of different things. To prove this, drop the same control on another form and see if the title sticks. You can then start working from there.
2. I'm using a Browse Dialog and one of my search fields is a boolean field. I can enter "true" or "false" (without the quotes) and it works find. If I make a mistake, e.g. I enter "fals", I get an exception error screen and the little searching progress window stays visible. How would you avoid this type of user input error on a boolean search field?
This is ultimately an integer value. What we generally do is use a Enum Value that may read "Yes" or "No". When you setup a search field, you can specify an enum value to use for selection. On the BrowseDialog property sheet, you will also see a property for the EnumTopMostValue text. You can set this property so that you can still excluded this field from the search if you so desire.
3. When defining the seach fields for a Browse Dialog, what is Enum Type used for? It's not mentioned in the help topic "Using the Browse Dialog", which seems a bit out of date.
See previous answer.
4. After successfully adding a new record in a maintenance form, the new record is appended to the end of the data held by the business object. How do I get it sorted into the correct position?
I don't know what you mean by "Correct Position" but you have control over this by setting the Sort proeprty of a business object. If you want to sort your BO, the just set the property and all new or existing records will follow suit.
5. The StrataFrame help file I have doesn't seem to have an index. Is this correct? An index would be a big help, as would more detail on all the various classes and their members. A big task I know, but its very frustrating to look up class members and only find short descriptions. Better than nothing, but could definitely be better. A product with the class of StrataFrame should have documentation to match.
There is an index, but it depends on how the file is opened. We are already aware of this and it will be resolved soon.
6. Finally, how is v1.5 for DevExpress 6.2 progressing? I'm very keen to get this update as soon as possible.
This is why we give you the source code so you do not have to wait on use to update all versions of the DevExpress updates. In fact, there are some posts on this forum where some of our users have already moved forward to 6.2. Regardless, this will more than likely be released with 1.5.