407-248-1481

Start Free Trial

Customer Area

QuoteWerks Update Center

Update Center home

example: QuoteValet "payment option" -deposit

114 Search results for SQL

Version: 23.0 Build: 2.09 Release Date: 04/13/2023 Type: Fix View All Features in Build

Addressed an issue with the Date/Time format for users with a Microsoft SQL 2019 and newer backend when integrating with ConnectWise PSA (formerly Manage), Kaseya BMS, Act! for Web, and QuickBooks Online.

Version: 23.0 Build: 2.09 Release Date: 04/13/2023 Type: Fix View All Features in Build

On the Product Lookup window if you right clicked on a product and chose 'Show product price history' or 'Show product price history for customer' or from the Quote Workbook, Tools ->Find Quoted Item actions would receive a SQL error.

Version: 23.0 Build: 2.05 Release Date: 03/21/2023 Type: Fix View All Features in Build

Would receive SQL query error when filtering on a date field with the operators of 'Greater than', 'Greater or Equal', 'Less than' , or 'Less or Equal' and leaving the search value blank. This would happened on the Open Document window and also the Opportunities Dashboard. Also when filtering by only a date when the field was a date/time field, sometimes expected results would not be returned due to UTC offset.

Version: 23.0 Build: 1.11 Release Date: 01/04/2023 Type: New View All Features in Build

Microsoft SQL Server 2022 is now supported!

Version: 23.0 Build: 1.03 Release Date: 11/28/2022 Type: New View All Features in Build

Various backups (like when importing products, etc) are now stored in the \QuoteWerks\Backups folder. Each day a backup is made a new folder will be created in the \Backups folder like "2022-09-25", and then any backup files created that day will be stored in that folder. The file name will contain the data type and the time in UTC 24 hour format. For a SQL backend, the backup feature for contact and vendors import now stores the backup data in the \Backups folder as (described above ) which is in a different location and format that previously used. If is the Access backend, the backup is saved as contacts.b01, vendors.b01, etc.

Version: 5.7 Build: 3.16 Release Date: 06/22/2022 Type: Fix View All Features in Build

For QuickBooks Online, ConnectWise Manage, and Kaseya BMS customers rehosted to Microsoft SQL that turned off TLS 1.0 and TLS 1.1 support on their SQL Server, and use only TLS 1.2, the database connection would sometimes be slow and/or timeout when integrating

Version: 5.7 Build: 3.16 Release Date: 06/22/2022 Type: Fix View All Features in Build

The feature that detected a database connection loss and attempted to re-connect automatically was not working for certain SQL backends because the connection error text was different.

Version: 5.7 Build: 2.11 Release Date: 02/11/2022 Type: New View All Features in Build

AutoRecover has replaced AutoSave. AutoRecover and AutoSave are both ways to prevent loss of your in-progress work due to a variety of reasons including power loss, computer lock ups, network disconnect, SQL server timing out, etc. AutoSave permanently saves any changes you make to your document as you are making the changes. The downside of this is that you can't open up a document and just make some "hypothetical" or "what-if" to see what it looks like because the AutoSave just made those changes permanent. Also, often we want to open up an existing document, make changes and then just save those changes as a new document, but you can't do that with AutoSave either because it just made those changes permanent to the original existing document. AutoRecover is a superior solution. It just quietly saves a temporary backup of your in-progress work. If you choose not to save the changes, or just close the document, it discards those changes. If QuoteWerks quit unexpectedly for the above reasons, then when you re-launch QuoteWerks it will ask you if you want to recover the in-progress changes. Additionally, AutoRecover has been implemented when the feature to "Terminate Running Instance" is used. Previously it would save copies of all quotes that were open on the terminated instance. Now it just creates AutoRecover documents for them all. If AutoRecover sounds amazing, its because it is! Microsoft Word Desktop has had an AutoRecover feature for decades. For Developers, the addition of AutoRecover will require some changes. The AutoRecover document is stored in the DocumentHeaders and DocumentItems tables just like a regular document, however there is a new DocumentHeaders.IsAutoRecoverDocForDocRecGUID field. If this field is populated then this is an AutoRecover document. If querying the database you will want to make sure that you filter these documents out with IsAutoRecoverDocForDocRecGUID=''. In fact, when looking for documents you will aready want to apply the filter of TemplateType=0 AND Superceeded=0 AND IsAutoRecoverDocForDocRecGUID='' so that the query excludes templates, superseded documents and AutoRecover documents. We also renamed UserSettings KeyName='EnableAutoSave' to KeyName='AutoRecoverEnabled' and UserSettings KeyName='AutoSaveInterval' to KeyName='AutoRecoverInterval'.Also, since an AutoRecover can replace the previously saved document, changing the DocumentHeaders.ID value, it is recommended to query a specific document based on the DocumentHeaders.RecGUID.

Version: 5.7 Build: 1.05 Release Date: 12/10/2021 Type: Fix View All Features in Build

When rehosting to SQL, the VendorRFQ tables would not get created.

Version: 5.7 Build: 1.03 Release Date: 11/29/2021 Type: New View All Features in Build

New VendorRFQ product release, including integration with QuoteWerks. VendorRFQ enables customers to communicate with their vendors, discussing and negotiating pricing and details for goods and services, collecting and organizing this information from one or all of their vendors. Your purchasing team will be able to compare and find the lowest prices to purchase available specific goods and services, while knowing at any given time which vendors have received the request for quote, and which have responded. All purchasing and procurement information is available in a centralized location for your team. Under the Utilities->Vendor maintenance menu you will want to setup your vendors, and make sure to enter your account number, the vendor sales rep name, email address, and phone. From the Quote Workbook, simply select an item and click on the VendorRFQ action button to create an RFQ and invite vendors. You can also do this from the Purchasing window. VendorRFQ requires the Corporate Edition of QuoteWerks, a SQL backend (either QuoteWerks DB Hosting subscription, or a SQL database that vendorrfq.com server can access), and a VendorRFQ subscription. VendorRFQ is only supported in master installations, it is not supported in Remote Site or Remote PC installations. The VendorRFQ integration is also supported in the Quote Workbook in QuoteWerks Web. A Misc Access right of "CannotUseVendorRFQLicense" is implemented to control the use of licenses per user. Under the Utilities->View Logs menu, in the Event log, events for "Licensing.VendorRFQLicenseCountExceeded" will be recorded.

Version: 5.6 Build: 5.12 Release Date: 09/24/2021 Type: Fix View All Features in Build

For SQL backend users, when importing large numbers of products into a product database with the Update option, the SQL transaction log would grow very large.

Version: 5.6 Build: 4.06 Release Date: 08/11/2021 Type: Misc View All Features in Build

For users rehosted to SQL, when importing products into an existing product database, the automatic backup of the existing data will be skipped if the product database has more than 150,000 records. Unfortunately, when a product database table contains this many records, it takes a long time to export all the data out, and the usual method of returning all records and then writing them all out causes "out of memory" issues. As a reminder, this automatic backup is not a replacement for proper full SQL database backups, but rather an extra resource in case accidental changes are applied to a product database. Normally, the backup is a tab delimited text file backup of the database and will be saved to a file with the same base name as the product database SQL table name like "Products_OurProducts" and will have a .bxx file extension.

Version: 5.6 Build: 3.32 Release Date: 05/11/2021 Type: Fix View All Features in Build

For SQL backend users, when running a Management Report on a product database would receive an error about the 'PRODUCTS' table was not included in the filter expression.

Version: 5.6 Build: 3.32 Release Date: 05/11/2021 Type: New View All Features in Build

For Access backend users, When importing products into an existing product database, a backup is always made of the product database. The backup file name will have the same base name as the product database file but with a .bxx extension. This backup feature now also happens for SQL backend users but is implemented a little differently. The backup is a tab delimited text file backup of the database and will be saved to a file with the same base name as the product database SQL table name like "Products_OurProducts" and will have a .bxx file extension. This is not a replacement for proper full SQL database backups, but rather an extra resource in case accidental changes are applied to a product database.

Version: 5.6 Build: 1.09 Release Date: 01/04/2021 Type: New View All Features in Build

When on the Product Lookup grid, you can now press the F5 key to refresh the grid with the underlying data in case that was just changed outside of QuoteWerks. This now works for Native Product Databases, MS SQL, ODBC, OLEDB, Excel, and Access data sources, in addition to QuickBooks, Peachtree, Zoho, and Salesforce.com.

Version: 5.5 Build: 5.21 Release Date: 08/17/2020 Type: Fix View All Features in Build

When linking to an external product data source like Access, Excel, MSSQL, ODBC, or OLEDB, even if you mapped a field to the UnitCost field, if a default CostModifier was set (under Document Items tab of Tools->Options), it would be applied causing the UnitCost to get overwritten with the CostModifier based calculation.

Version: 5.5 Build: 5.21 Release Date: 08/17/2020 Type: Fix View All Features in Build

When linking to an external product data source like Access, Excel, MSSQL, ODBC, or OLEDB, even if you mapped a field to the UnitPrice field, if a default PriceModifier was set (under Document Items tab of Tools->Options), it would be applied causing the UnitPrice to get overwritten with the PriceModifier based calculation.

Version: 5.5 Build: 4 Release Date: 04/22/2020 Type: New View All Features in Build

The nsetup.exe has a new option to "Install Microsoft SQL Server 2012 Native Client". This SQL Provider needs to be used to establish TLS 1.2 only SQL Database connections. Also, the installers of sqlClient2012_32bit.msi and sqlClient2012_64bit.msi are now installed in the QuoteWerks folder so they can be run separately at any time. Once this is installed on each machine that is running QuoteWerks, the backend.ini can be modified with these entries: SQLProvider=SQLNCLI11 and SQLEncryptConnection=-1 to fully activate a TLS 1.2 encrypted connection.

Version: 5.5 Build: 4 Release Date: 04/22/2020 Type: New View All Features in Build

The System tab of the Help->About menu now displays the "SQL Provider" and "SQL Encrypt Connection" settings.

Version: 5.5 Build: 4 Release Date: 04/22/2020 Type: New View All Features in Build

The backend.ini now supports the ini entry of SQLEncryptConnection=-1. This can be used to establish an encrypted connection with the SQL server. If the SQL Server itself is set to "Force Encryption" then an encrypted connection will be automatic.

Version: 5.5 Build: 3.04 Release Date: 03/10/2020 Type: Fix View All Features in Build

If backend.ini SQLProvider was specified for TLS 1.2 only support, the qw.dll backend API could not connect to the SQL database.

Version: 5.5 Build: 1.10 Release Date: 11/13/2019 Type: Fix View All Features in Build

In fresh installations, when saving a document, SQL Execute Error in SQLConnExecuteEx() QuoteWerks trapped Error (0) No value given for one or more required parameters. The new fields COnvertedFromRef, COnvertedFromOn, ConvertedFromBy were missing.

Version: 5.5 Build: 1.09 Release Date: 11/11/2019 Type: Fix View All Features in Build

QuoteWerks Update Key Validator, SSL security error, if you had implemented the TLS 1.2 only for SQL.

Version: 5.5 Build: 1.07 Release Date: 11/5/2019 Type: Fix View All Features in Build

For Salesforce.com users, non multi-currency organizations could receive an error about an invalid SQL call involving CurrencyIsoCode when saving opportunity line items when EnableQuantityScheduling is enabled for the Product table in Lightning.

Version: 5.5 Build: 1.07 Release Date: 11/5/2019 Type: New View All Features in Build

For customers rehosted to SQL that want to turn off TLS 1.0 and TLS 1.1 support on their SQL Server, and use only TLS 1.2, you can now run QuoteWerks in this environment. You must be running SQL Server 2014 or higher and in the backend.ini file under the [Backend] section, enter the ini key of SQLProvider=SQLNCLI11

Version: 5.4 Build: 1.17 Release Date: 12/07/2018 Type: Fix View All Features in Build

When rehosting to SQL the option "Copy data from the current Access databases to the new SQL database" should always be checked and disabled.

Version: 5.4 Build: 1.11 Release Date: 11/26/2018 Type: Fix View All Features in Build

When rehosting to SQL and then restarting QuoteWerks, the user that did the rehost appeared to still be logged into the licensing system.

Version: 5.4 Build: 1.08 Release Date: 11/19/2018 Type: Misc View All Features in Build

On startup QuoteWerks now checks the SQL server version to make sure it is supported.

Version: 5.4 Build: 1.08 Release Date: 11/19/2018 Type: New View All Features in Build

Microsoft SQL Server 2019 is now supported!

Version: 5.3 Build: 5 Release Date: 08/09/2018 Type: Fix View All Features in Build

For QuoteValet users with Payment Processing enabled, when initializing QuoteValet would receive error "SQL Execute Error in SQLConnExecuteEx()" about "String or binary data would be truncated." The Payments.Status field was not long enough for the new IntendsToPay status value.

Version: 5.3 Build: 5 Release Date: 08/09/2018 Type: Fix View All Features in Build

For Maximizer CRM On-Premise users, when selecting On-Premise from the Maximizer CRM Live Setup window and inputting an incorrect SQL Database Name, you would receive an "Object reference not set to an instance of an object." error message.

Version: 5.3 Build: 1.11 Release Date: 12/6/2017 Type: New View All Features in Build

Microsoft SQL Server 2017 is now supported!

Version: 5.3 Build: 4 Release Date: 06/11/2018 Type: Misc View All Features in Build

Increased timeouts when rehosting product databases to SQL for Amazon RDS and Azure.

Version: 5.3 Build: 2.02 Release Date: 01/23/2018 Type: New View All Features in Build

For API users, there is now an Installation.IsSQL property to indicate if the backend is rehosted to SQL.

Version: 5.3 Build: 1.07 Release Date: 11/30/2017 Type: Fix View All Features in Build

For fresh installations of version 5.3 when saving would receive error "SQL Execute Error in SQLConnExecuteEx() QuoteWerks trapped Error (0) No value given for one or more required parameters."

Version: 5.3 Build: 1.05 Release Date: 11/29/2017 Type: Fix View All Features in Build

When editing a product, on the Optional Items tab, and adding an item, would receive error "SQL Execute Error in SQLConnExecuteWithRecordsetReturn() QuoteWerks trapped Error (-2147217900) Invalid column name 'PartNumber'."

Version: 5.3 Build: 1.04 Release Date: 11/27/2017 Type: New View All Features in Build

For SQL users, all Memo fields in the datbase have been converted from NTEXT to nvarchar(MAX) for better performance and also because the next version of SQL will discontinue the NTEXT field type. Only SQL Server 2005 and higher support nvarchar(MAX) fields so we have discontinued support for MS SQL versions earlier than 2005.

Version: 5.2 Build: 8.12 Release Date: 07/11/2017 Type: Misc View All Features in Build

Most SQL queries timeout setting was increased from 30 seconds to 45 seconds.

Version: 5.2 Build: 6.07 Release Date: 05/30/2017 Type: Fix View All Features in Build

For SQL 2000 users, QuoteWerks trapped Error (-2147217865) Invalid object name 'sys.syslanguages'.

Version: 5.2 Build: 2.26 Release Date: 02/10/2017 Type: New View All Features in Build

Added Misc Access Right "CannotManuallyModifyProductQuery". When this is set, the "Show SQL" option will not appear on the Product Lookup window.

Version: 5.2 Build: 2.22 Release Date: 01/26/2017 Type: Fix View All Features in Build

When installing QuoteWerks update, converting from v5.0 Build 5 or earlier to version 5.2 would receive error: Error opening recordset in ConnOpenRecordset(): QuoteWerks trapped Error (-2147217865) Invalid object name 'SystemSettings'. SQL=SELECT KeyValue FROM SystemSettings WHERE SectionName='System' AND KeyName='PrintElementOrder'

Version: 5.2 Build: 2.22 Release Date: 01/26/2017 Type: Fix View All Features in Build

When converting a QUOTE to an ORDER that had multiple revisions and some revisions where deleted, could receive error: An error occurred in the SaveDocumentToDTFFileEx function. The Document Header record was not found in the database. SQL=SELECT * FROM DocumentHeaders WHERE ID = 0

Version: 5.2 Build: 1.29 Release Date: 11/09/2016 Type: Fix View All Features in Build

On startup before the version 5.2 conversion is run received error opening recordset in ConnOpenRecordset() SQL=SELECT KeyValue from SystemSettings WHERE SectionName='QuoteValet' AND KeyName='TenantAccountNumber'

Version: 5.2 Build: 1.28 Release Date: 11/08/2016 Type: Fix View All Features in Build

Increased SQL Query timeout from 30 to 60 seconds in the Open Document, Management Reports, and Tools->Find Quoted Item areas.

Version: 5.2 Build: 1.28 Release Date: 11/08/2016 Type: Fix View All Features in Build

Fixed issue with the re-establish connection for SQL database lost connections.

Version: 5.2 Build: 1.28 Release Date: 11/08/2016 Type: Fix View All Features in Build

On installations rehosted to SQL many years ago, when upgraded to v5.1 build 6.01 - 6.06 in some cases, would receive error "INIFileName was empty for user..." when starting QuoteWerks. This version 5.2 Build 1 upgrade will correct this issue for all versions in all scenarios.

Version: 5.2 Build: 1.28 Release Date: 11/08/2016 Type: New View All Features in Build

When rehosting to SQL you can now specify an existing Database to rehost to. This is useful so that you do not have to supply a SQL server UserID that has the security rights to create databases.

Version: 5.1 Build: 6.07 Release Date: 07/11/2016 Type: Fix View All Features in Build

On installations rehosted to SQL many years ago, when v5.1 Build 6.01 - 6.06 was installed, in some cases, would receive error "INIFileName was empty for user..." when starting QuoteWerks. User that install v5.1 Build 6.07 that have not installed build 6.01 - 6.06 will no longer receive this error. Any users that installed v5.1 Build 6.01 - 6.06 that experience this issue will need to contact technical support for assistance.

Version: 5.1 Build: 6.06 Release Date: 07/05/2016 Type: New View All Features in Build

Microsoft SQL Server 2016 is now supported!

Version: 5.1 Build: 4.22 Release Date: 03/14/2016 Type: Fix View All Features in Build

When opening a quote would sometimes receive error like "Error opening recordset in ConnOpenRecordset(): Error (-2147217900) Incorrect syntax near 'A26DDA8F4DF6963FE629216E7534'. adoConnState=1 SQL=SELECT DocNo, ID FROM DocumentHeaders WHERE RecGUID=6979A26DDA8F4DF6963FE629216E7534"

Version: 5.1 Build: 4 Release Date: 02/03/2016 Type: Fix View All Features in Build

Issue with determining SQL Server version for SQL Server 2012 for the "CU" cumulative update notation like "SQL Server 2012 (SP3-CU1)".

Version: 5.1 Build: 4 Release Date: 02/03/2016 Type: New View All Features in Build

Added new macro fields: &SYS_FirstDayOfCurrentYearForSQL, &SYS_LastDayOfCurrentYearForSQL, &SYS_FirstDayOfLastYearForSQL, and &SYS_LastDayOfLastYearForSQL. These are especially useful in report filters.

Version: 5.1 Build: 2.25 Release Date: 12/15/2015 Type: Fix View All Features in Build

When a SQL hosted Remote installation of QuoteWerks is in the middle of a synchronization and the network connection is lost, when restarting QuoteWerks the error "Error, no records found in SecurityAccounts table!" could be received. Changes have been made. Now the records from the table SecurityAccounts are copied into the SecurityAccounts_BACKUP_DataOnly table immediately before all the records are deleted out of SecurityAccounts in preparation to receive the newer records from the master installation. When QuoteWerks starts, if it detects that there are no SecurityAccounts records, it checks to see if it is a Remote installation and checks to see if the SecurityAccounts_BACKUP_DataOnly table exists. If both conditions are true then it restores the SecurityAccounts data back to the pre-synchronization version. At this point the user can log back into QuoteWerks and run the synchronization process again.

Version: 5.0 Build: 1 Release Date: 11/07/2014 Type: New View All Features in Build

Multiple Product Database Search. You can now do a product search across multiple product databases. This will search all selected product databases including native product databases, and external product data sources like SQL, OLEDB, Autotask, ConnectWise, salesforce.com, QuickBooks, etc

Version: 4.9 Build: 10.18 Release Date: 09/25/2014 Type: Fix View All Features in Build

For installations rehosted to SQL would receive error about LastModifiedBy field not being in the product database. This would happen during a synchronization process, or when creating a new product database.

Version: 4.9 Build: 8 Release Date: 06/05/2014 Type: New View All Features in Build

Microsoft SQL Server 2014 is now supported!

Version: 4.9 Build: 4 Release Date: 02/25/2014 Type: Fix View All Features in Build

Error about SQL "incorrect syntax" when deleting an approval profile.

Version: 4.9 Build: 1 Release Date: 10/08/2013 Type: Fix View All Features in Build

Would receive error "The text, ntext, and image data types cannot be used in the WHERE, HAVING, or ON clause, except with the LIKE or IS NULL predicates." or error "The data types ntext and varchar are incompatible in the equal to operator." This would happen when rehosted to the SQL backend and an "Equal to" search was performed on a Description field which is a memo field.

Version: 4.9 Build: 1 Release Date: 10/08/2013 Type: Fix View All Features in Build

When creating a new user, the user name is limited to 50 chars. Entering larger would cause an error when the installation was hosted on SQL.

Version: 4.8 Build: 5.12 Release Date: 07/12/2013 Type: Fix View All Features in Build

When creating a new product database on an installation that is rehosted to SQL, in the case where all the table names in the database added together where longer than 32,768 characters would receive an overflow error.

Version: 4.8 Build: 5 Release Date: 06/03/2013 Type: Fix View All Features in Build

The auxdata.mdb file was not getting rehosted to the SQL database during the rehost to SQL process.

Version: 4.8 Build: 5 Release Date: 06/03/2013 Type: Fix View All Features in Build

After a rehost to SQL the contacts.mdb and auxdata.mdb files were not getting renamed to contacts.rehosted and auxdata.rehosted respectively.

Version: 4.7 Build: 7 Release Date: 07/12/2012 Type: Fix View All Features in Build

When rehosted to SQL, from the Quick Lookup bar if choosing to lookup an item using the description field would receive an error.

Version: 4.7 Build: 7 Release Date: 07/12/2012 Type: Misc View All Features in Build

Changes to the Product Lookup window "Show SQL" option.

Version: 4.7 Build: 7 Release Date: 07/12/2012 Type: New View All Features in Build

Microsoft SQL Server 2012 is now supported!

Version: 4.7 Build: 4 Release Date: 03/09/2012 Type: Misc View All Features in Build

Added new settting to the backend.ini file. Under the [Backend] section, the key SQLForceUNICODE=-1 is used to force QuoteWerks to save to the SQL database in UNICODE format. This is needed in some countries depending upon their language and character sets.

Version: 4.7 Build: 1.01 Release Date: 11/16/2011 Type: Fix View All Features in Build

Error 438 when clicking on Finish tab when attempting to Rehost to SQL.

Version: 4.6 Build: 5 Release Date: 06/10/2011 Type: New View All Features in Build

For Corporate Edition users rehosted to SQL, Email Templates (introduced in this build) can now be rolled out to remote installations or bi-directionally synchronized (including deletions).

Version: 4.6 Build: 3 Release Date: 02/18/2011 Type: Fix View All Features in Build

For users with the SQL backend, during the build update would receive error "'NoPSTOnShipping' is not a constraint.

Version: 4.6 Build: 3 Release Date: 02/18/2011 Type: Fix View All Features in Build

For users with the SQL backend, if using the Open Export module to export xml or QuoteValet to re-upload an existing quote would receive "invalid use of null" error.

Version: 4.6 Build: 1.11 Release Date: 12/22/2010 Type: Fix View All Features in Build

In version 4.6 when rehosting to SQL, the new SecurityProfiles table was not getting created. Also, this table was not getting synchronized in a Corporate Edition sync.

Version: 4.5 Build: 7 Release Date: 06/21/2010 Type: Fix View All Features in Build

When running a product catalog report containing a Custom field on an installation that is running on a SQL backend, would receive error message "The field 'Products->CustomText01' found in the report layout is not in the query results, and cannot be displayed.'"

Version: 4.0 Build: 49 Release Date: 08/27/2009 Type: Misc View All Features in Build

Added new [Create Security.mdb for Remote PC or Site] button under the Utilities | License Manager. This is useful for populating an Access Security.mdb file with the current security data from a SQL hosted QuoteWerks backend. This is needed in situations where the Master installation has been rehosted to SQL, but the Remote PC (or Remote Site) installations may not have been re-hosted having opted to stay with the MS Access Backend.

Version: 4.0 Build: 49 Release Date: 08/27/2009 Type: Misc View All Features in Build

The file Security.dbt is now always installed whether an installation has been rehosted to SQL or not. This is an empty Security.mdb database with the current security database schema.

Version: 4.0 Build: 49 Release Date: 08/27/2009 Type: New View All Features in Build

For Canadian users, added support for a document level GST Tax rate. This is important now that the Canadian government has started changing the GST tax rate. Before installing this update we recommend that you do a Utilities|Merge Remote Documents, then install the update, then using the medic utility, you will need to run a SQL command to update all documents prior to the date that you changed the GST Tax Rate in QuoteWerks with the older GST Tax Rate. For MS Access backend database the SQL command would look similar to: "UPDATE DocumentHeaders SET GSTTaxRate=0.05 WHERE LastModified < #01/01/2008#", and for a MSSQL backend the SQL command would like similiar to "UPDATE DocumentHeaders SET GSTTaxRate=0.05 WHERE LastModified < '01/01/2008'". After you run the SQL update query, run the Utilities|Rebuild CM Transport files to update all the DTF files with the new field and data.

Version: 4.0 Build: 47 Release Date: 06/09/2009 Type: Fix View All Features in Build

For Corporate Edition installations rehosted to SQL, When importing a an xml file (formatted to QuoteWerks specifications) from the File|Import Document menu and the data for a field was longer than the length supported by QuoteWerks, an error would be displayed, and that record (the DocumentHeader record, or a DocumentItems record) would not be imported.

Version: 4.0 Build: 44.06 Release Date: 02/10/2009 Type: Fix View All Features in Build

After a document purge process completed, a message would remind the user to compact the database even if the database was hosted to SQL.

Version: 4.0 Build: 36 Release Date: 05/09/2008 Type: Fix View All Features in Build

When drilling down on a root Ingram Micro Categories folder would receive Query Error (-2147217913) Automation error SQL=SELECT * FROM [CATALOG] WHERE left$(CATSUBCAT,2)='11' ORDER BY VENDOR.

Version: 4.0 Build: 33 Release Date: 02/15/2008 Type: Misc View All Features in Build

The title bar of a critical error message now includes the version of the SQL backend if a SQL backend is in use.

Version: 4.0 Build: 33 Release Date: 02/15/2008 Type: Misc View All Features in Build

When entering Remote License Key, QuoteWerks will now notify you that you need to copy the security.mdb database file to this installation to complete the acceptance of the Remote License Key. Additionally, for Corporate Edition users, until this has been done, the ability to rehost the backend to SQL will not be available.

Version: 4.0 Build: 33 Release Date: 02/15/2008 Type: New View All Features in Build

Added macro "&SYS_45DaysAgoForSQL".

Version: 4.0 Build: 33 Release Date: 02/15/2008 Type: New View All Features in Build

Microsoft SQL Server 2008 is now supported!

Version: 4.0 Build: 29 Release Date: 05/18/2007 Type: Fix View All Features in Build

In Corporate Edition rehosted to SQL, when synchronizing Product Data Sources, if you selected "Do Not Synchronize" for a Product Data Source, a Product Data Source listing would be created and appear under the Products|Setup Product Data Sources menu, but the actual data tables for the Product Data Source would not be created resulting in errors whenever the Product Data Source was accessed in the Product Lookup window.

Version: 4.0 Build: 24 Release Date: 03/13/2007 Type: Fix View All Features in Build

If a product data source table name contained non alphanumeric characters like "&" or a space would receive SQL error about Incorrect Syntax when querying the database and when trying to delete the database.

Version: 4.0 Build: 24 Release Date: 03/13/2007 Type: Fix View All Features in Build

When running the Corporate Edition of QuoteWerks that is rehosted to MS SQL. If you deleted a product from a product database, or deleted all products from the product database (during a product import), or removed a product data source would receive error "trapped error Cannot insert duplicate key row in object 'SyncTransactions' with unique index 'TransactionGUID'".

Version: 4.0 Build: 24 Release Date: 03/13/2007 Type: Misc View All Features in Build

In preparation for Windows Vista support, corrected unable to connect password issue on Windows Vista with product databases that were hosted on SQL Server that required a password. Similar issue also occurred with Configurator "Login Failed for user 'xx'.

Version: 4.0 Build: 23 Release Date: 11/03/2006 Type: Fix View All Features in Build

When using QuoteWerks with the SQL backend and creating a management report where a filter item for a date field is compared to an empty value like "Equal to {empty}" would receive error "IsNull() requires two parameters".

Version: 4.0 Build: 21 Release Date: 08/09/2006 Type: Fix View All Features in Build

When selecting the File|Export To Document Transport file menu and choosing to export the current document, if it was a new document with no changes that has never been saved, would receive an error "An error occurred in the SaveDocumentToDTFFileEx function. The Document Header record was not found in the database. SQL=SELECT * FROM DocumentHeaders WHERE ID = -1"

Version: 4.0 Build: 21 Release Date: 08/09/2006 Type: Fix View All Features in Build

In the Product Data Source Wizard, if you selected to create a new QuoteWerks native product data source and then click on the [Back] button and then select to create a link to an Access, SQL, ODBC, OLEDB or Excel product data source, the wizard step that lets you select mappings and titles would not be displayed.

Version: 4.0 Build: 20 Release Date: 08/01/2006 Type: Fix View All Features in Build

Error "(-2147217900) Syntax error in FROM clause. SQL=Select * from" when upgrading from QuoteWerks 3.0 to QuoteWerks 4.0. Related to new InUseDocuments table added in build 16.

Version: 4.0 Build: 20 Release Date: 08/01/2006 Type: Fix View All Features in Build

When rehosting an installation of QuoteWerks to a SQL backend that was first installed as build 16 or build 17 would receive error "Error in ExecuteSchemaChange:" ... "Column name 'Index_3E260F3F_9C20_4D99" does not exist in the target table". This will no longer occur for installations first installed as build 18 or higher.

Version: 4.0 Build: 20 Release Date: 08/01/2006 Type: New View All Features in Build

The maximum number of line item supported in a quote has been increased to 1500 for Corporate Edition users that have rehosted to SQL. For Standard and Professional Edition users and Corporate Edition users that have not rehosted to SQL, the maximum number of line items is 600. Please note that while the number of supported line items has increased, more line items equates to more data that will be saved thereby increasing the amount of time it takes to open and save these larger documents. Additionally, opening and saving 1500 line item quotes may require additional RAM on the PC. Saving a 1500 line item quote with 350 characters of description in each line item takes around 30 seconds to save on a Pentium 4 (1.6 MHz) machine running Windows 2000 with 1.2 GB RAM saving to a Microsoft SQL Server 7 database.

Version: 4.0 Build: 20 Release Date: 08/01/2006 Type: New View All Features in Build

With the Corporate Edition (when rehosted to SQL), Product Data Sources on a Remote Install can now be synchronized instead of just replaced. Also, if the Product Data Sources reference an external Excel file, external Access file, the Tech Data or Ingram Micro offline price files the files will be copied over to the remote replacing the copy of the files on the remote if older. You can now also select individual product databases to synchronize or overwrite. Also, when products or entire product data sources are deleted from the master install, they will be deleted from the remote install too.

Version: 4.0 Build: 20 Release Date: 08/01/2006 Type: New View All Features in Build

Support for Microsoft SQL Server 2005 backend.

Version: 4.0 Build: 12 Release Date: 10/13/2005 Type: Fix View All Features in Build

When rehosted to the SQL backend, and running a report that used custom fields from both the DocumentHeaders and DocumentItems tables, the data returned for those fields could be mixed between the fields.

Version: 4.0 Build: 11 Release Date: 07/15/2005 Type: Fix View All Features in Build

When using &SYS_..ForSQL macros in report filters and your computer's date format is not set to the USA date format, the macros would not resolve to the correct date values.

Version: 4.0 Build: 9 Release Date: 05/05/2005 Type: Misc View All Features in Build

If a QuoteWerks installation is activated with a Corporate Edition License Key and is rehosted to SQL, when removing this primary key you will be notified that if you do not replace this key with another Corporate Edition License Key, your installation will become unusable.

Version: 4.0 Build: 6 Release Date: 02/15/2005 Type: Fix View All Features in Build

Error "specified index is invalid" when using the Corporate Edition rehosted to SQL and using the debug command "security" to copy all the security information to an access security.mdb file.

Version: 4.0 Build: 4 Release Date: 01/10/2005 Type: New View All Features in Build

The "Show SQL" checkbox is now available again (it used to be in version 3.0) on the Product Lookup window. Advanced users can use it to manually edit SQL queries used to search for the products.

Version: 4.0 Build: 4 Release Date: 01/10/2005 Type: New View All Features in Build

For Corporate edition users that have rehosted to MS SQL, the Utilities|Sync feature has been improved. Now, when rolling out data to a remote install you can choose which data to rollout. Previously all data except the quotes/orders/invoices was automatically rolled out. For example, you can choose to rollout Bundle data, but not configuration data.