type conflict where type not found in sequence file

[pwaszkewitz]

 Hi,

from a central master sequence, I am starting several sequences from other sequence files in new executions. These sequences have individual types as input and output parameters, the types being defined within these sequence files.

The master sequence only knows the names (as strings) of these types and when I do a "Find/Replace in files" in the master sequence file looking for those types, they are not found.

However when I change one of the types in its respective sequence file while I have the master sequence file open, the master sequence file is shown with an asterisk and later I get a type conflict if the settings is to "Never allow automatic type conflict resolution". This is fairly awkward since the master sequence file is supposed to be password protected and no-one should have to touch it in a project.

What can cause this behavior?

Apparently, usage of these types spread around through all sequence files although they do not have any need for using the types from other files.

Is it possible that it makes a difference whether the type was first defined in a type palette file or directly in a sequence file?

Best regards,

Peter

[Norbert_B]

Peter,

using the data type as parameter in another sequence file will include the type definition in the calling sequence file, therefore changing it. I am not sure why the Find/Replace tool does not display it, but it shows up in the types palette of the file.

When the data type is changed, it will result in a type conflict....

So when trying to reproduce the issue with TS 2010, i receive an dialog for resolving type conflict when setting to never do an automatic resolve...

Nevertheless, the calling sequence must be updated for sure if a used type is changed.

hope this helps,

Norbert