Folks, I looking for peoples opinions on modelcheck.
I'm prepping our pro/e data for entry into an ERP. We've shortened all descriptions (a string parameter in Pro) to 28 chars. Now the issue becomes controlling and maintaining. We have licenses for Model Check but have not implimented it. From what I understand modelcheck can keep people from checking in objects with too-long descriptions. My fear with this is having another program running introducing more uncertanties (ie bugs) into the picture. I also fear Modelcheck sucking away performance from Pro/e. We just don't need one more bottle neck, and one more reason for "premature exit". As far as modelcheck checking the parameter in Pro, I could write a toolkit app in 10 minutes to check the stringlength. I can't make up my mend to stop the user right there, or just put out a warning flag, or not let them save.
I realize MC can check all kinds of things, like hole diameters. I feel a simple toolkit app could acomplish the exact same thing on my terms, not PTC's. My skeptical attitude and my gut feeling is that this is an overblown application that becomes a bear on the back of the users.
I have not tried Modelcheck, just combed over the documentation. If anyone has been though this, or can defend modelcheck I like to hear your opinions.
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
