Roundtable Software Newsletter #50, August 28, 2007
Want to subscribe to future issues of our newsletter? Click here!
In this issue...
|Patch 32 Released|
|This patch contains minor bug fixes, several enhancements, and new features for use in conjunction with the new Windows version of the software.
Accounts Receivable program 52, Update General Ledger: A new feature has been added whereby you can choose to increment the Document Code on each entry created in General Ledger on an update. This feature was added mainly so that General Ledger deposit entries updated to Bank Reconciliation don't get 'rolled up' into one big transaction. Bank Reconciliation will combine G/L entries that share the same Document Code.
Inventory: Another batch of new fields have been added to various files for new features that will be in the upcoming Windows version of the module. Some minor DOS program changes were made in this connection.
Purchase Orders program 10, Post Items Received: Was not properly updating the Total Cost of a purchase order when deleting receipts.
Point of Sale: A new feature that adds two additional subtotals to Point of Sale invoices has been created. A new prompt has been added to System Defaults that allows you to choose one department that will be subtotaled separately. In addition to this subtotal which is the total for all line items on an invoice that reference that department, an additional subtotal shows the total for all line items not in that department.
Point of Sale: The recent enhancement to deal with longer Windows printer names created some problems in the Point of Sale invoicing and system defaults programs; programs 4, 5, 13 and 50 all have changed to better deal with the longer printer names. Due to lack of space, the size limit in Point of Sale is 55 characters, rather than the 57 characters available elsewhere. If your reports won't print to a specific Windows printer check to make sure your printer name isn't too long.
Point of Sale program 51, Estimate To Invoice: The new feature of transferring estimates to layaways would get fatal errors when trying to create Inventory allocations in some circumstances.
Order Entry program 52, Create Drop Ship POs: When the program created purchase orders it did not fill in the Backorder Quantity field. This allowed Purchase Orders program 53, Purge POs, to purge the purchase orders because it keys on the backordered quantity to determine if there are still items to be received on the POs.
Bank Reconciliation program 1, Gather Transactions: The program would duplicate AP checks that were already gathered if the transaction description in Bank Reconciliation was changed from that brought over originally from Accounts Payable.
Click here to go to our Patches page where you can review the versions changed in this patch and download the patch file.
If you prefer, you can order a replacement CD from your dealer to get all the latest patches and ensure you are up to date.
|UNIX Users: This patch is not available for download from our website. Please contact your dealer to order patch product.|
|We have been further researching the OPLOCKS problem on Windows. This, as you'll recall from previous newsletters, is a 'feature' of all Windows versions that can and does result in trashed data when running multi-user database applications, including RTS-Advantage. Why Microsoft persists in offering this buggy feature we don't know. Apparently slightly faster network data transfer is ranked as too important to let a little problem like trashed databases stand in the way. It is VERY IMPORTANT that you make sure OPLOCKS is turned off in your system if you are running over a network.
In our previous research we had gotten the impression that OPLOCKS needed to be turned off on Windows servers (all versions) and Windows 95/98 clients. Turns out this is not the case. It is important to turn off OPLOCKS not only on all servers, but also on all client machines at least through Windows XP (Vista presents even murkier problems, see below).
In order to turn off OPLOCKS on Windows XP clients and servers, and Windows 2000/2003 servers, go into REGEDIT and find this registry location:
You may or may not find a registry entry titled OplocksDisabled here. If the entry doesn't exist add it as a REG_DWORD type. To turn OPLOCKS off set the value to 1 (meaning disabled).
Microsoft also suggests setting a second registry value in this location:
Edit or create a REG_DWORD entry titled EnableOplocks and set the value to 0, meaning disabled.
Regarding Vista, Microsoft offers only that opportunistic locking cannot be turned off for SMB2 (SMB stands for Server Message Block), whereas it can be for SMB1. We can find no further information. Our best suggestion is to turn OPLOCKS off as for previous versions of Windows and hope for the best. If the system starts giving errors go ahead and turn it back on. We tried it on our Vista test machine and found that the registry did not have a ..\MRXSmb\Parameters location, but it did have the ..\LanmanServer\Parameters location. After turning off OPLOCKS in this location we could see no difference in the way the operating system was functioning (which is good).
For further information about OPLOCKS and the problems it causes please read these Microsoft KnowledgeBase articles:
|Roundtable Software 30831 Cove Road Tavares, FL 32778-5164
(352) 253-9779 FAX: (815) 572-5446
All contents copyright © 2000-2008 Roundtable Software. All rights reserved.