Sage 100

Looking for help with a v2017.2 client who is having a **S/O Entry screen issue** (see attached 3 screen-shots). Basically they get repeated/dup/corrupt lines and/or see actual line data in the column headers instead of the column headings. It's very inconsistent; can't make it happen at-will. And really it's only happening with one user because she primarily enters all the orders. Hasn't had a chance to try using a different computer. Usually they have to start over by closing S/O Entry and going back in. I think I may next need to try *ESC to temporarily disable screen customizations to see if that has anything to do with it, although that could have an impact on day-to-day operations in Sage 100, especially since we'd have to give it enough time (likely at least 3 days if not a week). Maybe try running the two Custom Office Utilities? Maybe try diff/new Sage 100 logon? I've already tried: oresetting the S/O Entry screen/panel and re-ran the Sage 100 workstation setup, but no help. odisabling wireless on the computer because it appeared it may have been in use by Sage 100, so I wanted to take that out of the equation, but no help either. Couldn't find anything here in SC, Sage KB or Sage City.

Any chance they have user defined scripts or a button script being executed? i remember seeing a post on sage city a while back that had the column names getting messed up. Here is the [link](https://sagecity.na.sage.com/support_communities/sage100_erp/f/sage-100-business-object-interface/72266/so-lines-button-script-changing-grid-column-headers/213482#213482).

I doubt this is it but add screen resolution to the list of things to rule out - I've had more than a few customer sites where someone is running other than the standard font size which causes odd display issues though usually that's limited to missing field names.

I had something similar and it was resolved with creating a new logon. But b4 doing that, have you tried having the user use a different computer? If you get the same error on a different computer, it is the user logon. If not, it is something with her computer.

Do they use the pipe ""|"" character anywhere in items / descriptions? I've seen grids become corrupted when encountering this character as data.

Thanks for the feedback. I haven't yet used it to further dig into the issue.