Why not use customer specific pricing?  It's more data to maintain, but works without any customizations.

Also, DSD has a couple enhancements to allow more customer price levels, if that is your goal.

You're active today! 

We have several customers that need different bill-to's but all accounts under the umbrella need the same price. I manage it externally currently, but it's very crude (email alerts to fix sales orders etc). 

The DSD enhancement is expensive and requires yearly maintenance fees. My hope would be for a custom office script to more or less accomplish the same goal. 

Yeah I might a VAR to show me how to use that, because the last time we played with that it was chaos, with invoices flowing through to the reference account. 

That's what test companies are for, but getting your Sage Partner involved is a good idea.

we did! 

At any rate, you don't think the UDF is viable? 

Custom Office is certainly something that can solve this kind of business problem.  We've done lots of fancy scripting to build a variety of business strategies for customer pricing.  However, using regular Sage features is more cost effective since it's fully supported and doesn't require additional design / development / maintenance costs.

When Sage 100 was sold not rented custom source code changes could be justified as enhancing your investment. The subscription model makes BOI scripting more affordable and less of a hassle to maintain. There isn't much you can't do with internal and external BOI scripting,

Display forms would be nice. I've been using menu-less bare bones IE windows, but IE is about to go away and there's no document object interface in Edge.

I use VB6 + VBCCR as an OCX form / class library for a UI outside NOMADS land. They can be used with UDT/UDF data and BOI external. VB6 calls back to ScriptBasic function and subs on events not associated with the UI.

This is VB6 OCX G/L Accounts Maintenance I did as a proof of concept that would use Sage 100's business logic (BOI) but not show the _ui object which would only be used for look-ups.

I use VB6 + VBCCR as an OCX form / class library for a UI outside NOMADS land. They can be used with UDT/UDF data and BOI external. VB6 calls back to ScriptBasic function and subs on events not associated with the UI.

This is VB6 OCX G/L Accounts Maintenance I did as a proof of concept that would use Sage 100's business logic (BOI) but not show the _ui object which would only be used for look-ups.

If I were to incorporate those tools then my backup team would be limited. As it is, any number of trusted independent Sage consultants can delve into my clear text and support my client's UDS and BOI scripts.