I couldn't test the code, so apparently I posted it too quickly and made a mistake.
I didn't define the Property Set correctly, before trying to access the Properties within.
Try this version.
Dim str_part As String = ThisDoc.PathAndFileName(False) & "_str.ipt"
'MsgBox("str_part = " & str_part)
If System.IO.File.Exists(str_part) = False Then
MsgBox("The File " & str_part & vbNewLine &
" doesn't exist yet.",vbExclamation,"FILE DOESN'T EXIST!")
Return
Else
new_desc = iProperties.Value("Project", "Description")
new_part = iProperties.Value("Project", "Part Number")
Dim oOpen As Boolean = False
Dim oODocs As Documents = ThisApplication.Documents
For Each oODoc As Document In oODocs
If oODoc.FullFileName = str_part Then
oODoc.Activate
oOpen = True
End If
Next
If oOpen = False Then
Dim oDoc As Inventor.Document = ThisApplication.Documents.Open(str_part, False)
Dim oPropSet As PropertySet = oDoc.PropertySets.Item("Design Tracking Properties")
oPropSet.Item("Part Number").Expression = new_part
oPropSet.Item("Description").Expression = new_desc
oDoc.Save()
oDoc.Close()
End If
End If
No. There is little difference between Value & Expression.
The diffenence doesn't seem to be very well documented in the Online Help area.
An Expression is always going to be in the form of a String, while a Value can be a String, Double, Date, or Boolean, type data. This is why the Value route is usually the more popular one to use.
I believe using Expression is useful if you want to include 'live linked iProperty values' within your String. This can be a very helpfull for automation purposes, if you're familiar with how to do it.
For example, in a new part file, go into your iProperties dialog / Summary tab, and manually type whatever you want within the Title text box. Then go do the Project tab, and within the Description text box type: "=<Title>", without the quotes. When you click Apply, it instantly changed to say whatever is in your Title area, and you will now see an Fx symbol next to that property's text box, meaning it knows it is displaying a linked Expression.
Wesley Crihfield
(Not an Autodesk Employee)
