See, here's my point though. EvoERP is not substantially different than Classic. It's the exact same thing but with some GUI and other improvements. There is no leaving people high and dry. DBA NG was not even developed by DBA and was nothing like Classic AT ALL. There is a HUGE difference between what I'm suggesting and what DBA Mfg did. If Classic were as great as people seem to be suggesting then why does it even need updates?
The underlying problem though, is that so far EvoERP has had a lot of stability problems. It would seem that maybe it needs more testing before release. But still, the old classic programs are available in the interim. I just don't think that any work should be done to those old versions if it can at all be helped. If there is some huge show stopper then, yeah, fix it. But otherwise leave it lie. Classic programs are an albatross around the neck of EvoERP and really should go as soon as possible.
But, if using Classic means that much to people then they are free to use it for however long they want. I just don't think that they should expect any more updates.
Quote from tdlugosh on 03/08/07 at 09:37:10:I agree with GG. Think DBA->NG. They dumped a viable product for a pie-in the-sky product that stinks after at least 3 years work. Some people are perfectly happy with Classic - it does the job. Classic needs to be maintained while EVO is being developed. The market will tell ISTECH when Classic is no longer relevent. I'd hate to think Lynn would operate the way Mike Hart did and leave hundreds of customers stranded.
Tom Dlugosh