AccessBlog.net

News, links, downloads, tips and tricks on Microsoft Access and related

About Me Search
Alex
Name:Alex Dybenko

Location:Moscow, Russia

Thursday, February 16, 2006

How to read ADP custom properties

This was really a nutshell. In MDB this is very easy – using currentdb() you get access to all available properties. There is no currentdb in ADP, there is a CurrentProject, but you can get only properties you add yourself, using CurrentProject.Properties. Also you have to start Access in order to read these properties – not a good idea for such a small application like VersionCheck.

Fortunately Google Groups knows everything! I found a following tread, discussing this issue. Sylvain Lafontaine (MVP) points to article Tales from the Script, which brings some light on this problem. Furthermore – there is an article in MS KB “Dsofile.dll lets you edit Office document properties without Office in Visual Basic .NET 2003 and in Visual Basic .NET 2002”, which shows samples using Dsofile.dll.

Currently I am improving our VersionCheck, so it can also work with ADP files, and let you know on results.

4 Comments:

Anonymous Anonymous said...

Hi Alex,

Curious if you were ever successful in reading the properties of an ADP/E using DSOFile.DLL?

Your blog never went on to say if you were able to accomplish this.

Walter Niesz
Fellow MVP

3:40 PM  
Blogger Alex Dybenko said...

Hi Walter,
yes, it works (well, worked at least) a me, try to run VersionCheck from the link above

3:51 PM  
Blogger JohnDoe said...

This comment has been removed by the author.

8:03 PM  
Anonymous Anonymous said...

Thanks Alex. It's good to know that this does work. Currently, I'm just opening the ADP with Automation and grabbing the values. I'm trying to decide whether it's worth it or not to add a dependancy to my project, or just use Automation.

But since you have managed to make it work, I now know that I have option available.

Thanks again,
Walter

8:05 PM  

Post a Comment

Links to this post:

Create a Link

<< Home