407-248-1481

QuoteWerks version 5.2 BETA

Quick Start
You can download the current beta here:

Expect to delete the Beta and your Beta data when testing is complete, so DO NOT update your live installation. The Beta install CANNOT be upgraded to the final production release.
 

Revision History

Build 0.12b (7/20/16 1:34pm) - Latest build.

Build 0.02b (7/20/16 1:32pm) - Moved Settings Manager to Help->About System tab. Added edit and delete buttons on Settings Manager.

Build 0.01b (7/20/16 11:00am) - First release.

What you need to know
We are ready to release our first beta of QuoteWerks 5.2.

This truly is a beta. It is not one of our typical interim releases. The difference being that we will most likely still add/remove/change fields from the database, and there is some functionality that we know is incomplete.

We recommend that you only install this as a fresh installation somewhere so that you can just delete it when you are done beta testing.

This beta period is essentially the time for you to test out the new features with your data using it in the way you would use it. Through this process, any issues or things that need to change will come to light.

You can download the full install from the hyperlink above.


Instructions
Coming soon..

Areas of Interest (new 5.2 features)

Coming soon...
Coming soon...
 

Documentation
We don't have documentation prepared yet....Let's start with getting it installed and we will take it from there. Just call us or email us with any questions.


Feedback
Just call us or email us with any questions. We look forward to your feedback!
 

BETA Release Installation Notes

  • Note, since an BETA release is designed to be used for a limited time period until the production build is released, QuoteWerks will notify you that you are running an BETA release build every time you start it.  This message cannot be turned off.  You will need to wait until the production release is released and then install it to make the message disappear.
     
  • After you install this build, to confirm that this build has been successfully installed, select the Help->About menu in QuoteWerks. On this window, the build number should match the build number that you just installed.
    Please note. No-one can be running QuoteWerks when you install the update.
     
  • If you have installed QuoteWerks on a network workstation, you will also need to re-run the node installation (\QuoteWerks\nsetup.exe) for each additional workstation that uses QuoteWerks on your network. Running the node installation is very easy to do. It does not ask you for any information, and it does not affect any of your settings.
  • If you install the newest build into your existing QuoteWerks directory, you do not need new registration codes. You will only need new registration codes after installing a new build update if you installed it into a brand new directory by accident.

   

QuoteWerks Version 5.2 INI to DB Changes

 

Version 5.2 implements significant changes to where the data is stored. Most data stored in INI files have been moved to database tables in preparation for QuoteWerks Web.

 

After updating to version 5.2 you will see some different files.

Take for example the User “John Lewe”. The user ini file used to be “JLEWE.INI”. In this example, after the upgrade, there will no longer be a JLEWE.INI file. You will see JLEWE.backup01 and JLEWE.UPGRADED01. Once you are confident the upgrade process has correctly transferred the data, you can delete both of these files.

The upgrade goes through a list of users currently in the QuoteWerks database user list and does the INI conversions. If you have deleted a QuoteWerks user and their, for example, JLEWE.INI file, was left behind, the upgrade will not detect it and will not convert it so you will want to manually delete those files as part of a manual cleanup process.

Of note, the spelling dictionary file for each user was named, for example, JLEWE.dic. The dictionary files have now been renamed to instead use the users full name, so for example, JohnLewe.dic. Any .dic files left behind from a previously deleted user will not be renamed.

 

Similarly, as system INI files like lookup.ini are converted to database storage you will end up with oexport.backup01 and oexport.upgraded01 files. These files will be moved into the \QuoteWerks\Backups\xxx folder. Once you are confident the upgrade process has correctly transferred the data, you can delete both of these files.

 

All of the settings that have been transferred to database tables can be viewed from the new Settings Manager accessible by clicking on the [Settings Manager] button on the System tab of the Help->About menu. The Settings Manager is also available from within the Medic Utility by selecting the Utilities->Settings Manager menu.

 

We have also added new API events and methods (listed below) so that developers can access this data in its new location.

  

 

Before version 5.2

Version 5.2 and higher

 

->New Database SYSTEMSETTINGS.MDB and table SystemSettings

->New Database USERSETTINGS.MDB and table UserSettings

->New Database SITE.MDB and table SiteSettings.

-> New SITEBOOT.INI file

site.ini

->No longer exists

->Most contents ported to SystemSettings table in SystemSettings.mdb

->Some contents ported to SiteSettings table in docs.mdb

->Of note, [Scripting] section settings moved to SystemSettings table.

 

->remaining small number of settings now stored in SiteBoot.ini

 

{UserIniName}.ini  (like admini.ini)

->{UserIniName}.ini files no longer exist

->Contents ported to UserSettings table in UserSettings.mdb

{UserIniName}.dic  (like admini.dic)

->{UserIniName}.dic files are now named with the User Name instead of an 8 character cryptic name. It is comprised of all the characters in the user name that are the letters A-Z and numbers 0-9

lookup.ini

->lookup.ini file no longer exists

->Contents ported to SystemSettings table in SystemSettings.mdb

oexport.ini

->oexport.ini file no longer exists

->Contents ported to SystemSettings table in SystemSettings.mdb

sys_cache.ini

->sys_cache.ini file no longer exists

->Contents ported to SiteSettings table in docs.mdb

sync.ini

->sync.ini file no longer exists

->Contents ported to SiteSettings table in docs.mdb

Backend.ini

->still exists

Menuopts.add

->still exists

 

 

SITEBOOT.INI file will now contain only:

 

[System]

Version=

Build=

SyncVersionBuildBreaksList=

UpgradeInProgress=

FirstInstalledVersionBuild=

UpdateKey=

DefaultContactManager_ReadOnly=

 

[Addons]

Addon1=

Addon1Users=

Addon2=

 

[Contact Managers]

3rdPartyLinkName= for api integrations, it is easier for them to write to an ini file during their installation.

3rdPartyLinkDescription=

3rdPartyLinkSettings=

 

QW.INI ini file will now contain only:

 

[System]

DataPath=

 

 

MENUOPTS.ADD

 

[Menu]

Quote Importer=%CommonFiles%\QuoteWerks\qwQuoteImporter\qwQuoteImporter.exe

Note Pad=notepad.exe

 

Along with these changes, changes were made to the API to give developers the tools they need to integrate these new changes:

 

-New: For API users, added the events: BeforeSynchronization(sXMLData, bCancel) AND AfterSynchronization(sXMLData)

 

-New: For API users, the event BeforeSaveDocument(ByVal iSaveAction As Integer, ByRef bCancel as Boolean) now fires for the AutoSave events with an iSaveAction=4.

 

-New: For API users, added event AfterSaveDocumentEx(ByVal iSaveAction As Integer, ByVal iResult As Integer, ByVal sXMLData As String). This event provides more information than the existing  AfterSaveDocument() event.

 

-New: The creation of user login names is no longer limited by the 8 character user INI file name generation. You used to receive a message like "The User Name specified cannot be added because it conflicts with the {username}.ini file of JLEWE.INI"

 

-New: Under the [Addons] section of the siteboot.ini file there is a new AutoRunXUsers= key. Here you can specify a comma delimited list of users that you want the addon for. For example the AutoRun1=notepad.exe and the AutoRun1Users=John Lewe, Brian Laufer

 

-New: For API users, added a series of methods to read/write/delete settings from the new Settings table since the data has been moved out of ini files into the database.

 

Application.SiteSettingRead (sSectionName as String, sKeyName as String)

Application.SiteSettingWrite (sSectionName as String, sKeyName as String, sKeyValue as String)

Application.SiteSettingDelete (sSectionName as String, sKeyName as String)

 

Application.SystemSettingRead (sSectionName as String, sKeyName as String)

Application.SystemSettingWrite (sSectionName as String, sKeyName as String, sKeyValue as String)

Application.SystemSettingDelete (sSectionName as String, sKeyName as String)

 

Application.UserSettingRead (sUserName as String, sSectionName as String, sKeyName as String)

Application.UserSettingWrite (sUserName as String, sSectionName as String, sKeyName as String, sKeyValue as String)

Application.UserSettingDelete (sUserName as String, sSectionName as String, sKeyName as String, sKeyValue as String)