Hi gavin12345
Thanks for your advice. Have since gained a copy of their myob.myo file - it was 1.95 mb long - an optimise reduced it to 495k - there is no perpetual inventory, no multi-currency. There are 2 files, the 2nd one no idea.
So I tried a local server upgrade of the file but after almost 24 hrs - and leaving my laptop going all night it was hung on, or still converting it -checking 'constraints' - so I killed it this morning - no idea whether it was still going - my next try is to purge the file of old data and try again.
I know big myob files may need to be sent into MYOB - but I will try an upload to a licenced 2025.10 - as I have requested the client to expedite getting 2 licences to move forward.
Sometimes uploading and allowing the online system to upgrade can work better. All trial and error - but 1 Mar 25 is just around the corner and we have 2 MS Access databases to re-engineer for API access.
An email stating the move forward facts goes out today and the path forward for API connectivity by 1 Mar 26. (I note your advice with keeping MYOB Enterprise - yes am aware but with this client they are not small but a big business that should have upgraded long ago and ignored advice to - kid gloves removed!!)
Regards The Doc
Hi The_Doc
The long upgrade process is not due to the file size (I take it you meant 1.95 GB reduced to 495 MB on optimise). I have upgraded many files in my time, some well over 490 MB.
The issue is I suspect this file has possibly a large number of payroll categories and or employees and or payroll history. The upgrade process is flawed (poorly coded) and rather than use indexes, the upgrade iterates in a circular fashion through every employee and every payroll category and every pay history record in seemingly endless loops. I had several upgrades that lasted over 24 hours due to this issue. The upgrade ran smoothly only after deleting standard pay records. Upgrade shouldn't take over 2 hrs for a 500 MB file.
Regards
Gavin
