Is your client on Standard or Advanced? If Advanced, try logging in to Sage 100 in "MAS 90 mode". I've run into this issue with a client; not clear on the source, but permissions of one sort or another may be behind it. I have an unresolved case open with Sage, but the above workaround is working for them.
↧