Flow Simulation has a folder naming convention that is not accepted by my Document Management tool. Inside the study results folder there is a sub-folder that starts with "$". That characeter is not allowed in my file system. Can someone test removing the "$" and see if Flow Sim still works...
I'd like to access my Vault at home when I travel. I don't want to use vpn, I just want to open ports on my router and directly addres my Vault competer's ip address and use the native Vault client to login. I've seen it done, but don't know what the IT/router setup looked like. I don't...
Right I forgot to mention it's decimal units not fractional, in which case the (in) shows up. Manufacturing can't have (in) or (mm) it must be (") for ALL inch dimensions (') for feet, and nothing for mm. We've all had these battles, I just wanted to make sure I wasn't missing a check box...
Dual dimensions, feet-inch on top, mm on bottom, no show units. Dimensions over 12 inches display correctly as 1'-5.000". Dimensions under 12 inches display 5.000. No (") symbol. Can't have the text (in) and/or (mm) displayed due to manufacturing requirements. Soooooo close, just need (")...
Yes, that's what we have now. Two lists accessed via the property tab pane. I was trying eliminate the need to set both of these properties on every part, drawing, and assembly on every check-in for the entire life of the document. It sounds trivial until you've got 100+ files to check in.
Yes, I think many would have a use for it. Your concern for security is valid, however in my case it is not an issue as none of these users would intentionally delete a property. My wish is that once set SW/WorkGroup would not automatically change it with each check-in.
Without resorting to Lifecycles I'd like to have two custom properties populated as follows:
"Author" would lock to the logged in user that created the document originally and never change. Maybe "created by" would be more descriptive.
The second would be set at check in, equating to the...
When I run a macro on 08' sp0.0 I get a "runtime error 13 type mismatch" message. That I don't get when running the same macro on 08' sp3.0. What are the chances that it is only a service pack issue?