MUST Version 8.1 Build 001 : Release Date 1st November 2010
---------------------------------------------------------------

MUST Revisions
----------------
None

MUST+SQL Revisions
--------------------
1. Revision to remove ; from subqueries
2. Query dependency chart is now exported to excel rather than printed
3. Build scripts improved to better handle creating parameters table schema
4. Support for translating ASC function to ASCII function added
5. Bug fixed when translating String() to Replicate(). Parameters on access function are now swapped over
6. format function changed adding formats 'mm/dd/yyyy' and 'yyyy-mm-dd'


MUST+Web Revisions
---------------------
1. Support for unbound controls
2. Support for VS2010 and Ajax Control Toolkit
3. Ajax Calendar control now used
4. Ajax Tab Control now used
5. Where possible images such as logos are exported to .net
6. Support for Command Buttons Added



========================================================================================================================
MUST VERSION 8.0 CHANGES
========================================================================================================================

1. File filtering when selecting databases changed to default to show both .mdb and .accdb files.

2. All use of suser_name updated to suser_sname in-line with Microsoft depreciating suser_name

3. Internationalisation problems for South African (English) machines fixed.

4. Improvements in reverse engineering algorithms


MUST+WEB

1. Bug fixed on updates for filtering on web forms with SQL Server 2000 (ONLY APPLIES TO 2000), where
   update sql used schema prefix [Reporting].vw_tblParameters, changed to vw_tblParameters

========================================================================================================================
MUST+SQL VERSION 7.8 CHANGES (Also applies to MUST+Web)
========================================================================================================================

1. Support added for using "SQL Server Native Client 10.0" (SQL Server 2008) and 
   "SQL Native Client" (SQL Server 2005) ODBC drivers i addition to standard "SQL Server" drivers.

2. Where the names of linked tables had been renamed, for example a SQL Server table called Order_Details, linked in Access
   and renamed to [Order Details], the re-mapping of names when converting the SQL from Access which would uses [Order Details]
   to SQL Server using [Order_Details] in a view was failing to correctly re-map. This has been corrected.

3. When deciding to convert existing pass-through queries to SQL Server, we noticed that some developers have a pass-through
   query called for example called View_Orders which has sql (SELECT * FROM view_Orders), when View_Orders is also an existing View
   in SQL Server. In this case we do not want to replace the existing view in SQL Server, we now have a revision which prevents the
   existing view on SQL Server from being replaced.

4. Allow for use of embedded quotes  and round braces inside parameter names, which caused translation problems. 

5. Default setting changed to read in existing views

6. new ? button for help on understanding query translation errors

========================================================================================================================
MUST+SQL VERSION 7.7 CHANGES (Also applies to MUST+Web)
========================================================================================================================
1. Bug in SQL translation flagging IIF as a UDF fixed. 7.6 introduced a systematic bug where customers
    Observed a UDF called IIF being created, this was not a critical issue, but undesirable and has now been resolved.

2. Enhancement to use a Switched Case statement added. For IIF statements nested over 10 levels deep
    such as when splitting for each month in a year SQL Server does not support more than 10 levels. If
    the criteria is similar for each IIF, MUST will now implement a SWITCHED CASE statement to resolve this.

3. Support for reserved function names in ending a udf like MyDiaryDate() added. If a UDF ended in
   a name such as Date which matched an inbuilt Access function then this caused minor issues in
   translation. These have now been resolved.

4. Translation bug introduced in Version 7.6 for Trim statements fixed. Our thanks to Ian Johnson
    for pointing out this bug.

5. Benchmark of 96.4% translation achieved over 5760 queries during testing.

========================================================================================================================
MUST VERSION 7.7 CHANGES (Also applies to MUST+Web and MUST+SQL)
========================================================================================================================
1. Custom constraint name patterns added. Not everyone wants to use our constraint naming convention.
    If we use IDX_<tablename><fieldnamelist> for an index maybe you prefer INDX_<tablename> <fieldnamelist>.
   We now support custom patterns for naming primary keys, defaults, checks, triggers and all other constraints,
   and also include two built in templates from which you can select and then customise. Our thanks to Peter Hutchinson
   for recommending this change.

2. FDA bug in update triggers fixed, where a large number of records in the auditlog could be
   incorrectly tagged with the wrong users credentials. Also copy of TIMESTAMP column in audit tables
   changed from VARCHAR(30) to VARBINARY(8). Our thanks to Peter Hutchinson for spotting the problem
   and recommending the use of varbinary(8).

3. Failure when a tablename is changed (remapped to a new name) to rename the upsized the table correctly
   in the Access database to refer to the new name in SQL Server.

4. For exceptionally long table names 64 characters is the maximum in Access, but to link to these tables back to Access this reduces
   to 60 characters allowing for dbo_. Reduction checks now added for Schema_TableName limited to 64 characters.

5. Although Access allows a field size of 64 characters it can only link to a maximum field size
    of 63 characters, a test has now been added to reduce the field size to 63 characters and maintain
    uniqueness for upsizing tables, the impact of this remapping on SQL Conversion is presently not supported for this.

========================================================================================================================
MUST VERSION 7.6 CHANGES
========================================================================================================================

MUST 7.6 Changes
-------------------------------------------------------------------------------------------------------
1. Improved translation of GUID's supporting NEWID() as a default value
2. Support for multiple AutoNumbers where one is a GUID added


========================================================================================================================
MUST VERSION 7.4 CHANGES
========================================================================================================================

MUST 7.4 Changes
-------------------------------------------------------------------------------------------------------
1. In certain cases very long validation rules were being truncated, this has been corrected.
2. Bug fix when upsizing very long tablename/fieldnames when identifying errors in dates.
3. Unique Index Ignore Null, these were failing to generate the required triggers.

MUST+SQL 7.4 Changes
-------------------------------------------------------------------------------------------------------

1. Crosstab query conversion improved, occassionaly fields were missed.
2. Minor improvements to query translation .
3. New Options when generating T-SQL migration scripts for queries.
4. If you have partly converted some queries in the past and MUST has already created a parameters table in SQL Server
   (tblParameters_M) this now gets backloaded when loading the data dictionary from an existing SQL Server.
   This provides better support for incremental query conversion and where new parameters are spliced into the existing 
   table preserving existing parameters.
5. Support added for translating the switch statement


========================================================================================================================


Version 7.3
---------------

1. Low impact change. When resetting after migrating structure to allow migration to be repeated, the flags  
   to enable checks and auditing triggers were not being reset and thus not migrated when the migration was repeated in this way. 
   This is now fixed allowing a simple reset to clear the flags. Work around is to drop all the Indexes before resetting to repeat a migration, which clears the flags.

2. Very long field names around 60 characters were causing problems in generating constraint names.

3. New additional checks added to warn if schema + tablename exceeds 64 characters, as these can not be linked to access.

4. New additional check added for any field names 64 characters long, as Access can only link to fields of 63 Characters,
   this looks like some subtle issue in Access.

5. On certain validation rules involving "=" an additional "=" was being added

6. MID and MID$ have an optional length, the equivalent SUBSTRING in SQL Server does not allow this, so a default
   value of 255 is now added. Translating MID(string,5) to MID(string,255) - SQL TRANSLATION ONLY

7. Support added for translation of Access ALike (which was designed to ease ADO code transition) to Like now added, 
requested by customer J. M. Cazala (many thanks).

8. Ability to edit queries after testing which have have failed, then re-build and re-test.

9. Translation for Ltrim(Rtrim( bug fixed

10. Improvements in reducing false identification of parameters.

MUST Version 7.2
-------------------------------------------------------------------------------------------------------
1. Revised ribbon in 2007
2. Revised Help System


MUST Version 7.1
-------------------------------------------------------------------------------------------------------
1. Minor interface revisions

MUST Version 7.0
-------------------------------------------------------------------------------------------------------

1. Double click to select databases on sql server from list of databases.

2. Auto-remove of replication fields : s_Generation, s_Lineage, s_GUID, s_ColLineage and associated indexes.
   Can also be switched off under options

3. reverse engineering flags errors if multiple table level rules, also removes extra braces ((...)) and (...) in defaults
   and checks, single quotes removed on defaults 

4. WRITE CONFLICT ON F10 resolved

5. Additional warning added if attempting to link to a secured database

MUST VERSION 6.8
-------------------------------------------------------------------------------------------------------
1. Full support for the translation of multivalue fields including attachments. MUST will generate
   a new table to hold the multivalue data and migrate the data to the new table. See website for
   a full article describing this.

2. Extraction of attachments, with option to upload back into SQL Server IMAGE fields (OLE Objects),
   the utility MUST_OLEUploader.accde has been added to upload attachments back into SQL Server
   if required. However MUST will generate a reference to the filename so that the attachments can
   be held outside of the database. See website.

3. Default translation of OLE and Attachments changed from VARBINARY(MAX) TO IMAGE in SQL Server 2005,
   this can be changed if required, testing has indicated that Access has problems when linked to
   VARBINARY(MAX) for certain documents.

4. Reverse engineering modified to enable databases other than those generated by MUST to be converted
   back from SQL Server into Access; to support developers who continue to RAD in Access.

5. Treeview control version revised down to improve support for more environments.


MUST VERSION 6.7
-------------------------------------------------------------------------------------------------------
1. Because of problems with inserting records and returning incorrect autonumbers from
Full Database Auditing, primary keys have been removed from the audit tables, this
removes the problems.

2. Schema drop down when assigning tables now includes limit to list preventing
entry of values not in available list of schemas.

3. When building security, reporting schema now automatically created if required.

4. When assigning synonyms, if an object has no schema, then no synonym is created. Previously
they were created for all tables regardless of whether a schema was assigned.

5. For those who want to convert queries with parameters to stored procedures with parameters,
translation features to do this have been improved.

6. Fix for SQL translation using "[" in concatenations.

7. When schema changed for upsizing queries, parameter table needs to be on same schema, update now added
for this. The parameter view was also not being correctly generated in this situation

8 Queries ending with the word Forms or Reports failed to convert.

9 IIF translation to case statement fields failed when translating string concatenation using '[' string literal values.

10. backflushing primary keys had a bug leading to this feature failing, this has been resolved

11. Support for translating autonumbers with Random settings now supported.

12. Parameter identification during SQL Translation improved.

MUST VERSION 6.6
-------------------------------------------------------------------------------------------------------
1. A problem with missing the identity property on databases created in 2007 has been resolved
2. Following a greater use of the full database auditing, support for schemas has been added
   and minor improvements made in simplifying the operation of this feature in terms of altering
   users if any steps are not performed in the correct sequence

MUST VERSION 6.5 Changes From MUST VERSION 6.3/4
-------------------------------------------------------------------------------------------------------
1. User interface in standard upsizing improved.
2. Back-population from existing SQL Server Databases enhanced
3. New reverse engineering feature added to convert SQL Server databases to Access
4. External help system replaced with internal application files

MUST VERSION 6.3 Changes From MUST VERSION 6.2
-------------------------------------------------------------------------------------------------------
1. Significant enhancements to SQL Translation raising the accuracy of translation.
   In our benchmark of 2642 queries on 10 applications from different software houses
   failures were 56 queries, giving an 98% translation rate.
2. FDA, Full Database Auditing in all MUST Versions


MUST VERSION 6.2 Changes From MUST VERSION 6.1
-------------------------------------------------------------------------------------------------------

1. When selecting SQL Server 2000 query schema now removed and becomes dbo conversely
becomes Reporting when SQL Server 2005 used
2. When no parameters in application this caused a crash when testing queries
3. Pre-loading Views from SQL Server now excludes Vw_report_ and vw_form_
4. Potential crash when accessing broken queries fixed, reduces vba searching a little
5. When index selectivity is set to 0, all indexing gets upsized; this did not happen
in previous versions. Duplicate indexes are still excluded.
6. Automatic removal of With Check Option when views not updateable in SQL Server 2000,
which can otherwise cause a problem with the SQL Translation





