Converting to MoneyWorks

Converting to MoneyWorks is not hard, but it does need to be done correctly. In essence you want a snapshot of your existing business at a point in time, and it is this snapshot that you take into MoneyWorks. If you are a new business with no history, this is almost trivial. But if you are switching from another system, it is slightly more complicated. The hardest bit can be getting the appropriate data for the snapshot out of your legacy system.

The first thing to do is to decide on a swap-over date. The end of the financial year is often good (because you have to have that snapshot for your end-of-year financials), but in fact you can switch over at any point, normally the end of a trading month. In fact given that there are often other issues that you need to address at year-end, changing part way through a year can be simpler. If you are not on a monthly GST/VAT/HST/Tax cycle, then it is a good idea to coordinate the swap-over with the end of your tax cycle. Note however that it is quite feasible (and not that uncommon) for users to switch mid month — the steps are exactly the same.

The aim is to ensure that closing balances from the old system match the opening balances in MoneyWorks. This is for both the general ledger and things like receivables, payables, inventory levels and valuations. If your old system is in a real mess with unreliable values, then you might just want to start afresh, but you will need to account for the differences to keep the tax people happy, so you should talk to your accountant about this.

What you need from your old system

  • Your customer and supplier details, and their balances as at the swap-over date
  • If you sell items, your item list and pricing
  • If you run inventory, your stock count and value
  • If you do manufacturing, your bills of material
  • A list of your unpresented payments and receipts
  • If you do order processing, your outstanding orders and quotes
  • Your general ledger accounts list and balances

How and if and in what form you can extract this information depends entirely on your existing system (and in most cases we can’t help you). But assuming you can get the information out, and from some “accounting systems” that is by no means a given), here’s what you need do.

Customer/Supplier information and balances

Your customer and supplier list (names, addresses etc) probably form the bulk of your data. In the absolute worst case scenario, if you are moving from a really decrepit system, you might have to print this out and rekey it into MoneyWorks. Hopefully though you will be able to export it and get it into a spreadsheet, where you can manipulate it and then import or just paste into MoneyWorks.

Most accounting systems (and MoneyWorks is no exception) require a code to uniquely identify a customer or supplier. If you are using one that doesn’t (and MYOB is one, which is one reason why MYOB users get so many duplicated customer entries), you can define a column in your spreadsheet and enter your code, or have MoneyWorks generate one automatically when you import the data.

In terms of your spreadsheet, it should be well formed (i.e. the same sort of data in every column and every row, with no gaps or report column headings appearing part way through the rows). In effect you need a column per datum (e.g. customer name, customer address line 1, customer postcode, and so on), and a row per record (so each customer is contained within one row).

Because of timing differences, you might not have the customer and supplier balances available when you set up the customer/supplier list in MoneyWorks. It is a good idea to get the customer/supplier list into MoneyWorks before the swap-over date, but you won’t know your customer/supplier balances until some time later. The balances need to be entered as invoices (check the Getting Started section of the MoneyWorks Manual for reasons for this).

If you can export your receivables/payables data as a report (for example, an Aged Receivables report), then you should be able to that information into MoneyWorks using the free OpenARAP script.

Product/Item Information

Your product list (if you have one, not everyone deals with products) can also be substantial; tradesmen for example routinely deal with over 50,000 items. Hopefully you can export it from your old system and get it into a spreadsheet, where once again you can manipulate it and then import (or copy/paste) into MoneyWorks.

If you are running inventory, then you need to bring the inventory counts and valuations as recorded in your old system into MoneyWorks. It may not be possible to export this information directly, but you should be able to run some sort of stock valuation report. If you can get the information out in a structured form, you should be able to get the product details, stock count and value into MoneyWorks using the free OpenStock script.

Bills of Material

Your bill of materials is essentially a list of components and quantities (including potentially labour) that are used to assemble/manufacture an item. If you have this list, you can use this handy script to import it into MoneyWorks (after the product information has been imported).

Unpresented items

These are cheques you have sent that have not yet been cleared by the bank (normally because the recipient hasn’t got around to banking it), plus any funds that you have received that you haven’t got around to banking. These need to be entered in part because at some point they will be presented, and its easier to have them there ready to tick off, but also for accounting reasons. These unpresented items are coded differently to normally deposits, as outlined in the Getting Started section of the MoneyWorks Manual.

Outstanding Orders and Quotes

If you have any outstanding orders or quotes, you will need these in MoneyWorks so they can be followed up. Although you can import these, it is probably easier just to re-key them into MoneyWorks.

General Ledger Accounts and Balances

The chart of accounts and general ledger is the heart of any accounting system. MoneyWorks has a very powerful, free-form chart of accounts structure, so you can probably just use whatever your coding structure was in your old system (or you might just adopt one of the built-in templates that are in MoneyWorks). If you can export your accounts list from your old system, you can import it into MoneyWorks, but it does need to be in a specific structure (described in the Exporting and Importing chapter of the MoneyWorks Manual), so you will have to massage it in a spreadsheet.

The actual general ledger balances as at the swap over date might not be available for some time, especially if you are waiting for the final year-end results from your accountant. This doesn’t matter, as you can enter them months or even years later. It is normally easiest just to journal these in—again this is covered in the Getting Started section of the manual.


In summary, conversion is not hard but you do need to be methodical and well organised. A lot depends on the quality and accessibility of the data in your old accounting system. If you have some skills with manipulating data in a spreadsheet, that can be helpful. Also remember that you can get your accountant or a MoneyWorks consultant to assist.

Posted in FAQ, File Conversion, Resources | Comments Off on Converting to MoneyWorks

Change History for 7.2

MoneyWorks 7.2 March 2015

All

  • Fixed crash caused by long analysis filenames.
  • Housekeeping Navigator panel now has a heading for the data section.
  • Updated BAS guide for Australia (for 49% tax withheld).
  • Transaction.Flag is now included in fulltext search.
  • Bank account next payment reference number now enforces field length on entry.
  • Updated 1099 Form: incorrect instructions on form.
  • Updated Trial Balance report: Not printing detail.description correctly.

Gold

  • Changing view in Jobsheet list now clears the search box.
  • Exporting item records: Buy price field is now actual last buy price (used to be base currency stock unit cost price).
  • New script function ImportImage(tablename, key, path)
    • tablename is “transaction” or “product”
    • key is sequencenumber for a transaction or product code for a product
    • path is the filesystem path to the image file to import and attach to the record
  • Authenticate(user, password, privilege) function now tests privileges for the requested user, rather than the currently logged-in user.
  • Deposits on Order: fixed a rounding issue.
  • Fixed Debtor Terms display (if added via custom column) in Names list (was not displaying as signed on high latency connection).
  • Batch Creditor Payments: Fixed Outstanding column display on high latency connection.
  • Updated Job Detailed report.
  • Updated Reorder list report.
  • MWScript: Fixed crash on reference to uninstantiated array.
  • MWScript: Fixed crash when executing DoForm() followed by External().
  • Sanitise filenames for temp files that use window title as a base (caused, e.g., print to Excel to fail for windows with a script indicator in title)..
  • Find related Job from Accounts list: fixed crash.
  • Deleting departmentalised account: merge window on Windows now shows department options.

Datacentre

  • Additional MoneyWorks Now™ support.
  • Upload All plugins no longer removes the Pictures folders on the server.
Posted in Change History | Comments Off on Change History for 7.2

What’s with the blurry display on my Retina Macbook Pro?

MoneyWorks 7.2 and earlier did not support “Retina” display mode on the Mac.

For retina text rendering, please update to MoneyWorks 7.3 or later.

Also, for best results, make sure that your Mac is set to its native display resolution (“Best for Retina Display”) rather than one of the “scaled” modes.

Posted in FAQ | Comments Off on What’s with the blurry display on my Retina Macbook Pro?

Change History for 7.1.9

December 2014

  • Datacentre: Fix race condition in temp file creation (Windows)
  • Cosmetic fix in Period maint dialog
  • Datacentre: Sales Enquiry Value column no longer includes GST when enquiry runs on server
  • Updated BAS Guide (Aus)
  • Fix possible circumvention of Select Filters privilege in choices
  • Datacentre: Serverside Import on Mac: Error condition is now returned from AppleEvent if a data error occurs
  • Datacentre: Colour now shows in Choices windows on high latency networks
  • Outstanding Column in Payables/Receivables: fixed decimal display
  • Windows: Allow files to grow beyond 2GB
  • Mac: fix SMTP with SSL on Yosemite
  • Report editor: parts with breakspecs now display as such (v7.0 regression)
  • Applescript do report to pd: fixed
Posted in Change History | Comments Off on Change History for 7.1.9

How can I send emails via Office365’s SMTP server?

It is possible to email directly via mail server from MoneyWorks using SMTP for Office365.

Using OAuth2 to authenticate

As of 16 September 2024, you must use OAUTH2 login for Microsoft’s public mail servers (password authentication will not work). To use OAuth2, you will need MoneyWorks 9.1.9 or later.

You should also make sure that SMTP AUTH is not disabled on your Microsoft account (it may be disabled by default for some newer accounts). See Enable or disable authenticated client SMTP submission (SMTP AUTH) in Exchange Online

Once you know that you have enabled SMTP on your Microsoft account, in MoneyWorks:

Go to Edit > MoneyWorks Preferences > Emailing

SMTP information is as follows:

  • SMTP Server: smtp.office365.com
  • Authentication method: OAuth2

Enter your Office365 mail username, then click Authorise…. This will open the Microsoft login page for you to authorise MoneyWorks to send mail from your account.

After authorising, you can click Test to try sending a test email to yourself.

Troubleshooting:

If no connection can be made to the default SMTP port (25) due to local network policy/firewall, you may need to use:

  • SMTP Server: smtp.office365.com:587

Debug mode

If you need to troubleshoot connection problems, you can hold down the Shift key when clicking Test. This will log the entire conversation with the SMTP server and display it in the log file. You can use this information when contacting your email server administrator or provider to find out what is wrong with the server or your mail account. Most problems around Microsoft mail servers will be to do with having standards-based mail transfer disabled for the account.

Posted in FAQ | Comments Off on How can I send emails via Office365’s SMTP server?

Change History for 7.1.8

November 2014

Performance enhancement

  • Much faster data importing with Datacentre server on high latency network.

Other changes/features

  • Tax code popups are alphabetical.
  • Tax code override popup for Names now displays full tax rate names.
  • Windows version now includes support for SMTP servers that require encryption (sendEmail tool included in install).

Bug fixes

  • Fixed encoding glitch with some importing error messages.
  • REST: Don’t return a 401 for document requests with credentials in URL.
  • Displaying command-key equivalents (by holding down the command key) for controls with very long names no longer crashes.
  • Fix a potential crash on startup (TraverseFolder).
  • Increased the file open retry period for Windows Datacentre for better behaviour when reopening a document that has just closed down.
  • Fixed display of Outstanding column in Receivables/Payables on high latency network with Datacentre.
  • Fixed privileges on Aged Receivables reports.
  • Fixed a DOS vulnerability in the SSL handshake (Datacentre).
  • Fixed Entourage/Outlook mailing support (broken in 7.1.7). (Mac).
  • Made importing of transaction/product images more resilient to corrupt image files.
  • Fixed a potential crash when testing SMTP settings.
  • Fixed a problem where MoneyWorks Now usernames were being truncated at 31 characters.
Posted in Change History | Comments Off on Change History for 7.1.8

Change History for 7.1.7

17 Oct 2014

  • Fixed a crash when choosing an overpayment to allocate when on a high latency connection to a Datacentre server.
  • Fixed the limitation on total custom column calculation length when on a high latency connection to a Datacentre server.
  • Updated the applescript glue for talking to Apple Mail.
  • Fixed the backup location on Datacentre (backups were going to Archives directory.
  • Save a local backup now updates the backup time on navigator.
  • Better handling of unicode text and hyphens when emailing via SMTP.
  • Cumulative P&L for range: Fixed spurious lines with zero in them.
  • CashFlow Report: Now works for locales that use something other than dot for decimal point.
  • Find no longer parses the search text to a date unless it is a date. This could add spurious results to the search.
Posted in Change History | Comments Off on Change History for 7.1.7

I just installed Yosemite on my Mac and now when I send emails from MoneyWorks, the attachment is missing

This seems to be a bug in Apple’s sandboxing scheme and/or Apple Mail. The good news is that it only seems to fail the first time you use Mail after updating the OS. To fix the problem, quit from Mail and start it again. The attachments should now work.

Posted in FAQ | Comments Off on I just installed Yosemite on my Mac and now when I send emails from MoneyWorks, the attachment is missing

Why are my reports getting truncated (short pages or missing pages)?

This can happen if your file was created on MoneyWorks 6 or earlier and for some (unknown) reason, the automatic transcoding of the text in the file was not completed when it was upgraded to v7.

Another sign of this problem will be error messages in the log file of the form [ERROR] text not utf8:

Solution

This problem can be resolved by rerunning the text encoding conversion. To do this:

  1. Open the file in single user mode (if it is in a Datacentre server, make sure everyone is logged out and the file has been closed, then open the file directly in MoneyWorks Gold using Open Other…).
  2. If on MoneyWorks Gold, make sure that the file does not have Gold sharing turned on (looking in File ➝ Sharing and Users: if the Share “…” on the network checkbox is on, turn it off, close the file and open it again (this will make the conversion proceed much much faster).
  3. Go to File ➝ Diagnostics.
  4. Click the gearwheel button and choose Convert to UTF8. The entire database will be checked for text that is not in the correct encoding. Any such text will be assumed to be in the native encoding of the platform you are running on (MacRoman or WinLatin). It will be transcoded from that encoding to Unicode UTF-8.
  5. If your period names contain accented characters, go to Show -> Period Names, retype any period names with accented characters and click OK (actually making any change should be sufficient to store the names in unicode).
Posted in FAQ | Comments Off on Why are my reports getting truncated (short pages or missing pages)?

Change History for 7.1.6

24 Sept 2014 — these change notes apply primarily to MoneyWorks Datacentre and MoneyWorks Gold, but changes to non-product-specific features will also apply to Express and Cashbook.

7.1.6 brings some more significant performance enhancements to Datacentre server and MoneyWorks Now clients accessing the server over the Internet or other high latency network connection.

Note: due to changes in the network protocol, MoneyWorks Gold 7.1.6 will not log in to an older server. Be sure to update servers first.

Datacentre server performance improvements for high latency network connections

  • Faster rendering of list views, most noticeable with lists that have standard or custom calculated columns that look up data from other tables (e.g. the Debtor list does this to display the overpayment indicator; and of course the Detail Lines list).
  • Sales Enquiries for ranges of Products and Customers are now much faster (3-50x in testing).
  • Sum Selection is much faster for transactions, orders, and names.
  • Increased cache sizes to better accommodate very large transactions (Sales Orders up to 600 lines now load much faster).
  • Support for running Chain Reports on the server (The component reports must all be preloaded on the server—use Upload All). This means chain reports can run at full speed for internet clients. Chain reports will also now load any scripts for subreports when running locally in Separate Reports mode, but be aware that using this facility is limited by the fact that custom control settings cannot be passed to subreports.
  • Loading a saved bank reconciliation is faster.

Other performance improvements

  • By popular demand, the non-customisable but speedier version of the Aged Receivables/Aged Payables report from v6 is now accessible again. With Datacentre this will now run on the server, so will be faster than ever. This mode has been built in to the regular reports and can be activated with the following combination of settings: Age By = Period, Show Tax = off, Omit Zero Balances = on, Highlighted Only = off, By Currency = off, Subtotal = None, Use Built-in Mode = on.

New features

  • Load Bank Statement now supports foreign currency bank accounts.
  • Added a backup command to the command line tool. See the manual/usage page for details.
  • Calculated columns in the Detail Lines list may access transaction fields without recourse to the Lookup function.
  • Added GetTaxRate(code, date) function.
  • Export command has XML option for Transaction, Items, Names, Jobs, Job Sheet Entries.
  • Server details for MoneyWorks Now documents can now be seen by holding down Cmd/Ctrl when selecting the doc in the login list.

Behaviour changes

  • If you leave your data file open overnight without having saved during the day, or you cause a Datacentre server to never be able to close the datafile (by, e.g. querying it constantly every minute, 24/7), MoneyWorks will now automatically force a save at approximately 11pm (server time).
  • The behaviour of some intrinsic functions and of calculated columns has changed very slightly. This may affect existing forms, reports, or custom column calculations that rely on the previous behaviour.
    • If NumToText is passed a parameter that is already text, it is now parsed to a number and reformatted in the requested format. Previously the text would pass through with its original format. A side effect of this is that NumToText(“blah”) now returns “0.00”, not “blah”.
    • If DateToText is passed a parameter that is already text, it is now parsed to a date and reformatted in the requested format. Previously the text would pass through.
    • TextToDate can now parse a YYYYMMDDHHMMSS string. The resulting “date” will include the specified time.
  • The privileges for Name and Product Sales/Purchase enquiries have been renamed, which may affect existing privilege controls in reports and uses of the Allowed() function where these privileges are referred to by name. Please update your reports or scripts if you are testing these privileges in them.
  • Datacentre backups are now performed asynchronously by a read-only backup process. The document becomes available for access (reopen) almost immediately after an idle close, while the backup is still being done. This should eliminate the “permissions error” window that used to happen for 5-30 seconds on document close during which reopen requests and REST requests for the document would fail and need to be reissued.

Bug fixes

  • Fixed bug in the form pagination that could cause the Last Page Only visibility attribute not to work for forms printed by a network client.
  • Error logging of XML was sometimes failing with a permissions error: fixed.
  • Windows version is now applying half-even rounding again.
  • Select Filter Privilege no longer throws spurious privilege errors in Navigator.
  • REST 401 response was failing to provide WWW-Authenticate headers in ASP mode.
  • Account Enquiry “Include Unposted” no longer puts the internal serverside report into the Reports menu as the last report printed.
  • Fixed a crash in report writer when report author does not have privilege specified as a requirement in the report settings.
  • A broken client connection while running a serverside report no longer escapes stale client detection.
  • Fixed a potential crash when a Sales Enquiry for a range of names is interrupted by clicking Stop.
  • Removed extraneous Find Advanced option from Item Sales Enquiry (Find and Find Advanced are interchangeable now).
  • Fixed standard control parameter setting from REST/CLI (e.g. Show_Departments).
  • Company Logo change is now more reliable on Datacentre (previously, certain graphic formats were not cleared which could cause a replaced logo to “stick”)
  • Mac version now checks for oversized logo graphic before attempting to upload to server.
  • Fixed a crash risk in detail list when transactions are deleted by another user while viewing the details
  • A report script with the same name as a global script will no longer clobber the global script.
  • Fixed the enabling of the MoneyWorks Now login button immediately after a new account password change.
  • Fixed syncing of DI/SO/QU/Job numbers in single-user case.
  • Script deletion now refreshes the script editor sidebar.
  • Fixed a resource leak in Diagnostics.
  • The Linesleft report variable now works when used before any output is generated.
  • Auto allocation 2-way splits now use explicit rounding to ensure the split balances.
  • Importing a text string via Applescript now accepts unicode text.
  • Sending a report to the clipboard (Mac) now provides unicode text.
  • Import error messages are now correctly encoded as utf8.
  • Font loading failure is now reported to the user (in some cases such failure could result in a div by zero crash).
  • Some std Analysis reports were complaining of wanting a signature.
  • Fixed a security vulnerability in moneyworks_daemon.
  • Fixed a problem with Datacentre that could prevent new connections after too many non-SSL connection attempts to a server configured to use SSL.
  • Items sidebar reports renamed so as not to inadvertently load incorrect report
  • Analysis reports now run on server again (bogus period out of range error)
  • MWScript: elevated attribute now remains set after a call to a non-elevated handler.
  • Windows 7 detail entry list now displays properly with 125% font scale
  • Report writer server-side testing of report now properly disables the Refresh icon in Preview
  • Sequence Number recovery after rollback no longer clobbers synced DI/SO/Job numbers with an old job number.
  • OrderShipped field is now updated properly by Goods-before-invoice and deposit allocation.
  • Singapore F5 Report tweaked realised gain/loss calculation.
  • Improved error reporting for XML import of transactions (detail line index now reported).
  • Apply (date) Format is a form no longer sets global short date format format.
  • User2 import via REST/CLI now returns correct created/updated result.
  • CLI/REST xml import duplicate error messages fixed.
  • MoneyWorks Now logins now appear in the Welcome screen Recents list on Windows.
  • Windows REST service now more reliable under high loads.
  • ValidateCell is now called with the correct list/tab name when changing tabs (e.g. from By Item to By Account).
  • Load Bank Statement: when a split transaction is converted to an invoice payment, the split amount now displays correctly.
  • Load Bank Statement: New split rule created on a zero value transaction no longer gets bad split %.
  • Full text search no longer incorrectly matches prefix of search term against shorter indexed fields such as transaction type.
  • Full text search now correctly matches terms on the start of a line in a multiline address.
  • Fixed overly long Malaysian tax rate names.

Other changes

  • Location for installing Externals has moved to <Application Support/AppData>/Cognito/MoneyWorks Gold/Externals/.
  • Job Code Required is now ignored for Quotes.
  • Foreign currency transactions are now cancelled at the original transactions exchange rate rather than the current system rate. This is to prevent issues with GST/VAT processing. If you need to cancel an invoice at a different rate, do a credit note and contra it.
  • A warning is now issued by the report printing dialog box before running a report locally on a high latency network connection. In this situation, reports should ideally be set to run on the server.
  • Product.Count field may now be imported and used with the Replace command and ReplaceField(). When doing a canonical export (e.g. Copy to clipboard) of products, the Count is exported in the same column that StockOnHand is for inventoried products (these fields are mutually exclusive). If you want to copy/paste inventoried products to become counted products, be sure to clear the StockAcct and inventory flag (#08) when reimporting. You can explicitly set the count flag to have it set even when the imported count is zero (#800000).
  • A reminder message is now issued when foreign currency accounts start to accumulate too much rounding drift. In this situation it is important to update the exchange rate for the currency (which gives MoneyWorks an opportunity to correct any rounding drift).
  • With a Gold Server, editing of scripts is now restricted to the server machine, due to complications with handling edits on clients. Datacentre can handle script editing by any client.
  • Datacentre Console: changing folder passwords no longer triggers a restart of the DC service
  • Changing Company Details now refreshes the navigator so that changes are seen immediately (e.g. updated logo).
  • Updated the Set Rate toolbar icon on Windows.
  • Name.splitAcct1 and splitAcct2 are now explicitly searchable.
  • With MoneyWorks Gold, the Load Bank Statement command can use an external MWScript (located in the standard Scripts/Bank Statement Importers/ folder) to import non-standard bank statement files. The script can use the new function AddStatementTransaction(ref, date, tofrom, desc, amt) to add transactions to the statement coding screen (transactions so added will be autocoded using rules in the usual way). The script will receive the Load message and should call AddStatementTransaction from there to add each transaction.
  • Tweaked the Datacentre console app icon on Mac.
  • The year popup in the report settings dialog now remembers its setting for the session.
  • Fixed a potential multi-second hang when launching on Yosemite.
  • The Use SSL checkbox setting is now remembered across sessions.
  • BuyPriceCurrency can now be imported for existing products.
  • Mac installers are now downloadable as .pkg files instead of .dmg.
  • Report Scripts may now have the same file access privileges as regular scripts provided the report is running locally. Report scripts running on server are sandboxed. In general you should not rely on reading local text files from a report. Reading them from the web server is preferable.
  • For Each part in a report may now read from a secure web server (https).
  • Empty reports now display in preview less confusingly.
  • Modified Mac code signing to conform to Apple’s new requirements for Mavericks 10.9.5 and Yosemite.
  • Improved error handling when communicating with Cognito web services.
  • CLI “list” reports command, now includes checked values for custom controls.
  • Improved the CSS for overscore and underscore in HTML report output.
  • CLI/REST list reports command now includes value of checkboxes/radio buttons stored in report
  • Increased the size of the autocode account fields on Name entry screen.
  • User2 fields may now be modified using the ReplaceField() function.
  • Load Bank Statement will no longer use highlighted code/amount text as match text for a new auto allocation rule.
  • REST: An Authorization header with no realm specifier is now assumed to be for the Datacentre realm if the server has ASP mode enabled.
  • OFX, QIF, QBO files may now be dragged and dropped onto the Load Bank Statement window and also into the Transaction list to invoke Load Bank Statement. In the latter case, no date filtering will take place (likewise no date filtering will take place if the file is dropped on the app icon in the Dock).
  • Load Bank Statement OFX/QBO importing now translates the ampersand entity.
  • REST developers can have all headers logged for debugging purposes (in conjunction with the verbose logging setting) by manually editing the Datacentre conf2 file to set debug: 1
  • Custom date controls in reports are now passed to the server in ISO format for international compatibiity.
  • XML import errors are now logged to progress window.
  • SMTP emailing no longer substitutes user’s email as From field if the SMTP server requires authentication.
  • Added Paste Records command to contextual menu.
  • Change Starts New Seq preference will now ignore a change to a non-numeric reference number.
  • Random() function is now much more random, especially in CLI mode where it was not seeded, and on Windows where the seed was insufficiently random.
  • Improved network latency measuring for better determination of when to use serverside reporting.

Additional changes in 7.1.6r1

  • Applescript importing could hang on Mac. Fixed.
  • Fixed some issues with Trial Balance report: Include unposted was not working in 7.1.6 and certain settings combinations did not work. The Include Unposted issue generally affected any custom report control with the same name as a standard control.
  • Fixed script list handles whihc were not working in 7.1.6 on Windows.
  • MoneyWorks Now account reset link (“forgot?” password) now goes to correct server without redirect.

Additional changes in Datacentre 7.1.6r2

  • Fixed failure to display Debtor/Creditor balances in Names list on Windows clients connecting over a high latency network.
  • Fixed a potential server crash with certain custom column calculations.

Additional changes for Gold/ Datacentre 7.1.6r3

  • Fixed optimised summing of purchase orders on high latency network.
  • Fixed “wrong codepath for base currency” error in bank statement import.
  • Ctrl-C in Console broadcast message dialog no longer sends message (ctrl-c was mapping to Enter)
  • Allow longer username in SMTP authentication.

Additional changes for Gold/ Datacentre 7.1.6r4

  • Fixed incorrect display of some columns in Stock Enquiry with Datacentre and high latency network.
Posted in Change History | Comments Off on Change History for 7.1.6