I have been getting this error followed by "IO Error -38 in Reset Routine File not open." everytime I try and display any report. Reports still print with no problem. Just no display.

I am running AccountEdge 2008 Release 12.0.9 on a Mac OS X 10.4.11

Any ideas?

Thanks.

I fixed my own problem. -5000 is a Mac OS error code for a file access problem, which in turn lead to the -38 error code.

The solution: make the account an admin account. For some reason MYOB does not let you display reports unless the Mac user account is an admin account.

Actually it has to do with the permissions of the AccountEdge folders. If you do a Get Info on the folder itself and set the Owner to the logged in user and all permissions to Read/Write this will solve the problem.

Unfortunately, that is not the case. You are correct in theory, however the user had ownership and full permissions on the MYOB files. I was still able to make changes and save the file normally; the only thing that I could not do was display reports.

I'm no computer wiz, so this is kind of a guess. I noticed that when the user was not an administrator, the hard drive was locked on read-only, even though folders beneath it had full permissions. My theory is that the display reports command is sending a permissions request to the wrong parameter, like the hard drive permissions, or documents folder permissions rather than the file permissions.

We just got this error on one user system this morning. Nothing has changed on the user system. The other user is able to display this report without issue. Both users are Standard and not Admin users. In fact, the Custom and Forms folder contents except for one particular report that is giving us the IO Error -5000 are all set to Read/Write for the Standard Users.

I will do Permissions Repair and see if that fixes it while the team is at lunch.

I fixed Permissions and that did no good. So, I switched to the Admin User and set the folder permissions to everyone read/write and we were in business.

The odd part is that this just happened out of the blue this morning. It was working yesterday afternoon just fine. But at least it is fixed now. (For awhile anyway.)