Build 2022-10-09 - Support is added for Sage 300 2024. Builds 2023-06-21 - Adjusted for Sage 300 2023.2 and 2023.3: The SQL Server Login ID used to connect to SQL Server must have sufficent rights to the Vault and Store databases, if you want to see or change Sage 300 database profile information. If you use the Login ID sa, you should have such rights. Build 2022-12-20 - Fix issue after creating a new company when not in a Sage 300 environment. Build 2022-11-24 - Fix issue with Sage 300 2023 companies set up with an ODBC source. Build 2022-11-23 - Internal improvements to licensing screens. Build 2022-09-19 - Support is added for Sage 300 2023. Build 2022-06-16 - The TaiRox Licensing screen has been updated with improved diagnostics. Build 2022-04-26 - When logging into a SQL Server instance, a checkbox allows users to remember SQL Server passwords. The remembered passwords are encrypted. - Show the System Database in the properties window of a Company Database. Build 2022-03-11 - When showing server properties, checking user access to a database is now done in a manner consistent with other operations. Build 2022-03-07 - Sage 300 Database Setup, shows DBSetup information in 2 grids. The top grid shows all system databases and the bottom grid shows all linked company databases. For selected company databases, the server name and credentials will be set to the system database settings. Build 2022-02-22 - A new program is added to the Tools Menu: Update Company Database Profiles. Update Company Database Profiles updates the server name and credentials for company databases that are linked to a system databases. The company settings are set to the system database settings for all linked companies in a single step. Build 2022-01-10 - The TaiRox Licensing screen has additional diagnostic checks, e.g. license is for a different TaiRox product. Build 2021-10-21 - Improved DBLoad functions Much less disk space used when loading large tables. 10%-40% less time taken for large loads. Less memory used on client computer when loading tables. - Improved cancelling during long operations of a very large table. Build 2021-09-24 - An ability to see fragmented Sage 300 tables and to reindex them has been added. Build 2021-08-31 - Support is added for Sage 300 2022. Build 2021-03-10 - Support is added for installation on the Sage Partner Portal. Build 2021-02-24 - The deactivate function will now remove data dictionary rows and 2-letter tables in situations where a row has been removed from the CSAPP in an (incomplete) attempt to deactivate an application. Build 2020-09-18 - Support is added for Sage 300 2021. Build 2020-06-25 Build 2020-06-05 - Improvements to licensing diagnostics. Build 2020-05-12 - Support added for Azure SQL Server. Build 2019-08-15 - Resolves display problems with low screen resolution computers. - Support for Sage 300 2020. Build 2019-05-13 - Will now dump and load improperly named tables, e.g. ORDER (no 2-letter prefix). Build 2019-04-30 - On a DBLoad, the primary index is made clustered if no other index is clustered. This conforms to Sage 300 DBLoad behaviour. Build 2019-01-15 - There is improved error handling when the server name cannot be resolved by the DNS. - The version will be correctly displayed for SQL Server 2017. Build 2018-08-27 (6813) - Support for Sage 300 2019. Build 2018-08-04 (6790) - Fixes issue with an SDK third party product creating a table named ORDER (no 2 letter prefix). Build 2017-03-24 (6292) - When dumping a database, the collation is stored in the DCT file in an unused location. - When loading a dataset that has collation information, a warning will be displayed if this does not match the database collation. - When deleting a database, the Database Setup record will be removed. - If the DCT extension is associated with Fast DBTools, opening a dataset results in Fast DBTools being started and the Dataset Explorer being opened to the folder containing the dataset. Build 2017-02-09 (Build 1.0.6249.22257) - Improved error handling when Dataset directory does not exist. Build 2017-01-09 (2.0.6212.27545) - A more modern file browser is used when navigating directories looking for data sets to browse. Fast DBTools can show your the contents of data sets (REC files) without loading the tables into a SQL Server database. Build 2016-09-13 (2.0.6100.27460) - When DBDumping a single company, a warning will appear if there are extra SQL objects in the database that will not be saved in the DBDump: triggers, extra tables, extra columns in SDK tables. - When DBDumping a single company, a warning will appear if there are stored procedures or views in the SQL Instance which might reference the company being DBDumped. Build 2016-09-08 (2.0.6095.26572) - The Connect to SQL Server dialog is displayed on start up. - When creating a new database like an existing database, accept a description that will be used as the database setup (DBSetup) description (instead of the database id). - When loading, a checkbox is presented. If checked, the database setup description will be used to update the common services company name. This saves time and confusion when repeatedly refreshing a test database. Build 2016-05-27 (2.0.5991.18359) - This version supports Sage 300 2017. - Databases that start with digits will now be correctly locked when restrict access selected. Build 2016-04-29 (2.0.5961) - Corrected minor UI issues, including progress bar stalling at 99%. Build 2016-01-28 - Fixed issue where the Load option was not enabled and should have been. Build 2015-12-03 - DBDump and DBCopy now provide a "Sage" option to gaurantee exclusive access to a source database. Build 2015-11-03 - The ability to shrink a database has been added. - The refresh operation will now function correctly when using a server alias such as localhost. - Improved error handling when user tries operations on a non-Sage 300 database (e.g. Deactivate App). Build 2015-10-19 - Support provided for Sage 300 2016. Build 2015-09-25 - Updated SQL Server object library to support newer and older SQL versions. Build 2015-09-24 - Rewritten to provide a way to explore Sage 300 database instances. - Multiple DBDumps at one time (multi-threaded) supported. - Adjusted for 2016 DBDump format - longer fields. Build 2014-12-03 - Copies user rights with new ORGID to new company when doing a DBLoad or DBCopy. Build 2014-06-26 - Repairs Audit Stamps in REC files where 0 BCD and blank values have been used to indicate "no audit stamp". In these cases, sets the audit stamp to the ADMIN user and the current date and time. Build 2013-07-17 - Improved error diagnostics for very large databases (several 100s of Gb). Build 2013-03-28 - For Accpac compatibility, allow "non-breaking-space" CHAR(160) to be part of a character column (don't trim). Build 2013-01-07 - Creates DATADICT table in database if not yet set up (eliminates need to use DB Setup). Build 2012-10-13 - Opens files on load readonly so you do not get an access violation when loading data from a readonly source. Build 2012-09-07 - Support for Sage 300 ERP 2012 Build 2012-07-24 - Fix to occasional slow startup (white screen). Build 2012-07-18 - Fix issue with inconsistent audit stamp column names. Build 2012-07-17 - Fast DBDump will correct nuls in character fields. - Fast DBLoad sets ORDID column in audit stamp (o.w. report issues if changing databases). Build 2012-06-28 - Fix long fields issue, can arise with Audit Logger. Build 2012-06-27 - Add deactivate tab. - Deactivating Audit Logger may significantly increase Accpac performance. Build 2012-05-11 - Fix issue that occurs when sa password contains a semi-colon. Build 2012-04-28 - Extend server timeout from 30 seconds to None. Build 2012-04-25 - Applications button operation fixed when CSV format used. Build 2012-04-20 - Manual now accessed and displayed properly from help menu. Build 2012-04-17 - Dump operation will create a dataset folder if it does not exist. Build 2012-04-16 - Includes DBCopy and DBDump functionality. - Able to dump and load in CSV or REC format. Build 2012-03-14 (SOX FastDBLoad) - Detects potential non-Accpac database and displays error.