Hello,
Sorry about that. With further testing, it appears the File Format overrides are not saved with the "Use for All files" setting to prevent conflicts with the Folder Compare: Session Settings: Misc tab's File Format handling.
Here's a new strategy:
Go to Tools->File Formats. Edit your COBOL Ebcdic file format.
Change the mask from trying to match on to a file extension, to a folder path:
*cobol*;*cobol*\*
(The 2nd definition is to help match in upcoming database changes).
Go to the saved Folder Compare, go to the Session Settings, Misc tab, and uncheck all the file formats except for the custom COBOL Ebcdic.
Now, when you open a file, the left side (which won't match *cobol* or *cobol*\*) will use the default, and things on the right path will.
And I just found your quote.
I edited this post/removed my paragraph asking you for BC2 settings, because this quote helps explain how that was working.
Let us know if how the *COBOL* file mask works for you, and if you run into any trouble implementing that solution.
Sorry about that. With further testing, it appears the File Format overrides are not saved with the "Use for All files" setting to prevent conflicts with the Folder Compare: Session Settings: Misc tab's File Format handling.
Here's a new strategy:
Go to Tools->File Formats. Edit your COBOL Ebcdic file format.
Change the mask from trying to match on to a file extension, to a folder path:
*cobol*;*cobol*\*
(The 2nd definition is to help match in upcoming database changes).
Go to the saved Folder Compare, go to the Session Settings, Misc tab, and uncheck all the file formats except for the custom COBOL Ebcdic.
Now, when you open a file, the left side (which won't match *cobol* or *cobol*\*) will use the default, and things on the right path will.
And I just found your quote.
such that cobol files always prompted me for the conversion code, ansi for the PC, 1143 for the mainframe
Let us know if how the *COBOL* file mask works for you, and if you run into any trouble implementing that solution.
Comment