reading custom properties from a closed file

Hi

I don't think you can - you will need to open it up first.

Richard,

I think this is possible.
In the windows explorer you can read the custom properties by a right-click / properties,
and the file wil not be opened.

Could you explain what it is that you want to know about the file - there are some properties accessible via the FileSystemObject, and perhaps these could be of use to you.

In the custom tab for the file properties, it is possble to add any number of custom properties.
You simply need to define a name, a type and a value.

My intention is to identify some kind of workbooks by some custom properties.
Maybe these properties will be set manually, or eventually they will be set automatically by the application.

The second step is to be able to read these custom properties from any workbook.
The goal is simply to create a kind of specialized scenario management.
All file from the same series of scenario would share a same custom property (setName).

In addition, all files related to this application would also share a common custom property.
In this way it is be easier create file selection screens where only the relevant files appear.

You can if you have the dsofile.dll - see here for details.
HTH

Well, i need to eat my hat because you would appear to be correct! I'll be honest with you I have no idea how to access those from a closed file - I don't even know how to write them to an open file. Time for me to try the macro recorder and see if that spots them.

EDIT: Ah, glad Rory dropped by - so now we know

rorya ,

Would there be a way to do it without dsofile?
What is inside dsofile that could not be written in plain VBA?

My concern is to keep distribution of my application as simple as possible.

lalbatros said:

What is inside dsofile that could not be written in plain VBA?

Click to expand...

As I didn't write dsofile, I have no idea what's in there, other than a bunch of C++ to work with compound objects! There may or may not be equivalent API functions that you can use from VBA, but just because something is possible for Microsoft, doesn't mean it's available to you as a VBA developer. In that article, you will note the section that reads:
"To help developers that are interested in reading document properties, we have provided the following two interfaces to manage property sets: <TABLE class="list ul"><TBODY><TR><TD class=bullet>•</TD><TD class=text>IPropertySetStorage</TD></TR><TR><TD class=bullet>•</TD><TD class=text>IPropertyStorage</TD></TR></TBODY></TABLE>However, some high-level programming languages may have trouble using these interfaces because the interfaces are not Automation-compatible. To resolve this problem, developers can use an ActiveX DLL, such the "DsoFile sample" to read and to write the most common properties that are used in OLE compound documents. This applies particularly those that are used by Microsoft Office applications."

Thanks rorya,

This illustrates very well and simply the historical evolution of the MS technology and the complexity it creates. Now in this .net period we tend to forget the technological wandering at the times of OLE and COM and even before.

I am still unable to tell what OLE and COM is, and I ignore totally what is behing the scene of .net, or even what .net actually is.