Backup online only - no offline opening - moving forward folks a perspective that may work
Hi Folks
Please read my post - I am not advocating lying down and rolling over - I will not but maybe we can approach these unwanted changes from a different perspective - you say 'accept them' - I say 'yes' but then say MYOB, this is a bad unwanted move - how about giving us some tools, utilities than bridge this gap? .... may be I dream.
Has MYOB asked me to write this - no; has MYOB got in my ear and moved me to the 'dark side' - nope, but as a very, very long term user of Microsoft products and MYOB's I can sometimes, hate and loathe changes, but understand them ..... and, later on perhaps just move with the change.
I am a long-in-the-tooth user ( since 1994), Certified Consultant since 1998 and MYOB partner and an API developer and in that time I have seen so many changes to MYOB's software and Microsoft's operating systems as to be called 'really old'..... hmmm.
I write database products that integrate with MYOB's starship products and I too, have to move these products forward to keep them relevant - these changes are mostly dictated by the operating systems that run them, and in general we are talking Microsoft and Microsoft seldomly listen to anyone crying 'foul' rollback, seldom... I suspect that this change is just part of this spider web.
By now some of you have stopped reading believing I am a proxy spokes-salesman for MYOB or Microsoft and I can assure you I am not, never have been and simply to old to be one - no this is from the heart and soul and in response to the screams of 'foul', 'don't do it', 'revert back', etc etc; and if you doubt which side I am on just read some of my replies to forum posts where I am most scathing of MYOB and what it is doing.
And yet MYOB leaves these posts up and on line ....... and I will continue this stance as required.
On to the recent changes - folks I hear you - they are fundamentally badly timed, badly managed in their roll out and simply very unwelcome - and I put this all in a big post to the forum and the 'language I used was grey zoned and the post got pulled' - a rarity in my posts - I generally don't write those sorts of posts - but this time I was angry at the changes, the timing and still am.
And there is a fundamental thing in software changes of such magnitude - that they are not impulse driven and short in planning - I suspect this change was a long time in the planning and implementation ( but badly advertised and implemented, and the timing at the EOFY 26 just stinks) and even if someone in MYOB wished it, rolling back these changes is as difficult as stopping a freight train and reversing it - I just believe these changes cannot be rolled back.
So what do we do, the users, the book keepers, the business owners, the developers, the analysts - we continue the shrill screams of 'foul' - very important that MYOB just needs to know how much we hurt out here..... but at the same time say - OK MYOB we have no choice but to accept these changes and we ask for something they have the power to give us ...... something to fill the gap and chasm of functionality that this change has caused.
My point - OK MYOB we will be dragged screaming and shouting to this change and it seems we have no choice on its implementation - your bad - but here is how you can perhaps ameliorate the change - produce a utility, a set of tools that simply allows those who want to, to download a backup and store it according to 'our business rules for security' and a utility or set of tools that allows us to open these files offline and view data.
There are a lot of considerations around this scenario but it would fill a huge chasm of functionality for so many users - it isn't a good solution, it isn't the best solution but I do not believe MYOB can roll this change back ... so my solution for a set of tools might be the 'only solution'.
Folks - please scream all you like - call me a turncoat, a proxy MYOB agent - be my guest - not the first time... but once you realise that this monumental change is 'fixed in concrete' as I believe it is, it gives clarity to moving forward and looking for another solution.
I will state for the record that I am not a proxy MYOB agent, I have not been 'got at' by MYOB, I have not be 'cautioned' by MYOB or in any way influenced on my stance - and to naysayers who don't believe it - I say read my past posts.
For those who reluctantly just want to move forward and 'deal with these changes' - offer some realistic reasons ( rather than emotional ones that can be shot to pieces) and the reasons why a set of tools as proposed would be a great stop-gap solution, if not a solution.
Up to you folks - keep this post alive or kill it, your choice.
The Doc