1. The MDDeployMain populated the SQL Server combo on the wrong thread
   

   In most environments, the cross-thread exception would not be thrown, however, the MDDeployDialog has been updated to ensure that the combo is populated on the UI thread versus on a background thread to ensure a cross-thread violation does not occur.

2. DDT Database Import Wizard not including indexes
   
   This was the same issue as the tables in a previous fix.  This was accidentally introduced when schemas were added as part of the criteria on the import.  This issue has now been resolved.

1. BrowseDialog may throw error if no search fields are visible
   

   If a BrowseDialog has no search fields visible an error may be thrown when trying to set the control positions since there are no controls to position.  A test has been added to prevent the error from being thrown if no search fields are visible.

2. SyntaxEditor now has PauseSyntaxColorization and ResumeSyntaxColorization methods
   
   The ability to prevent the syntax editor from colorizing altogether and then restart the colorization process has now been added through these two methods.

3. SyntaxEditor now supports RichTextToolstrip and can act as an RTF editor
   
   The SyntaxEditor can now be used to both colorize syntax while acting as a full fledged RTF control including support for the RichTextToolstrip control.  In order to act as a standard RTF control, the PreventStandardRTFTextFormatting property must be set to False.

4. SyntaxEditor control now has a PreventStandardRTFTextFormatting property
   
   A property called PreventStandardRTFTextFormatting has been added to the SyntaxEditor which will allow the formatting of the text through standard RTF properties such as the SelectionFont, etc.  By default, the SyntaxEditor control will strip this type of formatting to ensure that the editor font is consistent.

5. RichTextToolstrip now allows individual buttons to be shown or hidden
   
   The RTF toolstrip now supports the ability to individually show or hide certain action items within the toolstrip.  For example, the bold button can be hidden or prevent the end-user from changing the font, etc.

6. Issue with the CurrentRowIndex being incorrectly position after a table refill
   
   When a Fill method was called, the CurrentRowIndex was incorrectly position on the second record (if one existed) instead of the first.  This was actually introduced at the end of April 2008 during the 1.6.6 beta as a result of fixing another bug.  The _CurrentRowIndex is actually a property and not a private which takes into account Shared DataTable access.  A fix was previously introduced (in April) to prevent the _CurrentRowIndex from being an illegal value when the BO actually had records within it which caused other issues in regards to a Save or Undo in certain conditions.   The bottom line is that both issues are now correctly fixed.

*(There are several other minor fixes in this build as well)

DOWNLOAD THE OFFICIAL 1.6.6 RELEASE IN THE MY ACCOUNT AREA.