<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>My favorite Access keyboard commands - part 2</title><link>http://blogs.msdn.com/clintcovington/archive/2007/02/21/my-favorite-access-keyboard-commands.aspx</link><description>I have a confession to make… I started hacking around in computers with Windows 3.1—never learned how to really use the command line. I know—I have fallen from grace for many of you developers. The mouse has been my friend. I’m trying to change and use</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: My favorite Access keyboard commands</title><link>http://blogs.msdn.com/clintcovington/archive/2007/02/21/my-favorite-access-keyboard-commands.aspx#1743275</link><pubDate>Thu, 22 Feb 2007 22:57:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1743275</guid><dc:creator>ken</dc:creator><description>&lt;p&gt;Sorry for the OT but it's important.&lt;/p&gt;
&lt;p&gt;From &amp;quot;Macro improvements of Access 2007&amp;quot;&lt;/p&gt;
&lt;p&gt;Clint:&lt;/p&gt;
&lt;p&gt;&amp;quot;I'm not the security expert on our team and my views don't represent the views of Microsoft or the Access team. We might even see Suraj (our security expert drop by if he gets a chance).&lt;/p&gt;
&lt;p&gt;I don't think you will ever see MS changing the security settings to low. There are just too many things that can go wrong. Keep in mind, the security setting effects all Office documents such as Word and Excel. I think most people that get an Excel doc will expect it to be safe. Most of the security hacks these days are social engineering hacks where you trick someone into running your software without realizing it could be dangerous. The security dialog makes people understand the application could run code.&lt;/p&gt;
&lt;p&gt;You don't get a security dialog when you run Notepad because Notepad won't ever do anything wrong. You don't get a security dialog when you run .Net apps because you got it when you installed it. &lt;/p&gt;
&lt;p&gt;Unfortunately, there are lots of bad people that have invested interest in doing harm to others computers. Given the bad things that have happened to Microsoft customers--the company has to take this issue very seriously&amp;quot;&lt;/p&gt;
&lt;p&gt;.............................&lt;/p&gt;
&lt;p&gt;Clint, we are developers that distribute Runtime .MDE/ADE applications to our customers.&lt;/p&gt;
&lt;p&gt;An Access Runtime application must be (virtually) similar to a compiled .exe or .NET application.&lt;/p&gt;
&lt;p&gt;It's a big mistake to *force* us to buy the sagekey scripts.&lt;/p&gt;
&lt;p&gt;In my opinion the Access developer team don't know (or simply it ignores) the needs of Access/VBA developers.&lt;/p&gt;
&lt;p&gt;Microsoft Access-Runtime-edition isn't an Office application for final users!&lt;/p&gt;
&lt;p&gt;Bye&lt;/p&gt;
</description></item><item><title>re: My favorite Access keyboard commands</title><link>http://blogs.msdn.com/clintcovington/archive/2007/02/21/my-favorite-access-keyboard-commands.aspx#1744595</link><pubDate>Fri, 23 Feb 2007 03:38:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1744595</guid><dc:creator>Clint Covington</dc:creator><description>&lt;p&gt;Thanks Ken,&lt;/p&gt;
&lt;p&gt;I will pass your feedback along to the Access team. I know they are looking at different deployment options.&lt;/p&gt;
</description></item><item><title>re: My favorite Access keyboard commands</title><link>http://blogs.msdn.com/clintcovington/archive/2007/02/21/my-favorite-access-keyboard-commands.aspx#1749464</link><pubDate>Sat, 24 Feb 2007 00:28:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1749464</guid><dc:creator>AL</dc:creator><description>&lt;p&gt;Of course, I have to agree with ken 200%. &amp;nbsp;After some Google or UA investigation, it is trivial for any programmer to inactivate the security warnings, the same way that SageKey does it. &amp;nbsp;This of course means that any malicious hacker can do the same thing. &amp;nbsp;So really, what's the value of this, other than annoying people. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;IOW, the security warnings do nothing to enhance security, but are a great embarrassment for developers and a great annoyance to end-users. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;At the same time, there is not even a peep in the help files about the dangers of SQL injection to delete all of my data, and not a peep about the dangers of using SQL Server security to apply permissions that can then be used outside of the Access application. &amp;nbsp;When will Access support application roles, which provide much better security and performance? &amp;nbsp;(Some time ago, you or Eric said you would try to look into it, but we have not heard back.)&lt;/p&gt;
&lt;p&gt;Please try to understand that this current approach to &amp;quot;security&amp;quot; simply does not work in practice. &amp;nbsp;I suggest that the next blog post be used to solicit users' concerns and suggestions about Access security issues. &amp;nbsp;You can add a poll that asks developers: &amp;quot;Who likes the current &amp;quot;security model.&amp;quot;&lt;/p&gt;
&lt;p&gt;Having said all that, I want to thank you gain for making this blog and keeping open the lines of communication. &amp;nbsp;I, for one, really appreciate it! &amp;nbsp;&lt;/p&gt;
</description></item><item><title>re: My favorite Access keyboard commands</title><link>http://blogs.msdn.com/clintcovington/archive/2007/02/21/my-favorite-access-keyboard-commands.aspx#1755718</link><pubDate>Sun, 25 Feb 2007 07:33:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1755718</guid><dc:creator>Clint Covington</dc:creator><description>&lt;p&gt;Please keep in mind, a malicious hacker can't modify the low security settings without tricking you into running code on the system. The only way the SageKey system might be allowed to do it is because someone trusts the person installing the code.&lt;/p&gt;
&lt;p&gt;I understand there are some frustrations with the current security model. Trusted Locations does help in many scenarios but not all. I will pass along the feedback to the people that manage those decisions.&lt;/p&gt;
</description></item><item><title>re: My favorite Access keyboard commands</title><link>http://blogs.msdn.com/clintcovington/archive/2007/02/21/my-favorite-access-keyboard-commands.aspx#1765225</link><pubDate>Mon, 26 Feb 2007 23:19:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1765225</guid><dc:creator>Clint Covington</dc:creator><description>&lt;p&gt;I did more research on this topic--I'm not that connected to the runtime these days. It turns out--I gave you some wrong information (sorry about that). When you create the runtime MSI the runtime will add a trusted folder reg key for your data folder. This means, we will run your application without security prompts without lowering all of your Office security settings. T&lt;/p&gt;
&lt;p&gt;Happy?&lt;/p&gt;
</description></item><item><title>re: My favorite Access keyboard commands</title><link>http://blogs.msdn.com/clintcovington/archive/2007/02/21/my-favorite-access-keyboard-commands.aspx#1771934</link><pubDate>Wed, 28 Feb 2007 05:31:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1771934</guid><dc:creator>AL</dc:creator><description>&lt;p&gt;:-) :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) &lt;/p&gt;
&lt;p&gt;(Yes, Thank you!)&lt;/p&gt;
</description></item></channel></rss>