Sage 100

Things which if left as-is will spell the end of the Sage 100 product line (presuming there's a future): Go ahead and add your pick for the issues that Sage 100 needs to get under control... - Paperless Office and the myriad of security rights, permissions and general awkwardness of moving/relocating documents - Upgradeability of Sage 100 when third party enhancements are present --realistically having two or more enhancements (sometimes one) stalls you at the version you are at.

Depends on the enhancements. Ones I've worked with in that category are JobOps, T & B and POS. I'd add: - Sage CRM integration - Lack of BI Dashboards - Job Cost - Payroll - V/I - Inability to validate UDF's against existing files - Crappy Explorer

ODBC Security randomly turning itself on (or off)...

Technology confusion... Providex, SQL, Pervasive, a myriad of third party stuff (Aatrix, etc.) for the basic functions to work, old and new framework, 1/2 finished object interface, etc. Pick a base and let the MD community fill the holes you leave behind. Have a roadmap

Should Sage 100 be spun off from Sage?

Or perhaps a better question, should Sage be spun off from ""MAS 90"" (aka Sage 100 ERP)

Keep dreaming boys. Sage is gonna milk that cow till it is dry.

I forgot - it's funding the X3 development.