Addsum web site and general info

Postings here will focus mainly on Advanced Accounting software updates, tips, and related topics. They will also include general comments relating to troubleshooting PC/Windows/network problems and may also include reference to our other software products and projects including any of our various utilities, or to the TAS Premier programming language. We considered setting up separate blogs for different topics so that users/others could subscribe to topics mostly aligned with their interests, but decided that it would be better to keep things simple since some topics cross over into others. We would nonetheless welcome your feedback/input in this regard. Our web site URL is www.addsuminc.com. Call us at 800-648-6258 or 801-277-9240. We also maintain www.advancedaccounting.us so that older Business Tools users in particular have a greater chance to find us. White list noreply@follow.it to ensure you receive notifications once you subscribe.

Wednesday, March 11, 2015

Auto build when transferring a quote

Bill of materials (BOM) is a standard module included within the integrated Advanced Accounting software.   In addition to generating a build  of a finished or assembled product type from within the BOM module, the software has also long supported an "auto[matic] build" feature from within sales order entry whereby a build could be initiated right at the point of entering a line item.   For items that may involve little or no assembly such as kits that may have already been packaged (or that can be quickly assembled as part of the shipping process) but not yet formally built in the accounting system, this provides a quick and easy way to create units on hand that then can be reserved via the sales order module, and placed on a sales order for very fast order processing.

Recently a customer who is a heavy user of the BOM module and who also most commonly builds most of its items from "auto builds" (when entering sales orders) also wanted the ability to initiate a build right at the point of transferring a quote from a sales order.   This capability now exists and will be available in future releases.   This ability is also sometimes referred to as "building on the fly."

Just as when auto building from a sales order line, when building at the point of transferring a quote, the user has the ability to print a build order, and when building, the actual amounts used can be adjusted. 

While adding this capability into the quotes module might have on the surface seemed simple in just moving existing sales order entry logic into the quote transfer program, in fact it turned out to be extremely complex due to the many subtle differences.   The primary reason for the additional complexity relates to the fact that the auto build is being initiated in a very different overall place since the user is not interacting with a single line item entry when transferring a quote, and the decision logic that then occurs has many non-obvious implications.

Further the user may at first to decide to build, but then either not build all of the units or build a lower number.   And there are different circumstances involving whether the full quantity can be built or a smaller number (or none at all).

In addition to the logic issues involving when transferring a quote and in the extensive testing that we conducted over a month's time, we added a capability that the availability logic had never supported:  the ability to tell the user how many units of an item could be built  if all of the units being ordered could not be built.   We found this necessary just to be able to more quickly determine whether logic changes were working; and it should be highly beneficial to all BOM module users.

Another issue related to the fact that the user needed much more "messaging" information. When prompted about building an a item in sales order entry, the user would know exactly what item the message was referring to since they were working with it on-screen.   This is not true however when transferring an entire quote to a sales order where the user is not directly at that point interacting with line items and the line items normally do not even need to be displayed.

Advanced Accounting is multi-location driven in terms of its inventory unit processing.  Builds therefore occur at a "location" (which can simply a "blank" location or a named location; if necessary items can be separately transferred from one location to another when the finished item is being built).   When all of the units cannot be built at the time of sales order entry or when being transferred to a quote, the user will now receive the prompt:

"Would you like to determine what the maximum number of units are that can be built at this location?"

If responded to in the affirmative, then the program will make that determination and then allow the user to build that quantity (with the remainder, if all or some successuflly built, being placed on backorder).

The "auto build" flag, as in sales order entry, is also a trigger for initiating a build from a quote.  Users who never want to auto build therefore can specify that they do not want to be prompted to build in this fashion if desired.   This option is established in BM-I  Set configuration.   Items that are not available as units on hand at the location will then simply be placed on the sales order as units on backorder.

The new "maximum number that can be built" calculation functionality will benefit both the "auto build" and normal build/unbuild processes alike:


Auto build, i.e. builds initiated from:

SO-A Enter/Change Sales Orders (which can also be reached in other ways)
QC-B Transfer Quotes (which can also be initiated after saving a quote)


All builds:

BM-E  Print To-Build order
BM-F  Build/un-build process




Many users make heavy use of Advanced Accounting's BOM or BM module (and therefore ultimately BM-F).  Consequently, the BM-F build program has received considerable attention by us over the years.  We have been making programming updates to the standard BOM build/unbuild program since 1997 (after working with its earlier incarnations from the early 90's in even older versions).  In 2007 we first converted it to a graphical (true Windows form-based) program.  Extensive changes were made in 2009 to deal with negative unit and average costing problems that prior attempts had not fully resolved, and those efforts have proven to be quite successful.   In 2013, the entire recursive logic routine was re-examined and ultimately significant changes made to solve a resource allocation problem with builds deeper than two or three levels (builds can be up to nine levels deep) and a large amount of testing occurred with an end user's data involving complex  and deeply nested assemblies.  In the process of the 2013 work, significant user status bar information tracking each step in the build process was added since it was essential for troubleshooting, and that work remains in the program as a helpful aid for both us and the end user.





*The JC (job cost), BOM (bill of material) and POS (point of sale) were originally add-on modules starting with version 4.03 and in later versions 5.0, 5.1, 6.0, 6.1 and currently 7i included as standard.

Wednesday, February 11, 2015

Microsoft automatic security update causes font degradation

Microsoft kernel mode driver security update 3013455 released on February 10, 2015 has caused the quality of text to degrade or fonts to become corrupt on some systems.   Systems impacted include Windows Server 2003 SP2, Server 2008 SP2 and Vista SP2.   There is an independent report that XP may also be affected.

Users with automatic updates enabled will likely already have this update.

The solution is to uninstall the update from the control panel (add/remove programs).    If you have enabled automatic updates, this update will still attempted to be installed, so if you have an afflicted system, you will have to start to control which updates are installed and avoid installing this one until/unless Microsoft finds a resolution (as of February 13 that was still not the case).

A site providing early information about the problem:

http://windowsitpro.com/msrc/patch-tuesday-font-corruption-kb3013455

Microsoft's description of the security update:

https://support.microsoft.com/kb/3013455

One report indicated that only the Courier New font was impacted, but in fact, Arial and other fonts have also been impacted by this update.   As of early morning on February 11, 2015, one of our users running Windows 2003 SP2 reported experiencing this issue.   It did not make their system unusable, but it caused text to be significantly less readable (all characters lighter overall, each character with broken connecting lines and not evenly rounded).    The same user had the problem recur 24 hours later because of having automatic updates enabled.

In a Terminal Services environment, users logging into an afflicted server via remote desktop (RDP) may experience the problem, whereas directly connected user clients that either do not have the update or are running a non-impacted operating system may not experience the issue.

You can determine what Windows updates may be installed on your system by clicking on Start and then choose Search.  Search for Windows Update.   When Windows Update is found, click on Stop.   There is a WindowsUpdate.log file than can be browsed and towards the end might show:


WindowsUpdate.log example:

2015-02-10 15:13:46:843  828 3848 Agent   *   Title = Security Update for Windows Server 2003 (KB3013455)

To fully review your update history, click on Windows Update in the search list and then click on the Review your update history option which might then look as follows:












Monday, February 2, 2015

Addsum Btrieve 6.15 setup utility updated and now available to third parties

Since 2004, we have provided a utility to assist end users in configuring the Btrieve 6.15 microkernel record manager engine in the context of providing support to end users of Advanced Accounting and TAS Professional originally released by Business Tools, Inc.  Business Tools had an unlimited distribution license for the Btrieve 6.15 engine.

Recently we have made additional enhancements to the utility which previously had not been changed since 2013 after periodic updates since its initial release by us.   This update will be made available to our accounting software in a future release.  We are now making the utility available for any third party use (since the configuration utility is not specific to any particular application).

A screen shot of the latest version of our setup utility as of end of January 2015 is contained below.





The latest version of the utility has been tested under XP Pro, Windows 7, Windows 8 and equivalent server versions, i.e. 2003 Server, 2008 Server and 2012 Server.

The Btrieve 6.15 setup utility can be acquired for a nominal amount at:

http://www.addsuminc.com/btr615setup.html


Background information: 

The Btrieve 6.15 engine was published by Btrieve Technologies, Inc. (later Pervasive and now Actian Pervasive).  It has not been updated nor supported by Pervasive since 1999.  This engine however continues to be operational under all 32-bit and 64-bit operating systems released by Microsoft since that time.

Btrieve 6.15 is a very compact workgroup engine that employs page locking (similar in terms of functionality to Microsoft Access, although it typically outperforms MS Access).   Many software publishers have over the users distributed applications using the Btrieve record manager engine.   Peachtree for many years for example included Btrieve 6.15 with their accounting software installations.

The Btrieve 6.15 engine did not dynamically establish its settings as did the later versions renamed to be Pervasive.   Therefore a utility that established those settings especially in a multi-user enviroment is needed.

Business Tools provided a barebones tool named BTRVINSTL.EXE with the initial release of TAS Professional 6.  This tool however did not establish all of the appropriate settings that were needed and that became apparent only after several years of end user support, and after further research on our part in migrating users from older versions of Business Tools software.   This then led to the development of our own tool, BTRSETUP.EXE, the earliest version of which was released only to users we supported in 2004.

Because the Btrieve 6.15 engine was designed to read values from HKEY_LOCAL_MACHINE, a local user needs more user rights than ordinarily might be desirable.  This was less of a problem in earlier eras where security rights were somewhat less of an issue than they are today.  With the newer security features added first with Vista and continuing with Windows 7 and Windows 8, some default and other settings that were provided by the original publisher of the Btrieve 6.15 engine are now in conflict and will even prevent the software from loading.   (In that regard, see also our related blog post entitled Pervasive/Btrieve status (error) code 20).   Our utility as now also recently updated can help prevent or solve some of those types of problems.   More technical information is contained on the btr615setup.html page referenced above.















Friday, January 23, 2015

Quote message line enhancements (in Advanced Accounting)

Based on an end user request, we have added the ability for some basic formatting options of message lines when entering and printing a quote from Advanced Accounting 7i which will be available in the next release.   As a result, two new group boxes in the line item entry section have been added as outlined below.


QC-A Quote line item entry

The report output font size normally is 9pt and the larger T size will cause the message line output to instead be in 14pt.   Further, for both the regular and larger font sizes, formatting options can be selected that include bold (B), underlining (U), or both bold and underlined (BU).

When output, the body of the quote report output appears as follows:


QC quote output (total differs from image above due to changes made to the first line item prior to printing



When the larger text option is selected, the message line text is aligned with the product code column rather than with the product description to allow for the additional space required by the increased font size.   When sent to a printer, the output normally will match the preview as above.   Conversions to PDF files (available directly within the software and which automatically occurs when choosing to e-mail a quote), can result in slight differences.  For example, if the underline option is chosen, the underline may extend all the way to the right and not just under the text.

Message lines can be "attached" to notes rather than just single text strings.  (This is true also in connection with purchase orders and sales orders/invoices).   When these new formatting options are applied, notes attached to message lines will be formatted accordingly (see image above for an example of a note that has been selected to be in a larger text size and in bold).    A better way to describe this kind of message line might be a message line note, or a message line that is "transformed" to a free-standing note that is not attached to product/item code (notes that instead are truly "attached" to product code lines will continue to print as they have in the past and are unchanged).

These new options allow the user to emphasize certain conditions or contingencies that often apply when providing estimates.    These same options could be added to sales orders/invoices and to purchase orders in the future depending on end user interest.




















Wednesday, January 21, 2015

AccuWage Submitter EIN and Employer/Agent EIN matches alert


When testing 2014 electronic file W-2 submissions, the SSA's AccuWage software may provide this alert:





This is a non-critical alert or warning message.

If you are submitting a file on behalf of your own company, then the Submitter EIN and Employer/Agent EIN are in fact going to be the same.   Nothing in that event is wrong.

In an era where employers are being encouraged to upload their information electronically, it is somewhat peculiar for end users to encounter this sort of warning which presumably is designed more to help tax practitioners catch mistakes prior to submitting files on behalf of others.


Wednesday, December 24, 2014

Actian releases Pervasive 12: first look

The latest version of Pervasive (informally "Btrieve") was released on or about December 17, 2014.

Btrieve/Pervasive record manager engines have been the data interface backbone of choice for both Advanced Accounting (and earlier "Books") as well as versions of the TAS 4GL integrated development environment since the late 1980's. A number of other accounting software and multi-user database systems also continue to rely on the speed and robustness provided by these engines, a key feature of which has been expandability and true client-server support.

Version 11 was released in September of 2010 and remains in widespread use.

Important note:  Pervasive v12 will no longer support XP Pro nor Windows 2003 Server.

Actian now owns Pervasive and here is their product availability notice:



FAQ's:



Download page:

http://www.pervasive.com/database/Home/Products/PSQLv12.aspx

Hardware requirements are the same for both versions 11 and 12.

It is expected that product support and updates for version 11 will continue until June 30, 2015.

There is currently no rush for existing users to migrate to version 12.  It will primarily be of interest for new users, users who are on older versions and especially pre-v10 systems who will now likely want to migrate to v12 rather than v11, and users who need to expand their license counts.

One feature of the new version is an interesting defragmenter that can be run while the files are open (see screen shot at end).

Other currently outlined features may be of little to no benefit for existing v11 users.

First look:

As an initial test, we installed the workgroup engine on a desktop Windows 7 PC (32-bit O/S, SP1) and also on an ASUS Transformer Book running Windows 8.1 (32-bit version).     Both installations went very smoothly, and with no issues.  The workgroup engine can be installed as an application or as a service.  Most users will want to install as a service.  We installed one as a service, and one as an application.





In both cases (and has been our experience with essentially all prior Pervasive installations since version 7), both PC's had to be re-booted before our test applications would run (the installation does not tell the end user however that a re-boot is necessary, but this is something we have routinely advised).    After re-booting and after some initial testing with two completely different applications running on each of the PC's, they both appear to be working exactly as expected and as they have with prior versions of Pervasive/Btrieve.





On one of the test PC's, we noticed something different than in the past:  the presence of an older Btrieve 6.15 engine in the application folder did not create a problem with the Pervasive 12 engine running.  And in fact, we were able to run one application using Pervasive v12 and another application using Btrieve 6.15 at the same time.  This previously has not been possible.

The installation default group now is Actian PSQL 12 rather than Pervasive.

Installed Pervasive tools such as the License Administrator, Gateway Locator and Rebuild look substantially similar as does the Pervasive Control Center (PCC).  User data files will not have to be rebuilt, and the "highest" Pervasive internal file format remains at 9.5 as it has since the Pervasive 9.x series.

Unfortunately Pervasive v12 continues to by default enable limiting data file sizes to 2GB before they "segment" which was a limitation imposed by Windows NT but which has not been an issue in newer Windows operating systems.  Segmented data files cause various potential problems including how multi-company file naming extensions are deployed within TAS-based systems as well as can create potential backup, data integrity, reindex,  manual file deletion/renaming and other file handling issues, and therefore is not supported.   Pervasive users will need to uncheck this option so that segmentation never occurs (and this needs to be done in the event of a re-installation as well).

 Pervasive v12 - uncheck Limit segment size to 2GB
(same action needs to be taken prior versions)


And, all supported protocols continue to be enabled by default in version 12.  Most users only need TCP/IP and non-used protocols should be removed by unchecking them (see below).

Pervasive v12 - removed unneeded communication protocols
(same as in prior versions)



Some final random thoughts:

We would be hopeful that the addition of the defragmenter feature might also mean that status code 46 problems resulting from access of the files from outside of Pervasive's handling might also be reduced or eliminated, but we suspect it will not.  The defragmenter however may prove to be a very useful diagnostics and general analysis tool.

With server version purchases, Actian is offering for free (but as a separate download) its "Actian Analytics Platform for PSQL."   This in part shows the influence of the new product owner and future directions that the product might take.  This tool looks interesting as well, but is not something we have yet looked at.

The installer update which automatically detects the bitness of client operating systems could backfire if installation and connectivity problems related to the 64-bit Pervasive client engine continues to occur with 64-bit client operating systems.   With v11, users have had more success installing 32-bit clients on client-server systems even if the server install was 64-bit and even though the clients are running 64-bit operating systems.   If this remains the case and there is no way to install 32-bit components on a 64-bit PC, then this will be a potential problem.

The legacy 32-bit Btrieve 6.15 continues to work for older users who already had this engine on even Windows 8 systems (32-bit and 64-bit).   Compatibility issues with this old version (despite its limitations, and despite not having been officially supported by Pervasive since the late 1990's) remains far fewer than with any subsequent version.  And contrary to what might have been published elsewhere, it does run on 64-bit Windows 7 or Windows 8.   It is not however suited for more than a relatively few simultaneous uses and does not provide client-server support, and it requires higher local user privileges than the newer engine.  Its tiny footprint and its ability to "keep on ticking" however is quite admirable.

In any event, it appears that Pervasive v12 should be a smooth migration for prior Pervasive users; and for new users, preliminary indications are that it is a solid product.


New PSQL12 Defragmenter tool






















Tuesday, December 16, 2014

MSN messenger service going the way of the Dodo

Since the April 2013 retirement of  MSN messenger, also referred to as the Microsoft Messenger or as the Windows Live messenger (see announcement at http://windows.microsoft.com/en-us/messenger/messenger-to-skype), it is remarkable that problems with MSN messenger live.com accounts have not occurred in a more widespread fashion sooner than now.

But sometime just in the past ten days or so, we noticed that our live.com account was no longer connecting via Zoho Chat.   We thought that maybe something had changed there or that we had installed something that was preventing the connection.  In Zoho Chat, it simply attempts to connect with the message 'Connecting . . . ' which remains on screen indefinitely with no error message or any indication as to what the issue is, nor any indication of a sign-in failure.





We had no difficulties logging into live.com which simply accesses browser-based mail.   We tried disabling/enabling the Zoho Chat settings with no change.

Proceeding to reinstall the latest version of a desktop instant messaging (IM) client we used to use, Pidgin, we still could not connect to the live.com account getting sometimes a "connection refused by server" response.

Investigating further, we finally stumbled on these helpful postings:

https://messengergeek.wordpress.com/2014/11/12/most-third-party-messenger-clients-have-gone-offline-temporarily/

and

https://messengergeek.wordpress.com/2014/12/05/microsoft-appears-to-be-pushing-messenger-to-http/

And also:

http://ismsndeadyet.com/

We tried linking a new live.com account using WLM protocol (instead of MSN protocol, and after installing the "msn-pecan" protocol - see first link above for the link and as recommended there) and that did not work, but then noticed the more recent indication that the HTTP method had to also be used.   That also did not seem to work;  we then changed the Server setting per one of the other recommendations to bn1.gateway.messenger.live.com.  The connection still did not at first seem to work, but shortly thereafter, and only after all of the foregoing changes, and for perhaps what will last for only a short period of time, we appear to have our "live.com" connection temporarily back (which we have used solely to communicate with a single customer that historically has used it)!

The MSN messenger service does appear to be on life support.


Postcript:  the day following, a connection via Pidgin could again not be established.  In the intervening period,  Microsoft made a change that required HTTPS that Pidgin does not currently support.  More details.

For connectivity with Pidgin, changing the server (with or without the HTTP method checked) to msn.messengergeek.com did not work for us on the 18th but as of the 19th was working again. But for how long this time?!