You're pretty close to getting what you need. There is a little trick though. The FVITEM table does not store the filename in the vault. There is a UNIQUESEQUENCENUMBER column that you need to use to derive the file name. What you do is take the sequence number, convert it to hexidecimal, and then prefill it with 0's until it is 14 characters long. DISCLAIMER: I didn't figure this all out on my own. There was a great DB links user presentation at PTC Global a few years ago that devulged this information. If I can find the presentation, I'll give credit to the presenter.
Ex:
UNIQUESEQUENCENNUMBER = 47772
Converted to hex: BA9C
Prefilled with 0's: 0000000000BA9C
So, you would look in the vault for the file: 0000000000BA9C
I made an app that I use to go from the vault file to the Windchill object, and the query looks like this:
SELECT h.*
FROM HolderToContent h, ApplicationData a, FvItem f
WHERE (f.uniqueSequenceNumber = 47772)
AND (f.idA2A2 = a.IDA3A5)
AND (a.idA2A2 = h.idA3B5)
I take the vault file name as input and convert it to decimal which then goes in the WHERE clause (f.uniqueSequenceNumber = <decimalValuefromHex>)
That should give you a pretty good start. We don't allows users to access files without using the UI, but I do understand your requirement You could also use the Windchill APIs to traverse all the objects/links.
Hope this helps.
~Jamie
