An update went out on July 2 that had a problem for some users. It was missing a file called SYSUSR.dbf. This file was used for a new logging feature implemented previously and why it didn’t cause a problem on earlier releases is a puzzle.

An update did go out on 7/3/19 at 11:00 am PDT that resolved the issue. Of course, if you had the problem, to read this bulletin, you’ve already resolved the problem. Our auto updater added the file if you followed the simple prompts.

Sorry if this caused an inconvenience.

You are used to seeing the notice that your ASW 11 has been updated, but next week you will receive one that is different. Please read this carefully …

When you first see the notice, it will be just like you expect. HOWEVER, it will then tell you the database needs to be updated. It will then ask if everyone is out of ASW. Before saying OK, BE SURE that no one is in the program. It will then want to perform a backup. You get to select where, so just click on the downloads folder on the displayed list. Then when that finishes, it will tell you it is going to update the databases.

There is only one file being updated, but it may be large. It is the parts sold file. So, this could take awhile. Of course, if you use the server ( where the data is stored ) as a workstation, make sure that is the one you first start ASW on that morning, and use it to do this process. This will be the fastest. If you use a dedicated server, then any workstation is ok.

When the update is complete, go under Tools to Index and just reindex the item called Parts Utilized.

This will only need to occur on one machine. Once the database is updated all other machines will simply start as usual.

Again, this might take some time, depending on how fast your computers operate and are connected.

Look for this update on Tuesday morning.