<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.office.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>Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx</link><description>In the last post, I gave a quick overview of SharePoint, SharePoint lists, and how Access works on SharePoint. In this version, I'll show what happens when you move an Access database to SharePoint. Publish to SharePoint Access has had a feature to "Upsize</description><dc:language>en-US</dc:language><generator>Telligent Community 1.5.134.15456 (Build: 5.5.134.15456)</generator><item><title>re: Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx#17921</link><pubDate>Thu, 01 Feb 2007 16:32:07 GMT</pubDate><guid isPermaLink="false">53587256-c606-4c9b-bad4-97c86b12ce62:17921</guid><dc:creator>Imamu Hunter</dc:creator><description>&lt;p&gt;What is it going to take to get microsoft to add an auto scheduling function to MS Access. Please try to look at it from the users side. To schedule reports in MS Access would be a revolutionary tool. Please try to help us.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.office.com/aggbug.aspx?PostID=17921" width="1" height="1"&gt;</description></item><item><title>re: Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx#17922</link><pubDate>Mon, 01 Jan 2007 16:40:57 GMT</pubDate><guid isPermaLink="false">53587256-c606-4c9b-bad4-97c86b12ce62:17922</guid><dc:creator>LCCVR</dc:creator><description>&lt;p&gt;Access 2003 already had some WSS 2.0 integration capabilities: it could link, import and export lists, edit data, create reports based on WSS data, etc. Now Access + WSS integration is said to be a &amp;quot;brand new feature&amp;quot; and, even more, the main reason to upgrade do A2007. It&amp;#39;s a nice feature to have and I consider Access an excellent front-end to WSS data, but I don&amp;#39;t believe I&amp;#39;ll see or work with Access + WSS apps because 99% of the Access relies on desktop databases. I want to see what was done for developers: improvements in object models? Tools for code-generation? Mouse wheel in VBE is fine, but it should be on since Access 2k or XP. Report and form design capabilities are one of the main benefits for developers.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.office.com/aggbug.aspx?PostID=17922" width="1" height="1"&gt;</description></item><item><title>re: Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx#17923</link><pubDate>Thu, 12 Oct 2006 20:13:23 GMT</pubDate><guid isPermaLink="false">53587256-c606-4c9b-bad4-97c86b12ce62:17923</guid><dc:creator>Stevbe</dc:creator><description>&lt;p&gt;OMG ... thanks for correcting me ... it has been a while (obviously) since I worked with Original WSS ... never touched the new Coke :-) Why use the same TLA ... with only 19683 (3^3?) available they need to start conserving resources ... or is this kind of like the confusin being sown by mashing WinFX and .NET 2.0 together and calling it .Net 3.0? I don&amp;#39;t ever plan on storing anything in SharePoint directly, hey ... I read the details, it really is good at indexing but you are are wasting time and space by not just pointing it at your file servers. OK ... enough rant ... I have not got B2TR on my PC yet but am planning on it this weekend for more ribbon experiments. Steve&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.office.com/aggbug.aspx?PostID=17923" width="1" height="1"&gt;</description></item><item><title>re: Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx#17924</link><pubDate>Thu, 12 Oct 2006 19:29:59 GMT</pubDate><guid isPermaLink="false">53587256-c606-4c9b-bad4-97c86b12ce62:17924</guid><dc:creator>Mike</dc:creator><description>&lt;p&gt;Stevbe, Ok, now I understand your confusion! The acronym “WSS” was also used for the “Web Storage System”, an Exchange 2000 and SharePoint Portal Server 2001 (SPS) storage tech that now is defunct. Exchange now calls it “Exchange Storage”. There is no “M:” drive in Exchange 2003. Windows SharePoint Services, SharePoint Portal Server 2003, the new Office SharePoint Server (MOSS) do not use the old Exchange Web Storage System. The future of Web Storage System in Exchange is murky. Clear as M$ mud? To say this another way, Windows SharePoint Services (WSS) that M$ linked Access 07 to has nothing to do with the old Web Storage System. WSS uses SQL Server or MSDE/Express as a storage platform in a funky SharePoint kind of way (basically everything is stored in three tables). You did make me think, although. From the stand point of Access, it makes no sense to story anything on SharePoint. But from the Standpoint of SharePoint, it’s good to have something as powerful as Access to handle data massaging. So for example if a SharePoint “list” (that is SharePoint lingo for a pseudo table), contains a survey or URLs, contacts, etc, you can at least get at this data and manipulate it allot easer in Access. This is one case where it makes sense to link Access to SharePoint. Mike&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.office.com/aggbug.aspx?PostID=17924" width="1" height="1"&gt;</description></item><item><title>re: Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx#17925</link><pubDate>Thu, 12 Oct 2006 14:50:41 GMT</pubDate><guid isPermaLink="false">53587256-c606-4c9b-bad4-97c86b12ce62:17925</guid><dc:creator>StepUP</dc:creator><description>&lt;p&gt;I finally got to updating to the nearly half a gig &amp;quot;2007 Microsoft Office system Beta 2 Technical Refresh&amp;quot;. I could not find any info as to what was fixed or changed for Access in this release. Does anyone have a clue on this? One thing that I noticed was NOT fixed was the &amp;quot;auto repeat&amp;quot; capability on the navigation buttons (i.e. the ability to quickly scroll through records when the forward or back buttons are pressed). I reported this months ago. I was hoping that there would be several new &amp;quot;color schemes&amp;quot;, or a way to make forms have a classic Windows style. Will this ever be possible?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.office.com/aggbug.aspx?PostID=17925" width="1" height="1"&gt;</description></item><item><title>re: Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx#17926</link><pubDate>Thu, 12 Oct 2006 12:39:11 GMT</pubDate><guid isPermaLink="false">53587256-c606-4c9b-bad4-97c86b12ce62:17926</guid><dc:creator>Stevbe</dc:creator><description>&lt;p&gt;Mike: &amp;quot;WSS is just a data store&amp;quot; Yes ... Web Storage System was introduced with Exhange 2000 not with SharePoint (which was code named Tahoe). Take a look at an Exchange 2000 server, you will see a mapped drive &amp;quot;M&amp;quot;. This is a virtual drive that you can use to read/write files into WSS directly from Windows Explorer. SharePoint is just another FE into WSS. You can read/write to WSS without using SharePoint at all by using file system code, ExIFS and even with ADO. it is a database management system, it does not store the data in and of itself, that is why we have the option to use jet, newjet, excel, text, sharepoint etc. as data sources. I am still experimenting with ribbon options myself and also dislike the *playschool* button size but have not come up with a good use of the extra space if I do use small buttons. Steve&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.office.com/aggbug.aspx?PostID=17926" width="1" height="1"&gt;</description></item><item><title>re: Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx#17927</link><pubDate>Thu, 12 Oct 2006 07:16:41 GMT</pubDate><guid isPermaLink="false">53587256-c606-4c9b-bad4-97c86b12ce62:17927</guid><dc:creator>Mike</dc:creator><description>&lt;p&gt;Erik, I answered my question. Yes, you can modify the &amp;quot;office button&amp;quot; FULLY. This is good news for the HelpDesk… Now if I can just get an event to fire when a ribbon menu TAB is clicked. This will at least allow existing 1024x768 forms to work if the ribbon is set to auto hide - not ideal, a clunky/distracting menu flash actually, but it removes an impediment to Access 07 use by hundreds of users with 1024x768 screens. An alternative is to have the main application objects (that were accessible via a nice slim custom tool bar) accessible via large garish buttons on a ribbon or clumped up buttons or something ribbon-fishy. Mike&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.office.com/aggbug.aspx?PostID=17927" width="1" height="1"&gt;</description></item><item><title>re: Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx#17928</link><pubDate>Wed, 11 Oct 2006 21:09:06 GMT</pubDate><guid isPermaLink="false">53587256-c606-4c9b-bad4-97c86b12ce62:17928</guid><dc:creator>Mike</dc:creator><description>&lt;p&gt;Eric, there are exactly ZERO discussions about how to modify the &amp;quot;Office File Menu&amp;quot; - the big round button. This has NOT be covered in this blog - or Jensen&amp;#39;s - or anywhere. In Access 2007 can the items on this menu be removed/added/changed through VB? For example, can we remove the &amp;quot;Access Settings&amp;quot;, New, Open, Save As, etc. I would really like an answer to this!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.office.com/aggbug.aspx?PostID=17928" width="1" height="1"&gt;</description></item><item><title>re: Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx#17929</link><pubDate>Wed, 11 Oct 2006 20:54:07 GMT</pubDate><guid isPermaLink="false">53587256-c606-4c9b-bad4-97c86b12ce62:17929</guid><dc:creator>Mike</dc:creator><description>&lt;p&gt;&amp;quot;WSS is not the same thing as SharePoint, that would be like saying that Jet and Access are the same thing. WSS is just a data store, nothing more, nothing less, I was programming with it back before it was RTM&amp;#39;d with Exchange 2000. &amp;quot; Hmmm. WSS = Windows SharePoint Services = SharePoint v2/v3&lt;/p&gt;
&lt;p&gt;STS = SharePoint Team Services = SharePoint v1 &amp;quot;WSS is just a data store&amp;quot; I suppose that Access 07 is not a database application anymore also...&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.office.com/aggbug.aspx?PostID=17929" width="1" height="1"&gt;</description></item><item><title>re: Publish to SharePoint</title><link>http://blogs.office.com/b/microsoft-access/archive/2006/09/18/publish-to-sharepoint.aspx#17930</link><pubDate>Wed, 11 Oct 2006 19:38:38 GMT</pubDate><guid isPermaLink="false">53587256-c606-4c9b-bad4-97c86b12ce62:17930</guid><dc:creator>Stevbe</dc:creator><description>&lt;p&gt;Eric: Sorry if I sounded confrontational, I really do appreciate the information you have been providing us even if I don&amp;#39;t always agree with the decisions that have been made. I hope this experiment in continual development blogs does not die because it seems like all you get is flack and the onerous spam posts &amp;quot; great site ... meet me at the poker table&amp;quot;. Which leads to an off topic question ... can you folks block post backs that have the words &amp;quot;poker&amp;quot;, &amp;quot;alice&amp;quot;, or &amp;quot;zoomer&amp;quot; in them? that would trim the auto-email by about 50%. Thanks again,&lt;/p&gt;
&lt;p&gt;Steve I think for my current employment, 2007 will not affect me much other than working out the detail of the ribbon which don&amp;#39;t seem to really be that difficult, just a bit more time consuming.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.office.com/aggbug.aspx?PostID=17930" width="1" height="1"&gt;</description></item></channel></rss>