var sidebar_align = 'right';
var content_container_margin = parseInt('290px');
var sidebar_width = parseInt('270px');
Unanswered: dissable open or cancell promt in access runtime
in standard access 2003 you can dissable the open or cancell promt that appears when you first open a db through properties. you can also dissable the permisions for update and append queries.
is it possible to dissable these in the access runtime version that comes with visual studio tools for office?
Last edited by "L"PLATE; 12-12-06 at 14:12.
I haven't used VSTO yet, but I would imagine you still have access to the DoCmd.SetWarnings method via COM at the very least...
once you package your db app you can't see the db window, unless you packeged it giving users the ability to see it obviously.
and no other db's can be opened with the runtime version unless it was installed with runtime.
do you know the complete command, i'll give it a go and let you know if it works
access 2003 runtime, visual studio 2005
i've managed to dissable the confirm query actions permissions with: -
Application.SetOption "confirm action queries", False
Application.SetOption "confirm record changes", False
Application.SetOption "Confirm Document Deletions", False
seems to do the trick in access runtime too
still sturgling with the macro security settings, the "msoAutomationSecurityLow" command should set security to low but i can't get it to work
any ideas anyone?
all help greatfully recieved
RESOLVED: Macro security in runtime
office 2003, visual studio 2005, access 2003
GOT IT SORTED
thought i'd post it here incase anyone comes across the same issue
1 - open selfcert.exe which should come with office 2003 and create a digital certificate
2 - open the visual basic window of your db app, ij the tools menu select certificate and assign the digital certificate that you created.
3 - when youR app is installed you'll be asked to trust this publisher, if you tick the "always trust this publisher" box then the macro security dialogue doesn't appear every time the app is started.
i've tested this in access 2003 runtime and it does the trick for me.
Last edited by "L"PLATE; 12-16-06 at 08:58.