J
Joe
I want to be able to define and manipulate custom office properties
for an ADP file from VBA code within the ADP. Now, I can
interactively right click on the file, choose properties, choose
custom, and create a custom property and value. The property and
value even persist into the ade file I make from the adp. So far, so
good.
The problem is I can't come up with any way to set or even read these
custom properties from vba inside the adp file. I've seen some
examples of doing it with word 2003, but nothing for Access...let
alone Access adp files. I've got to believe that since I can set and
retreive the data from the UI, there's got to be an api somewhere I
can call...but short of exporting the dll functions from MSAccess.EXE
and trying to guess, I can't seem to find a way. Anyone?
Alternatively, is there any way to associate metadata with an adp file
that can be read and written from within vba? The metadata must
persist across executions, not be loaded from an external
source...otherwise i could sneak it into the tag property of a startup
form or something. Any out of the box ideas welcome...or if there's
something blindingly obvious that I'm missing.
for an ADP file from VBA code within the ADP. Now, I can
interactively right click on the file, choose properties, choose
custom, and create a custom property and value. The property and
value even persist into the ade file I make from the adp. So far, so
good.
The problem is I can't come up with any way to set or even read these
custom properties from vba inside the adp file. I've seen some
examples of doing it with word 2003, but nothing for Access...let
alone Access adp files. I've got to believe that since I can set and
retreive the data from the UI, there's got to be an api somewhere I
can call...but short of exporting the dll functions from MSAccess.EXE
and trying to guess, I can't seem to find a way. Anyone?
Alternatively, is there any way to associate metadata with an adp file
that can be read and written from within vba? The metadata must
persist across executions, not be loaded from an external
source...otherwise i could sneak it into the tag property of a startup
form or something. Any out of the box ideas welcome...or if there's
something blindingly obvious that I'm missing.