tamhas
ProgressTalk.com Sponsor
If you are modifying source code, why is there a requirement to not change the create date of the file? This seems like one of the most basic elements of version control.
If Unix, I have a shell script I wrote a million years ago that uses sed and sdfiff and will give you preview of the changes to be made side by side so that you can tell it is going to do the right thing. It will be a ***lot*** faster than doing this with Progress. Note that this won't preserve your create dates, but it is vastly safer because of the ability to preview.
BUT, if it is source code, you are limiting yourself greatly by treating it as text. There are a whole lot of ways to get in big trouble because you think you are changing a database field name, for example, but that also turns out to be a variable name, a loop name, part of a comment, etc. Not to mention, of course, the problem one can get into if the code includes any abbreviated fields, tables, or keywords. To do this properly you should use ProParse or ProRefactor so that you are operating on syntactically meaningful units.
BTW, a brief statement in the initial post that this what you wanted to do would have produced a different discussion.
If Unix, I have a shell script I wrote a million years ago that uses sed and sdfiff and will give you preview of the changes to be made side by side so that you can tell it is going to do the right thing. It will be a ***lot*** faster than doing this with Progress. Note that this won't preserve your create dates, but it is vastly safer because of the ability to preview.
BUT, if it is source code, you are limiting yourself greatly by treating it as text. There are a whole lot of ways to get in big trouble because you think you are changing a database field name, for example, but that also turns out to be a variable name, a loop name, part of a comment, etc. Not to mention, of course, the problem one can get into if the code includes any abbreviated fields, tables, or keywords. To do this properly you should use ProParse or ProRefactor so that you are operating on syntactically meaningful units.
BTW, a brief statement in the initial post that this what you wanted to do would have produced a different discussion.