I have one of those unanswerable 'why' questions.
The 'control wizards', like for buttons and such, make extensive use of
the
'DoCmd' keyword.
E.g. if you use the button wizzard to add a button to a form, and tell the
wizard that you want that button to open up a form, you get VBcode that
says:
"DoCmd.OpenForm stDocName, , , stLinkCriteria"
Now, since 'DoCmd' is one of the MANY functions/expressions that are
blocked
by 'sandbox mode', how are we supposed to re-write the code to make a
button
open up a particular form in a way that *won't* get blocked by sandbox
mode?
(and here comes the unanswerable 'why') Why would the wizards still use
'dangerous expressions' to do what needs doing? (Or is there no better
way,
and MS is merely trying to feed more money to the third-party certificate
authorities?)
We aren't nearly big enough to need a Certificate Authority.
Is there a way to use a 'self-certified cert'?
I'd like to not have to turn off sandbox mode just to be able to run my
own
code! So if I could re-write the code to comply with the sandbox rules,
that'd be great. So how do I get VBcode to open a form without using
'docmd.
openform'?
(If I wrote a WSH-type script to turn the sandbox on or off via the
registry,
would a user without admin rights be able to do that? Or would I need
some
sort of 'run as...' thing?)
jk
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/200805/1
|
