1. New Popup class allows any control to appear as a drop down
   

   A new class called Popup is now available which allows any control to appear as a drop down in association with an owner control.  For example, a button can be turned into a drop down style control in a single line of code!  Simply create a Popup class and pass over the control that will be shown within the drop down.  Then simply call the Show method and supply the appropriate parameters.  It is that simple!

2. DDT Import Wizard may skip certain stored procedures and UDFs
   
   To improve performance, the DDT would exit when enumerating stored procedures and UDFs when the first system object was found as system objects to not need to be imported.  However, under certain, very rare circumstances, legitimate sprocs or UDFs may appear within the collection AFTER the system objects.  This is highly unusual, but so as not to have this issue creep up again in the future and since the import is a process in which a developer does not live (as this is generally only done once per database) the lengthier process will be implemented.

3. SyntaxEditor now supports Ctrl+Z undo
   
   With the release of the 1.6.6 SyntaxEditor, the Undo logic of the underlying RTF control was no longer functioning.  A custom Undo implementation has been implemented to overwrite this functionality.

4. PackageIt registry updates changed to look at HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE
   
   To ensure that there are no permission issues on saving dialog locations, etc. the PackageIt application has been updated to use the HKEY_CURRENT_USER.

5. Some changes have been made to the install to attempt to prevent VFP and core C++ DLL conflicts
   
   Under certain OS environments and depending upon Visual FoxPro installations, certain files were attempting to be written to disk and overwritten in other cases.  The installation has been changed in an attempt to prevent this from happening.  Specifically the VFPOLEDB and VFP8 DLLs as well as the MSCVR70.DLL required by VFP8.

6. IPControl no long supported.
   
   The IPControl has been removed from the control collection as this was a very lightly used (if ever) control which did not follow our standards any longer.  Use a MaskedTextBox instead when this need arises.

7. SF Textbox would render prefix characters (i.e. ampersand) incorrectly when enabled
   
   The SF Textbox performs custom rendering when disabled which uses the TextRenderer class.  However, a format flag of Noprefix was not specified which would render the character after an ampersand, for example, like a label with an underscore.  This issue has been resolved and teh NoPrefix tag has been added to the format flags to properly render the text.

8. ThemedDetailWindow item now has a ValueMaxWidth property
   
   The ThemedDetailWindow items now have a ValueMaxWidth property which is taken into account when aligning the value right.  This allows the width of the column to be specified so that the ThemedDetailWindow can be wider than the value text will need to render.  This is especially helpful when showing items such as currency.

9. The ListView BeforeChildFormExecuted event now supports a cancellation action
   
   The ListView BeforeChildFormExecuted event now has a CancelAction parm on the event argument which allows several options.  None, which would continue as normal, cancel the ChildFormDialog execution only, or cancel the dialog execution and undo any data changes related to the currently executed action (i.e. if adding a new record the new record would not be added).  This gives the best of all worlds in regards to the potential needs to cancelling an automated ChildFormDialog execution.

10. Changed the binding on BusinessLayer to the BoundControls to determine if the specific binding exists for the bound property rather than testing on Count > 0.
    
    A control can now properly be bound to more than 1 property.  1 property through StrataFrame BusinessLayer binding and additional bindings through native .NET binding.

11. If a right-click was executed within the BO Mapper without a TreeView object being selected, an error would occur
    
    If a right-click was executed within the BO Mapper on the TreeView list, an error (NullReferenceException) would occur if an object was not selected.  This issue has been resolved.

12. DDT Import Wizard now allows a unique index with an entity column to be imported as a unique index instead of a primary
    
    Under certain conditions, an index was being brought in through the import wizard as primary when it should have just been imported as Unique.  An import option was added to treat unique indexes with entity columns as primary.  This can be unchecked to prevent this from occuring resolving the issue in most cases.

1. The Change Password dialog of the Role Based Security was not respecting localization.
   

   The Role-Based Security change password dialog title was always appearing in English.  The appropriate key has been applied and this issue has been resolved.

2. Security password change dialog did not show all broken rules simulating a form that would not close
   
   The most common broken rule that was not being displayed when changing a password was password complexity.  When a user was forced to change their password and did not meet all of the requirements of the password, the form would not always show the broken rules for the password field when OK was clicked.  This issue has been resolved.

3. Security password dialog no longer allows access to Cancel button when being forced to change
   
   If an end-user logged in and was forced to change their password the "Change Password" dialog would show a cancel button.  However, when the cancel button was clicked the form would close and immediately reopen.  The cancel button is no longer accessible when the end-user is being forced to change their password preventing any confusion.

4. SQL Server 2008 is now fully supported
   
   SQL Server 2008 is now fully supported from the design-time environment all the way through to the DDT deployment.

5. Connection Manager now supports 2008 authentication.
   
   When using the connection manager authentication would fail when trying to connect to a 2008 SQL Server.  This was due to SMO 9.0 attempting to talk to 2008 which requires SMO 10.0.  To prevent this type of thing from happening in the future and to prevent any SQL assemblies being added to projects when an SF UI control is dropped into a non-SF application.

6. Inherited business objects that use the same base business object and share the same property descriptor dictionary can now have properties of the same name.
   
   In previous versions, a base business object A that defines the property descriptor dictionary (in the .designer.* file) would not allow more than one descriptor to be added for a given name.  Subclass B and subclass C, both inheriting from A could not define a property with the same name or at runtime, the first instance of B or C instantiated in the system would define the property descriptor for only its class.  The property descriptor dictionary now allows more than 1 field descriptor per field name and uses the ComponentType to determine the inheritence branch of the property descriptors in order to return the correct descriptor when the property name is supplied.

7. Role Based Security - Error within the user editor if old permissions deleted
   
   In the cycle of development , it is possible that some keys may be deleted or removed altogether.  If the permissions are removed and a link record still exists between a user and a permission that doesn't exist, an error would occur when going into the user editor.  This issue has been resolved.

ES Notice: For those developers using the Enterprise Server, attached here is the ES site contents that contains all files necessary to update your ES server sites.  This is an easier mechanism to update than using ther ES install, especially if you already have the site up and running.  Just replace your site contents with these files and the restart IIS and you will be good to go.

1. Changed enterprise server to account for UTC time when passing parameters to commands.
   

   This is a breaking change.  The server and client must both be upgraded or this change will break communication between the ES and the clients.
   
   Before this change, the ES would not consider UTC time when passing parameters on commands, but would use UTC to return the results of a query back to the client (through .NET's serialization of the data table).  Now, UTC is taken into account when passing parameters.
   
   If the CustomDataSerializer is used, UTC is not considered when passing parameters or when returning results back to the client.

2. ListView column sorting would not work when swapping between dates and strings
   
   When a ListView contained columns that were dates and strings, the ListViewColumnSorter would not sort the columns properly for each type.  If the first column (default sort column) was a date, then the sorter tried to sort all columns as dates.  If the default sort column was a string, then all columns attempted to sort as a string.  This issue has been resolved.

3. New Database Deployment Toolkit deployment package merge type added
   
   A fourth merge type has been added to the data deployment package which will skip any data deployment for that item if the destination table already contains records.

4. Database Deployment Toolkit IDE has been tweaked for better UI interaction
   
   The DDT UI now shows the stored procedures sub-categories within the treeview making it easier to locate and work with sprocs in a particular category.  Additionally, at times, when a new table was added or a sproc was saved, for example, the item would not be properly selected within the list or treeview.  These types of issues have been resolved.

5. Database Deployment Toolkit now supports search and find functionality within the IDE
   
   The Database Deployment Toolkit now supports the ability to search through all elements of the profile and includes searching within T-SQL body content, names, and descriptions.  Making it extremely easy to locate code and sprocs within large profiles.  Also, once within the search results list, the item can be modified directy from within that list.

1. Business object enumerator had a memory leak under certain conditions.
   

   The BusinessLayer enumerator had a memory leak under certain conditions.  This was noticed predominately in the web business binding source.  This issue has been resolved.

2. MicroFour StrataFrame Inherited UI (DevExpress) has been updated to 8.2.8
   
   The templates as well as the MicroFour StrataFrame Inherited UI (DevExpress) has been updated to 8.2.8.

3. Other minor bug fixes to be detailed at a later date.

* Log in to the My Account area to gain access to the updates.

1. BrowseDialog now supports the ability to override the underlying query table (or view)
   

   Two new properties have been added to the BrowseDialog that add a phenominal amount of flexibility.  You can now set the OverrideSearchTableName and OverrideSearchTableSchema.  This allows a view to be used in place of an underlying table associated with a BO making it possible to search across multiple tables.  The BrowseDialog has always been limited to searching on a single table.  With this feature, a view can be supplied as an override and fields that do not belong to the table in which the BO represents can be searched.  See the update on the overridable field data type on the search fields also.

2. BrowseDialog search fields now allow the field data type to be overwritten.
   
   There is now an additional tab when modifying a search field on a Browse Dialog.  The Data Type tab allows the field data type to be overwritten instead of being pulled from the business object.  This is especially helpful and necessary when using a view as an overridable search table on the browse dialog and the field being added will be part of the view but is not part of the mapped BO.  This allows any field to be specified and the field data type provided so that it can be searched on just as if it existed within the BO mapping of the business object.

3. All security dialogs now save any settings in HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE
   
   The RBS security dialogs now only reference HKEY_CURRENT_USER in the registry versus HKEY_LOCAL_MACHINE which will prevent any types of errors from occuring for restricted users.

4. Danish Keys Updated
   
   The pre-localized Danish keys have been updated.

5. Other minor changes and bug fixes to be noted at a later date.

* Log in to the My Account area to gain access to the updates.

1. The unique index type for CONSTRAINT versus INDEX was not being respected
   

   This would not be an issue in most situations.  However, if there were two tables with the same index name and both indexes were set as unique and the index was not the primary index, this error would crop up.  The issue is that when SQL Server uses the CREATE INDEX versus the ADD CONSTRAINT command, multiple unique indexes with the same name (while not being the primary key) can be created.  This issue has been resolved.

2. Business object now has a IsCheckingRules property
   
   An IsCheckingRules property has been added to the BO that is True only when the rules are being checked for the BO.  This is useful in scenarios where logic may be added to the Navigating event, for exmaple, and you do not want to execute that code when checking rules.

3. Database deployment toolkit not properly updating the date and time of an object history item
   
   This would not cause an issue with deployment or a package.  However, when a new object history item was created the object history date and time was not being properly updated.  This issue has been resolved.

4. The TabOrderController would not advance when AutoComplete mode is turned on and the EnterAdvances was not set
   
   This actually happens to be an issue with how .NET raises events.  The OnKeyDown was not called on controls that support AutoComplete when the AutoCompleteMode was set to a value other than None.  This issue has been resolved.

5. SqlTransaction connection to reader being closed when not using SPROCS
   
   An error could occur when using transactions and CRUD settings or SPROCS were not being used for inserts and updates.  This issue was accidentally introduced in a recent build when making a change to improve performance and resolving another issue in regards to a memory leak.  This issue has been resolved.

6. Collation can now be added to a database within the DDT
   
   The collation can now be set for a database within the DDT.  This is a plain text field that can be copied from SQL Server and then pasted into this location.  If the specified collation cannot be found, the default collation for the database will be used.

* Log in to the My Account area to gain access to the updates.