No Records exist or match your criteria
Are you missing transactions from your MYOB® company file? Many users routinely use MYOB's Transaction Journal to check for or locate transactions - but when AR2024 responds with 'No Records exist or match your criteria' - the question is 'can you trust AR2024?' Have the transactions really vanished?

The cornerstone of any Accounting Software is 'reliability' - MYOB® used to be the Gold standard, until they released AccountRight Live - initially in 2011 as AR2011, it's latest version is AR2024. Sadly not only does AccountRight Live still have a large number of bugs that MYOB have known about for years, some users continue to experience significant performance issues, and data integrity issues, even with the very latest version - AR2024.

AR2024 cannot cope well with large company files - MYOB staff recommend a company file size be under 300 MB to lessen the impact of performance issues.

Note: The comments below are based on AR2018.4 - we are not sure if this issue has been addressed in the latest version or not.



Just to illustrate one of the things that happens with a larger file, see the images below. We opened a larger file (> 1 GB) in AR2018.4, the current version at the time. The file belongs to a client who complained about performance issues.

The images below show the Tranactions Journal - General Tab. Between 1 July 2010 and 30 June 2017 this file has 20 General Journals, at least one in each financial year. See what AR2018.4 showed when we select 1 July 2010 to 30 June 2017 - please note in all instances after selecting the dates, we clicked the Refresh (F5) button as highlighted in Red.



Let's try reducing the date span by one year, from 1 July 2011, and click Refresh.



Let's try reducing the date span by another year, from 1 July 2012, and click Refresh.



Let's try reducing the date span by another year, from 1 July 2013, and click Refresh.



Let's try reducing the date span by another year, from 1 July 2014, and click Refresh.



Let's try reducing the date span by another year, from 1 July 2015, and click Refresh.



Let's try reducing the date span by another year, from 1 July 2016, and click Refresh. 'Yippee' - finally something appears! - we do actually have transactions in this file, and they have been there all along.



Just to show there were transactions in every year, see what MYOB displays when we select from 1 July 2014 to 30 June 2015, and click Refresh.



These did not display when we selected a date span exceeding 12 months, as you can see in the first 5 images above.



With some files, AR2018.4 shows 'No Records exist or match your criteria' until you reduce the date span to months, so to see all transactions for a full financial year, some users must select one quarter at a time. FYI generating Reports does the same thing and you see a message 'There's no information to display. Try changing the filters and then run the report'. The same applies to the latest version - AR2024 simply cannot cope with larger files.

This illustrates why we are not so keen on AR2024 and advise v19 users to stay on v19 for the foreseeable future. There are alternative ways to comply with Single Touch Payroll, see here for more information.

FGH Tables will continue to support MYOB® beyond Sep 2019, when MYOB Aust ends support - see here.

For those struggling with larger files, see our Purge Service MYOX which managed to reduce this client's file to less than 40% of its original size.

System.OutOfMemoryException is another common error AR2024 has with larger files - see here for more details.