For the danger of being off-topic:
- In your files you may use variables that are identified as KEYWORDS in the Integrity-Context.
When you are now using default-settings for some Source-commands like for eg. check in, you are using the functionality "expand keywords". Effect: your file will be changed during check in.
Solution: define a general policy that uses the option "Unexpand keywords"
- For existing text-archives you can define an archive-parameter "Store by reference".
Doing this will have two effects:
a. the internal "View Member Differences" won't work any longer.
b. a check in won't store the difference to the previous revision any longer, but every time the complete file.
- For the future you can define that every archive created will be a binary archive.
Effects: see 2.
Hopefully this entry is helpful in your context.