I guess I don't see wholesale re-writing all your code to use SQL instead of RLA as a prudent use of a technical staff resources :-)
Maybe your boss does, but that's not my business.
My staff is constantly working on new projects involving new technology, so there are ways of prudently using new technology without doing projects that might have .0001 percent net benefit.
Programmers will only wander off if they are bored and my staff would definitely wander off if I told them to go re-write all of our programs to convert RLA to SQL without a real business benefit :-)
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
-----------------------------------
date: Fri, 2 Nov 2012 16:08:33 -0400
from: "John Allen" <jallen@xxxxxxxxxxx>
subject: RE: Should I replace all CHAIN, SETLL, and READs to SQL
Richard,
We are always updating our existing code to ensure that it
is up to date and using the latest technology.
We don't want to have programs that were written 15 years
ago if there is more advanced way of doing something.
Most programmers never get the opportunity to update their
existing programs for just the reason you state
("just for the sake of the latest and greatest DB access
technique")
Our programmers do get this opportunity on a regular basis.
Just because a program is "good working code" doesn't mean
that it can't be improved.
Sometimes we just change good working Fixed format programs
to Free format for the heck of it programmers learn new
skills,
programs are easier to maintain and we end up with better
good working code
And our programmers like the fact they get to keep their
skills up to date and they don't go wondering off to another
company :)
midrange.com
