![]() If almost everything is controller scoped, not so much. ![]() If they scoped tags locally for each of the individual burners, you're likely in luck. That, of course, will depend on how well the project is organized to begin with. If you change that to the "By Hierarchy" tab, you just get the scope of that tag, which may help more readily identify which tags you're going to keep and continue to use, and which are obsolete. As you likely already know, right-clicking on any given tag, then clicking cross reference, will pull up the report. The report defaults to the "By Logic" tab, which shows everything about that tag. If I were tackling this, I would probably go through the project routine by routine, cross referencing the tags on the rung instructions as I go. You mentioned that most of your tags are aliases this can be to your advantage, as the aliases are probably the ones that are most important, because it's rare in a large project to use a module defined tag without an alias. I don't know of any way to cross reference multiple tags simultaneously and even if you could, 4,000 tags would contain so much data that I don't know how you'd sort through it all. The cross reference tool is a method of determining every location and type of use a given tag is being utilized for in a project. It sounds like you've got your work cut out for you. ![]() However, V21 will work in Windows 10 just make sure you're using an older version of Adobe, as there are known conflicts with Adobe 11, such as online books not working, etc. ![]() V32 is the highest version currently available. Version 30 is the first one that is supposed to be 100% Windows 10 compliant. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |