Sage 100

Price level field is one character, could really use 2 or 3. What are the ways you've gotten around this limitation? I need about 70 price schedules, and the limit of 37 is too restrictive.

Staring at the keyboard, there about 68 different characters for use (~!@#$%^&*_+........) That might get you close. You aren't restricted to just alpha and numeric, any character will work. @DanBurleson wrote a pricing script for me a couple years ago using and Access database. There were over a 1,000 pricing combinations in all. Complicated, but he got it done...

Didn't think about the extra #$%^& characters but it would be hard to describe...customer is on the * list or the $ list but not the ^ list. Thanks for the idea about the db I'll look into it.

I know. Looks ugly, cumbersome and very embarrassing to describe. Just don't get why this field hasn't been expanded.....

DSD has a nice extended price level enhancement too.

Actually, they have two. The first one allows upper and lower case (I think?) and the second is two characters.

@ThereseLogeais - thanks I'll look at their enhancements. Couldn't agree more with you @JeffSchwenk it only took them 20+ yrs to expand item numbers, customer numbers, if we wait long enough it might get done in Sage 100 Release 2050.

Yes, while the glitz (cloud, mobile) sizzles, it is the solid backend functionality that keeps people paying the maintenance. A big glaring hole in the foundation. I am sure the DSD enhancements are great, but REALLY?? There shouldn't be a need for them.