StrataFrame Forum / Updates and Information / Posted Releases

StrataFrame 1.6.7 Beta Installation

Trent L. Taylor — Mon, 06 Oct 2008 11:18:27 GMT

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!
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.

StrataFrame 1.6.6 Beta Installation

Trent L. Taylor — Wed, 16 Apr 2008 10:45:13 GMT

This is the first installment of the 1.6.6 beta update. You will notice that the version will display as 1.6.5.1 when looking in the StrataFrame->Version window. This will make it easier for us to determine if you are running a beta version or a fully released version.

There are quite a few changes in this build and there will be many more to come before the release. However, there have bee some requests out there that are in this build which include the business object field orders to the specifications of the ConnectionDataFolder (ability to specify the folder location for the Appkeys.dat and the Connections.dat files).

There are also many new enhancements to the DDT which includes pre and post script executions, field struction default prefixes (makes it easier when creating new columns), and more.

Here is a list of what is in this update:

AddPreSaveBusinessObject and RemovePreSaveBusinessObject methods added to BusinessLayer
In the instance that the need arises where the order of the business objects save needs to be set, the AddPreSaveBusinessObject method can be used. This allows business objects to be dependent upon other business objects and rely on the primary/foreign key relationhships that are established.
ListView now supports UI data interaction including related business objects, child form dialog, and
related command or toolstrip buttons.

The ListView has been dramatically expanded to have native logic for tasks that are common recoded. There are now many new properties (detailed below) and events that allow a more dynamic child display interaction with much less code. By simply setting the UI interaction properties of the ListView, the ListView will dynamically manage the toolstrip buttons (or any other type of control) for the Add, Edit, and Delete as well as any security keys that may also be associated with those objects. Additionally, a ChildFormDialog can be attached to the ListView which will then by dynamically shown to the end-user on an Add or Edit dynamically with no additional code. Finally, the ListView will now allow the instance of the business object of which it represents to be attached and the current index (or row position) of the business object to be dynamically updated.
New Properties:
AddObject
AddObjectSecurityKey
EditObject
EditObjectSecurityKey
DeleteObject
DeleteObjectSecurityKey
DeleteMessageKey
AutoNavigateToSelectedRecord
HandleAddAction
HandleDeleteAction
HandleEditAction
New Events:
ChildFormResults
Wizard control default colors modified when using a Windows based color theme on Vista

Some of the colors pulled from the OS when using a Windows based theme looked a little dark when running on a Vista OS. This issue has been corrected.
BusinessLayer now has an UndoByFilter method

In the circumstance that you are dealing with a grandchild many-to-many environment and you need to undo the changes for the grandchild without effecting the other records that have been modified on that same grandchild business object, you can use the UndoByFilter method. This allows a business object to undo only those records that meet the criteria of the filter. If a filter is already applied on the business object it will be ignored and left intact once the Undo operation has been completed.
BrokenRule constructors made public

The BrokenRule constructors have been made public instead of internal (friend) allowing a new broken rule to be created through an external assembly.
Embedded localization languages file not always located.

A change has been made within the framework regarding how the Message_Languages.xml file is located in an embedded environment. This file was previously not always located unless stored externally.
RenderAsSolidBackground property added to a WizardPage

A wizard page now supports the RenderAsSolidBackground property like the other themed container controls.
New SyntaxEditor control now replaces the ColorizedTextbox

A new control has been created that allows a legitimate syntax editing environment exist. This control replaces the ColorizedTextbox which was never really designed for editing but viewing and had many limitations as it relates to text size and performance. The SyntaxEditor is designed to allow for much larger text environments while maintaining the keyword colorizations dynamically. (Note: There will be a number of additional features added to this control prior to the 1.6.6 release).
New SyntaxEditorLineNumbers control which shows line numbers for a SyntaxEditor control.

This control can be used in conjunction with the SyntaxEditor control and displays the line numbers currently visible within the SyntaxEditor.
Database Deployment Toolkit SQL editors revamped to use the new SyntaxEditor controls

When dealing with the SQL code for a stored procedure, view, or user-defined function, it was difficult to actually use the text area as an editor, especially on larger queries and commands. The DDT has been updated to use the new SyntaxEditor controls so that it is much easier to work with this data within the editors.
DDT code windows now remember their previous sizes and positions

The code windows within the DDT (stored procedures, views, and user-defined functions) now remember their positions and sizes from the previous entry.
CustomPattern added to the Regex options for a Keyword within the SyntaxEditor

The SyntaxEditor already had 3 pattern types that included MatchBetween, MatchTextToEOL, and MatchExact that came across from the ColorizedTextbox control. However, a new option has been added called CustomPattern which allows literally any Regex expression to be supplied allowing the syntax coloring to support any complicated or intricate colorizations.
AccessDataSourceItem would not automatically return the primary key value

When inserting a new record and the PrimarykeyIsAutoIncrementing property was set to True on the BO, the saved primary key value would not be returned for an AccessDataSourceItem. This issue has now been resolved.
GetTypeFromReferencedAssemblies method changed to ignore loader exceptions

Under certain conditions when the referenced assemblies were being reflected, an assembly reference that was not needed in one environment may be hit, though it is not used, and throw an exception since that assembly could not be found in the GAC or on the machine. This change will prevent that error.
Database Deployment Toolkit now supports category for stored procedures

When dealing with a large database and many stored procedures, it can become difficult to locate a single sproc in the list. A category can now be assigned to a sproc so that like sprocs can be grouped together making it easier to locate a specific sproc.
BrowseDialog now has a ReturnSelectedRecordOnly property

When the ReturnSelectedRecordOnly property is set to True, the selected record within the browse results will be the only record copied into the BusinessObjectToPopulate when returned from the BrowseDialog.
BuildDataTableFromEnum improperly created a top most value for the value type

When using a combo box or manually calling teh BuildDataTableFromEnum method in the MicroFour.StrataFrame.Tools.Common shared class and a top most value was supplied, the value type that was set as the top most value was, at times, coming in as a string or invalid type. This would result in an ArgumentException (though it may be snuffed) which in turn could result in a very slow UI response to any other other that is bound to the same data source. To resolve this issue, the TopMostValue is attempted to be parsed as an integer. If so, it is then added to the value as an enum type of that value, even if the enum in question doesn't actually have that value. This results in much faster performance and resolves the ArgumentExceptions.
Database Deployment Toolkit now has a default prefix option for each table

A default prefix can now be supplied for each table which will auto-populate any new field created with this value making it easier to create new structures. For example, if a prefix of "pre_" were supplied then a new field, when created, would automatically appear as "pre_" with the caret position after the "_" ready for the rest of the field name to be supplied.
Pre and Post deployment scripts now available within the Database Deployment Toolkit

A new feature has been added to the Database Deployment Toolkit which allows scripts to be created and executed before and after a profile is deployed to a server. This allows any strange or out of the ordinary deployment actions to be taken. For example, if the need existed to convert DateTime fields to a BigInt on a pre-existing database, and still maintain the data within the fields, a Pre-Deployment script could be created to convert the DateTime fields to BigInt (ticks would be stored) fields prior to the database updating the structures which would circumvent data loss and/or an error.
ConnectionManager now allows the data folder that stores the connection files to be specified

A new property has been added to the ConnectionManager class called ConnectionDataFolder. By setting the ConnectionDataFolder prior to calling the SetConnections() method, the folder location to which the AppKeys.dat and Connections.dat will be stored can be specified. This allows environments with extremely tight security restrictions to supply the folder when the common application data folder has been restricted from general use.
New Solution Preference added to determine if field names will appear in alphabetical or natural order.

With the release of 1.6.5 a change was made to the display of bindable business object fields to appear in alphabetical order. However, there were some developers who preferred to view their field names in a natural order. A new preference was added to the Solution Preferences so that this can be specified on a per solution basis and developers of both preference types can view the fields in their desired order.

Note: For those developers who have a license, you can get the source code for this build in the My Account are of the website.

DevExpress Wrapper for 8.1.1

Trent L. Taylor — Wed, 26 Mar 2008 10:58:56 GMT

For trial users and developers having issues recompiling the MicroFour StrataFrame Inherited UI assembly, attached is the assembly and XML for the DevExpress build version of 8.1.1.

Copy these files to the c:\Program Files\Common Files\MicroFour\StrataFrame folder.

Be sure to also drag the DLL into the GAC (C:\Windows\Assembly). Once done, go back into Visual Studio and this assembly will then support the 8.1.1 version of DevExpress.

Note: We will post the source code with the next update in the My Account area. DevExpress changed some of their event arguments and base classes is why some of you were having an issue recompiling.

Fix for Message_Languages.xml file not being located when embedded

Trent L. Taylor — Wed, 26 Mar 2008 10:40:57 GMT

Under certain conditions, the embedded Message_Languages.xml file may not be located. This issue has been resolved in this fix. Copy the DLL and XML file to the C:\Program FIles\Common Files\MicroFour\StrataFrame folder and drag the DLL into the GAC (C:\Windows\Assembly) then go back into VS or run the application in question.

Fix for DbEngine when deploying SPROCS for non-dbo schemas

Trent L. Taylor — Fri, 21 Mar 2008 13:10:28 GMT

In the 1.6.5 build, we changed the DDT to use extended properties on the database, stored procedures, views,and UDFs so that in environments where there may be a DBA they can add their own without being removed the next time the meta-data was deployed. In doing so, we accidentally introduced a bug related to those extended properties. So now, when a schema other than DBO was being used, the DDT did not "see" the extended properties and thus did not remove them prior to attempting to re-deploy them which resulted in an error. This issue has been resolved with this assembly. Extract the attached ZIP and do the following:

Close the DDT and Visual Studio
Copy the DLL and XML both to the c:\program files\common files\microfour\strataframe folder
Drag the DLL into the GAC (c:\windows\assembly)
Go back into Visual Studio and/or the DDT and redeploy your package. The error should be resolved.

DevExpress Wrapper for 7.3.8

Trent L. Taylor — Wed, 19 Mar 2008 10:44:18 GMT

For trial users and developers having issues recompiling the MicroFour StrataFrame Inherited UI assembly, attached is the assembly and XML for the DevExpress build version of 7.3.8.

Copy these files to the c:\Program Files\Common Files\MicroFour\StrataFrame folder.

Be sure to also drag the DLL into the GAC (C:\Windows\Assembly). Once done, go back into Visual Studio and this assembly will then support the 7.3.8 version of DevExpress.

StrataFrame 1.6.5 Maintenance Release

Trent L. Taylor — Wed, 12 Mar 2008 14:54:44 GMT

The update posted in the My Account area only resolves the two following issues:

Properly installing the StrataFrame Add-In for Visual Studio 2008 on a 64-bit Operating System
Resolves an issue with installing a package file to a SQL Server 2000 instance. There was a new feature added that allows new functions, views, and stored procedures to be added outside of the DDT and not be deleted. However, there was a minor bug on the extended property being set on a SQL Server 2000 instance.

That pretty much covers it :)

StrataFrame 1.6.5 - Web Application Template Update

Trent L. Taylor — Fri, 07 Mar 2008 10:07:00 GMT

The 1.6.5 release had a fix to include the global.asax file within the template, however, a corrupt ZIP file prevented the global.asax file from being included for both the VB.NET and C# Web Application project templates. These corrected templates will be included in the next install build, however, to manually update these templates extract the attachment to this post to a temporary location. Once extracted, copy the CSharp project template to:

[codesnippet]C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplates\CSharp\StrataFrame[/codesnippet]

and overwrite the existing template (SF_WebApplicationProject.zip). Next, copy the VB.NET template to the following location:

[codesnippet]C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplates\VisualBasic\StrataFrame[/codesnippet]

and overwrite the existing template (SF_WebApplicationProject.zip). Once this is done, exit Visual Studio and run the following command:

[codesnippet]"c:\program files\Microsoft Visual Studio 9.0\Common7\ide\devenv.exe" /setup[/codesnippet]

The project templates should now be updated and ready to go.

StrataFrame 1.6.5 Beta Installation

Trent L. Taylor — Mon, 07 Jan 2008 17:15:52 GMT

This installation is a beta but will install to both VS2005 and VS2008. There are some samples that have not yet been included and this install does not yet have all of the enhancements and bug fixes that will be included in the final build. However, this is a stable build as we have been using it for quite some time.

This is a great way to get going on 2008 easily for those developers who are moving forward. Also, the StrataFrame menu now has a new option...Version. :) We are planning on leaving the assembly version at 1.6.0.0 so that your projects do not have to be changed and this installation can be implemented easily; however, the assemblies each have a 1.6.5.0 file version which is how we will determine exactly which version you are on. You can get a listing of your assemblies and your current version by clicking the StrataFrame -> Version menu item within Visual Studio.

If you run into anything related to the installation or interaction with VS 2008, please let us know via the forum. If you do not yet see that one bug fix or enhancement that you have been waiting for...please do not post those items as we still have a long list that we are working through to include in the final build. Thanks!

One final note, this build does include updated DevExpress assemblies to 7.3.5 for those trial users who do not have source code yet.

Manual Visual Studio 2008 Update Instructions

Trent L. Taylor — Mon, 03 Dec 2007 09:57:55 GMT

We will be releasing a new update very soon that will do this for you automatically. However, for those of you who REALLY want to up and running on VS2008 right now without having to wait a couple of weeks, here are the instructions as well as the assemblies that are required in order for you to be fully running on 2008.

Manually Adding VS2008 Support

First, to get the StrataFrame menu to appear in 2008, you will have to copy over the StrataFrame.AddIn and change the version within it:

[codesnippet]C:\Documents and Settings\MyUser\Application Data\Microsoft\MSEnvShared\AddIns\StrataFrame.AddIn[/codesnippet]

[codesnippet]C:\Documents and Settings\tltaylor\Application Data\Microsoft\MSEnvShared\AddIns\StrataFrame2008.AddIn[/codesnippet]

Once this is done, open the 2008 AddIn that you just copied over and change the two version entries to 9.0.

Close the file, close Visual Studio 2008, go back in and you will see the StrataFrame menu. However, all of the templates will not be installed. To get the templates installed, you must copy them over from the 2005 folders:

Visual Studio 2005 Folders
[codesnippet]C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ItemTemplates\CSharp
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ItemTemplates\VisualBasic
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ItemTemplates\Web\VisualBasic
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ItemTemplates\Web\CSharp
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ProjectTemplates\CSharp\StrataFrame
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ProjectTemplates\VisualBasic\StrataFrame[/codesnippet]

Copy all of the templates that begin with SF to the 2008 folders of the same names in the Microsoft Visual Studio 9.0 folders.

Visual Studio 2008 Folders
[codesnippet]C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplates\CSharp
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplates\VisualBasic
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplates\Web\CSharp
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplates\Web\VisualBasic
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplates\CSharp\StrataFrame
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplates\VisualBasic\StrataFrame[/codesnippet]

Once they are copied over to the 2008 folders, execute this command (be sure VS2008 is closed):

[codesnippet]C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe /setup[/codesnippet]

Updating Assemblies
Be sure to download the assemblies attached to this post so that all of the StrataFrame type editors will work properly. You will also find the enhancements from previous posts in this forum section in these assemblies as well. Once these assemblies are downloaded, do the following:

Exit Visual Studio
Add the assemblies to the GAC (C:\Windows\assembly) folder.
Copy the assemblies to the C:\Program Files\Common Files\MicroFour\StrataFrame folder
Go back into Visual Studio

At this point you should be up and running.

StrataFrame 1.6.1 Maintenance Release

Ben Chase — Mon, 19 Nov 2007 10:38:37 GMT

This update contains a more detailed message when the GetBusinessObject() method fails to find the business object on the ApplicationBasePage.

StrataFrame 1.6.1 Maintenance Release

Ben Chase — Thu, 15 Nov 2007 08:50:57 GMT

This update contains the fix to the OracleDataSourceItem for the improper parameter name for primary key parameters passed to update stored procedures.

StrataFrame 1.6.1 Maintenance Release

Trent L. Taylor — Mon, 12 Nov 2007 18:11:45 GMT

This maintenance release includes the previous maintenance releases up to this point (minus the Enterprise Server assemblies and enhancements). This was added after the last BrowseDialog update to provide additional functionality and to resolve an issue when dealing with a top most item (<Not Used> item). The bug existing when a combos return type was any data type other than integer. A new tab has been added to the search field item editor which allows the top most text and value to be specified on a per item basis. Also, the BrowseDialog is now testing differently so that it can more accurately determine if the top most item has been selected avoiding any issues with a field being selected as part of the search criteria when it hasn't.

StrataFrame 1.6.1 Maintenance Release

Trent L. Taylor — Sat, 10 Nov 2007 21:00:41 GMT

The changes in this maintenance release obviously includes any previous changes as well as the changes to the BrowseDialog as posted below.

BrowseDialog Changes

A unique key has been added to the search item which allows multiple fields of the same name to be properly stored in the registry when the forms settings are saved avoiding a bug upon re-entry of the browse dialog.
A DateTime field now properly displays the short date pattern based on the loaded culture information for the logged in Windows user.
The search field now has an additional page tab titled "Date" which allows a Time Action to be specified which allows the time to either be left alone, set to the start of the day, or set to the end of the day. This allows accurate searches to be performed on DateTime fields without the end-user having to account for this by moving to a previous day or a day after which could, in certain conditions, return invalid records.
AdvancedOptionsInitiallyShown property has been added to the BrowseDialog control which, as the name points out, allows the advanced options of the browse dialog to be initially shown without requiring the end-user to click the Advanced Options check box.
The RowBackColor and RowForeColor properties are now respected within the RowPopulating event which allows a specific color to be assigned to a row. Note that if the ViewAsLedgerCard property is set, the RowBackColor property will be ignored.

StrataFrame 1.6.1 Maintenance Release

Trent L. Taylor — Wed, 07 Nov 2007 10:25:31 GMT

This update includes all of the assemblies except the Enterprise assemblies and is a culmination of all updates thus far. This post was added in response to a change prompted by post #12525 where the BrowseDialog was ignore the RowBackColor and RowForeColor properties.

This change will now respect the RowBackColor and RowForeColor properties of the RowPopulating event of the BrowseDialog. Note that if the ViewAsLedgerCard property is set, the back color will be overwritten and the specified value will be ignored.

StrataFrame 1.6.1 Maintenance Release

Ben Chase — Tue, 06 Nov 2007 09:22:58 GMT

This release contains the fix for problems when updating records through the OracleDataSourceItem when the table has a compound primary key.

StrataFrame 1.6.1 Maintenance Release (Database Deployment Toolkit)

Ben Chase — Mon, 05 Nov 2007 10:52:25 GMT

This update contains the DDT files that match the last posted 1.6.1 StrataFrame core DLLs.

StrataFrame 1.6.1 Maintenance Release

Ben Chase — Tue, 30 Oct 2007 09:07:32 GMT

This update contains a change to the IsValidInterfaceType() method to consider Wireless80211 interfaces to be valid.

Install instructions: http://forum.strataframe.net/FindPost12264.aspx

StrataFrame Update Instructions

Ben Chase — Tue, 30 Oct 2007 09:03:44 GMT

To install an update found within this forum:

1) Download the attached *.zip file from the attachments section of the post.

2) Extract the contents of the *.zip file to a temporary location.

3) Drag all of the files to the C:\Program Files\Common Files\MicroFour\StrataFrame folder (C:\Program Files (x86)\Common Files\MicroFour\StrataFrame for 64-bit Windows machines).

4) Drag the *.dll files to the C:\Windows\assembly folder (the GAC).

5) Restart all instances of Visual Studio.

StrataFrame 1.6.1 Maintenance Release

Ben Chase — Tue, 30 Oct 2007 08:44:47 GMT

This release contains the fix for extra 'End If's being added to field properties for VB.NET business objects.

Install instructions: http://forum.strataframe.net/FindPost12264.aspx

StrataFrame Setup - Version 1.6.1 - July 7, 2007 - 11:30 AM

Trent L. Taylor — Sat, 07 Jul 2007 11:34:24 GMT

The post added on July 7, 2007 was posted to correct a problem with the StrataFrame add-ins. When opening a project an error would occur that would cause Visual Studio to crash. This issue can be resolved by moved the attached assemblies on this post into the GAC (C:\windows\assembly) or by downloading and installing this build. That is the only difference with this published install versus the original published installation.

StrataFrame Setup - Version 1.6 - February 21, 1:30 PM

Trent L. Taylor — Wed, 21 Feb 2007 13:32:40 GMT

When running the Role-Based security for French, German, Italian, or Russian, an error would occur indicating that the localization key "SFSTText - New" could not be located. This was due to the embedded localization files not being udpated for these languages.

The setup posted on this date resolves only this issue.

StrataFrame Setup - Version 1.6 - February 19, 5:00 PM

Trent L. Taylor — Mon, 19 Feb 2007 17:08:21 GMT

The StrataFrame Application Setup posted on Monday, February 19, 2007 at 5:00 PM fixes the FileNotFound exception when installing StrataFrame. This error occurred when attempting to install the StrataFrame databases within certain scenarios related to the GAC.

If you are experiencing issues getting the databases installed, please download the latest version and this should resolve your issue.

StrataFrame Setup - Version 1.6 - February 16, 1:10 PM

Trent L. Taylor — Fri, 16 Feb 2007 13:26:20 GMT

The setup posted at this time resolves some minor installation issues that were encountered with the initial 1.6 setup. Below is a list of potential errors that may have been encountered. If you see any symptoms within the list below, then it is recommended that you download the latest setup and re-install StrataFrame.

64-Bit Operating Systems Platforms
Standard Windows Error with the Send or Don't Send buttons appeared
Have the Database Deployment Toolkit (BO Mapper Option is disabled)
Received an error while deploying data to the SQL Server database