External Rule (API) Password for Project

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello Friends -
We are a small company and have chosen to use Legacy (shared type projects)
Twp part question -
I have already found the solution to apply an internal rule that prompts the user for a required password when they open the file... But I do not want to apply this rule one by one to thousands of drawings! I have skimmed the surface regarding API and ilogic....
Question 1. How would you create an external rule (password required to activate a Project)?
I want the shared Project type to be password protected... that way all inventor files associated will be protected under that project. More or less this is just to alert who is accessing inventor files under this project to be aware (prevent users) from editing accidentally released files...
If this password protection is an over kill, and there is another way to protect the files under the project from being edited accidentally... please convey!
Perhaps using the iproperties (status: Design state)?
Question 2. Is the check in and check out feature only accessible through Vault type projects?
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Problem...
Opening a Inventor file in two PC's or two inventor applications active on a single machine....
Inventor doesn't prompt with an alert when the file is opened by two people (applications)...
Both persons editing the file and still no prompts (alerts) from inventor....
However,
Inventor prompts this when a file is open and if you attempt to save your modified (edit) part.
If you answer "YES", you are given the second prompt and if you answer "NO", you can continue editing the part
If you answer "No" than you can continue saving the part and the other person tries to save the same part, inventor prompts him this...
So, my point is by than you would have two different parts... or lost changes to one of them... Is there another way to prevent this other than using Vault type projects?
When i check the "status" under iproperties, it doesn't seemed to matter weather it is "Released", "Work in progress" results are the same... and the check out and check in features are grayed out.. with fields empty.
Thanks,
Brian