Crossing the (file size) line in MYOB
Posted in blog on Apr 04. Tags: issues, MYOB, recovery
Ever wondered what the maximum file size for a MYOB data file is?

Want to guess? I’m pretty sure it’s somewhere around 2.0Gb myself. Why? Because I have just spent many, many hours optimising a (.MYO) data file to get it back under this magic limit. I can’t say for sure, but if you get a MYOB file to 1,906,528KB you might also run in to this issue.
In fact, please email me if you do, because I would like to have confirmation that it’s not just this particular installation. Here is my “experience”…
The night before: Run the invoice import which uses the ODBC link to insert ~4000 invoices that were generated earlier in the day. These are the monthly invoices for the company. Yes, I have told them (for years) to get a different accounting package.
~8:30am: I get the call that the MYOB file is “not working”. I try to open the file and receive an “Error 1233: -3000 in DMBeginTransaction” message. After a bit of looking around the only posted solution is to optimise the file and hope for the best.
12:03pm: Optimisation has finished and the file has been shrunk to 1,895,424KB. It will open in MYOB again.
~4:00pm: Someone notices that a bunch of recently imported invoices so I kick off the various comparison processes that marks invoices previously thought to have been imported, that are no longer present in the MYOB file, as un-imported. This then kicks off the import process, which starts importing the outstanding invoices.
4:24pm: Auto-import process crashes. All users in that MYOB file also crash.
~4:27pm: We discover the backup process has silently failed two days ago and that the file that was backed up last night was 1,906,528KB in size. There is no backup. The decision to scrap the days transactions is made and I restore the recovered file from 12:03pm.
~4:30pm: I kick of the roll-over process, effectively removing all transactions from the previous financial year. A process that someone “just never got around to doing it”.
7:05pm: Roll-over process completes. File is now EVEN LARGER @ 2,137,120KB. It won’t open – “Error 1233: -3000 in DMBeginTransaction”.
7:12pm: I apprehensively kick off the file optimisation process. It seems to be working.
~8:13pm: Optimisation finished. File is now 1,018,400KB. This might actually work! Missing the invoices still, but now I can re-import them without going over any soft limit.
8:55pm: The import has finished without issue and the MYOB file seems to be fine. Huzzah!
Now the Accounts Department only has to figure out what other transactions from the last couple of days have been wiped out and then they can continue with their week.
NOTE: When optimising huge MYOB files, the optimiser doesn’t seem to be able to calculate the required/free space on the disk correctly. I have been doing all the optimisations on a 50GB drive with upwards of 40GB free space. Each time I have started to optimise a new file (I am using copies, it’s a long process) the optimiser tells me that there is not enough free space. I copy and paste the file back into its folder (making a duplicate with ” – Copy” in the name) and then, suddently, the optimiser will let me process the file. I do not have an explanation for this, but I have noticed this issue for at least the last 3 years.
