Ele
Trusted Cover User
Joined 10 years ago
User Profile
User Widgets
Contributions
Why does it take so long to delete dead jobs ?
We reuse job numbers. So I go thru Myob deleting dead jobs. What I am curious about is : Why does it take so long ? file length (number of debtors & creditors invoices) does not seem a factor. Why does it say Job Information/not responding ... when it is working in the background?Re: Just updated to 2022.2 and can not scroll down within the payroll category
Thanks for your reply Sam R. You say 'the scale may need to be adjusted to your liking' However .... for us who have made the scale bigger to see the small fonts used (which get harder to read if you are sight challenged). It would be rather off-MYOB-putting, if you had to scale down to see a choice, scale up to read, scale down to choice, scale up to read. If Myob do not make everything scroll-down-able - then they will miss out when sightchallenged users decide its all too hard to use.747Views0likes1CommentHow to change the font size WITHIN Myob
Back in 2017 a user noted "It seemed more logical to change display settings WITHIN MYOB rather than hoping that a global Windows display setting change would suffice, going back and forth to see results, disappointed. Thanks for the reply, though..." It still is logical and applicable - especially to us who use glasses. I have noticed that my employers are also now squinting when looking at MYOB. Maybe the inability to increase the font size within MYOB will force them to purchase a new programme they can actually see on screen.1.4KViews1like1CommentRe: OrmDataException
"when I am the only person in that order" = orders are part of the Purchasing Section I raised the order, got the OrmDataException roadblock. Closed out. Re-opened and checked to see the last order/purchase number (via Find Transaction) ... and lough and behold it was there. It has not happened since. Thanks.1.5KViews0likes5CommentsRe: OrmDataException
This comes up when after entering the transaction for the first time, you press record. Up comes OrmDataException. You cancell out (thinking you can not save your entry). You decide to double check via Find Transactions, and guess what? it is there !!! THEREFORE the error is somewhere in the system. it is nothing to do with the client (me) having two windows open (see original entry)1.6KViews0likes7CommentsOrmDataException
Generally speaking an “ormdataexception” message means that the data has been changed in the background. This could happen if a transaction was opened in two windows or on two computers and it was changed on one, whilst the other computer it was still open Why do I get this when I am the only person in that order. So no-one else is creating that transaction. And no, there were not two windows open on my computer at that time.Solved