Specifically, I want to override the 'New..' menu item. In Word / Excel /
Powerpoint, it is a simple case of having autoexec run in the default
template. But I cannot find a similar way of doing it in Access.
The Access Runtime Version is a version that does not include any design
capabilities (think MS PowerPoint Viewer). I am not that familar with it
nor Developer's Version of Access - which I believe you'll need to in
order to deploy it. I did find this article which should get you started.
The Access Runtime Version is a version that does not include any design
capabilities (think MS PowerPoint Viewer). I am not that familar with it
nor Developer's Version of Access - which I believe you'll need to in
order to deploy it. I did find these articles which should get you started.
Rather than preventing the user from creating a new database, I need to run a
routine that formats the new database's filename to a certain format. When
my db that contains the code is open and I go File->New..., it correctly
creates a new database with the right name, but I do not know how to get the
code to run outside of the test database.
A new requirement at work requires all documents to follow a certain naming
convention and because we use an NT4 domain, we are unable to use document
management software.
I have a dialogue box comes up asking for the subject, then it formulates
the filename based on that. I have sorted out Word / Excel / Powerpoint,
just Access giving me headaches.
Actually, I take that back. It *MIGHT* be possible if you were to create
some sort of solution using VB that invokes the Access Object Model to
create a new database. At that point, you have the ability to control
how the database is named, however the users would still have the
ability to change the name *AND* they would still be able to create a
new DB directly in Access that bypasses the naming schema.
And for that matter...
As a developer I would wash my hands of the whole thing and communicate
the new (however stupid) standard it is to the end users leaving up to
them to comply. In the end, they can still rename the files
(Access/Word/Excel/PowerPoint) or do a Save As... or Copy and trying to
fight that would be a waste of time. I would leave any noncompliance
issues up to the compliance police and the end user.
David H
(Final post and I promise to think before I hit SEND)