Do most of you write all reports using Progress 4GL? I am just curious. It would seem that any of the reporting packages available would require ODBC. And ODBC would require the SQL Width to be properly set within the Progress database. But most Progress programmers do not care about the SQL Width because the Progress database will accept any length of character string content.
Personally, I am livid with anger towards Progress for releasing a product that fails to work well in 'normal' work environments in which people work with sofware that does not come from Progress.
If Progress owned the intelligence behind our most popular operating systems (or our most popular anything), then, perhaps, Progress could dictate to the marketplace. However, the majority of users, systems professionals, and business managers in the U.S. have never heard of Progress. Frankly, I don't care what the licensing arrangements are for a developer, if it walks like a duck, talks like a duck, and looks like a duck, it's a duck.
Personally, I am livid with anger towards Progress for releasing a product that fails to work well in 'normal' work environments in which people work with sofware that does not come from Progress.
If Progress owned the intelligence behind our most popular operating systems (or our most popular anything), then, perhaps, Progress could dictate to the marketplace. However, the majority of users, systems professionals, and business managers in the U.S. have never heard of Progress. Frankly, I don't care what the licensing arrangements are for a developer, if it walks like a duck, talks like a duck, and looks like a duck, it's a duck.