>Then the client has the wrong consultant. I have worked with the SBT and ACCPAC Products for years and never have I had the problems you mention. Nothing but satisfied customers who pay dearly for my services.....ACCPAC is highly configurable. The half assed conversions you mention are time proven accounting principals and hold true to this day. You might update your client from SBT to ACCPAC to see the difference. Give me their name and I'll take over the account for you....If you don't like it why do you still work with it?.....If you're an ACCPAC certified reseller or consultant I'm sure they (ACCPAC) would like to hear from you. You're not listed, on their website as an authorized reseller or consultant....That doesn't mean you're not but what qualifies you to work on the product and disparedge it here?
-----------------------------------------------------------

Being a reasonably competant developer qualifies me to disparge something that is so obviously a piece of crap. It may have been pretty hot back in '89, but programming methodology has advanced immesurably since then...and instead of embracing these advances, SBT chose to kludge in just enough to get it working with subsequent versions of fox. OOP? Not. Buffering? Not. Commitment control? Not. Normalized database design? Thats a big negatory good buddy. They might as well have just left the thing in DOS...the windows conversions are just window dressing.

Since when does cruddy old code equate to "established accounting principles", anyhow? The thing has SHOW and GET statements in it, for Petes sake. There are fields in some of the tables subdivided into other fields. Its a friggin joke.

If you can get money out of people for it, good for you. If it makes them happy, good for them. Britney Spears has a similar relationship with her clients. As long as the relationship is consensual, I'm not against it...