S
Snaux
I have a small utility (.exe) that I've embedded in my database as an
OLE Package. I found that if I double-click it, it actually runs...
very cool and quite unexpected functionality for a low-end db like
Access. My database "shells" numerous small utilities like this, which
got me thinking about using my database as a container for them, to
both aid in distribution and to keep idle hands from playing with them.
1) How can I get the OLE Packaged executable to actually run via VBA,
as opposed to double-clicking the field that contains it?
2) Once embedded in the db as an OLE package, is there a way to extract
it back to a standalone .exe file?
OLE Package. I found that if I double-click it, it actually runs...
very cool and quite unexpected functionality for a low-end db like
Access. My database "shells" numerous small utilities like this, which
got me thinking about using my database as a container for them, to
both aid in distribution and to keep idle hands from playing with them.
1) How can I get the OLE Packaged executable to actually run via VBA,
as opposed to double-clicking the field that contains it?
2) Once embedded in the db as an OLE package, is there a way to extract
it back to a standalone .exe file?