Showing posts with label Microsoft Office 2010. Show all posts
Showing posts with label Microsoft Office 2010. Show all posts

8/04/2012

Which Excel, Visio and other Office products can "Publish" to SharePoint

 

A frequent question I get is "I can't publish to SharePoint". Not all editions of Excel and Visio have the publish feature!

Excel and Excel Services

Any edition of Excel can save files to a SharePoint library. Only the following editions of Excel 2010 can publish to Excel Services:

  • Microsoft Office Professional Plus 2010
  • Microsoft Office Professional Academic 2010
  • Microsoft Excel Stand-Alone 2010

Details: http://support.microsoft.com/kb/2569945

 

Visio and Visio Services

Any edition of Visio can save files to a SharePoint library. The edition needed to use Visio with other SharePoint features varies:

  • SharePoint Workflow import and export through SharePoint Designer 2010: Premium
  • Visual mash-ups with Visio Services: Professional and Premium
  • Publishing of diagrams to SharePoint Process repository: Standard, Professional and Premium
  • Publishing Visio Web (.vdw) drawings to SharePoint: Professional and Premium
  • Automatic Data Linking to data sources in SharePoint: Professional and Premium
  • Real-Time sharing of dynamic, data-driven diagrams via a browser using Visio Services: Professional and Premium

Details: http://visio.microsoft.com/en-us/TryBuy/Pages/Edition_Comparison.aspxhttp://technet.microsoft.com/en-us/library/ee663485.aspx and http://office.microsoft.com/en-us/visio-help/save-diagrams-to-sharepoint-as-web-drawings-HA010357073.aspx

 

SharePoint 2010 Services and Features by edition:

http://sharepoint.microsoft.com/en-us/buy/Pages/Editions-Comparison.aspx

 

.

5/21/2012

SharePoint Office Web Apps

 

I'm astounded each time I mention Office Web Apps in my classes and presentations and find that many of the SharePoint users still have not used, or even heard of, these FREE SharePoint add ins.

 

What are the Office Web Apps?

Simply stated, Office Web Apps are Word, Excel, PowerPoint and OneNote running in a web browser. Or a better way to say this is these are Office applications that have been recreated as browser only applications. The user of the these applications do not need to have Office installed.

Office Web Apps are part of Windows Live and can be downloaded and added to any SharePoint 2010 installation. If you have not looked at Office Web Apps for a while, there have been a number of changes with Service Pack 1 including: support for IE 9, OpenDocument format (ODF), printing from Word and PowerPoint, insert charts into Excel, and more. See the links below for more info.

 

Browser Support:

Not just IE!

  • Windows: Internet Explorer 7 or later versions, Firefox 3.5 or later versions, Chrome
  • Mac: Safari 4 or later versions, Firefox 3.5 or later versions
  • Linux: Firefox 3.5 or later versions, Chrome

Mobile Browser Support:

  • Internet Explorer: Windows Mobile 6 through Windows Mobile 6.5 and Windows Phone
  • Safari 4 & 5: iPhone 3G or 3GS, iPhone 4
  • Other browsers: BlackBerry 5.x and later versions, Nokia S60 3.x and 5.0, and Andriod 1.6, 2.1, and 2.2

Is Silverlight required?

Short answer, no. Having Silverlight will improve the smoothness of PowerPoint presentations, the display of fonts and loading time of pages. Silverlight adds no benefits to Excel and OneNote.

 

Interesting features:

For a complete list of features download this PDF: Microsoft Office Web Apps Product Guide

Excel:

  • The Office Web Apps version of Excel is multi-user. As an example use, you could set up a conference call to discuss the budget, ask all of the users to click a URL to the Excel file stored in a SharePoint library and then as a group update the budget. Literally as you change a cell, all of the users see the change.

PowerPoint:

  • Not only can you view and edit PowerPoint decks, you can switch to full screen mode and deliver your presentation from your laptop. Forget your laptop? You can deliver your presentation from any compatible browser from any PC that can connect to your SharePoint site.
  • Office Web Apps also supports the PowerPoint Broadcast Service to make it easy to deliver PowerPoint presentations around the company or around the internet.

 

Free?

Let's say… "no extra charge". Your users do need to be licensed for Microsoft Office. Here's a quote from a TechNet article: "Business customers licensed for Microsoft Office 2010 through a Volume Licensing program can run Office Web Apps on a server that runs Microsoft SharePoint Foundation 2010 or Microsoft SharePoint Server 2010." Windows Live and Office 365 / SharePoint Online licensing also covers Office Web Apps.

 

How to experience Office Web Apps in 15 minutes or less!

If you don't already have Office Web Apps installed, the quickest way to learn about them is to create a Microsoft Live SkyDrive account or a Office 365 / SharePoint online account. As you are most likely a SharePoint user if you are reading this blog, then I'd recommend setting up an Office 365 30 day trial. I takes less than five minutes and does not require a credit card or payment commitment.

http://www.microsoft.com/en-us/office365/free-office365-trial.aspx?WT.z_O365_ca=Try_online-software-Simp_en-us

I'd recommend that you select the E3 trial so you can play with all of the features.

 

Links:

Microsoft Office Web Apps Product Guide
http://download.microsoft.com/download/2/6/2/26253C22-D8EC-4230-A3ED-E2DEED9E8EBE/Microsoft%20Office%20Web%20Apps%20Product%20Guide_Final.pdf

Office (Web Apps) help and how-to
http://office.microsoft.com/en-us/web-apps-help/

Microsoft Office Web Apps Deployment
http://technet.microsoft.com/en-us/office/ee815687

Description of Office Web Apps SP1
http://support.microsoft.com/kb/2460073

Planning Broadcast Slide Show (Office Web Apps)
http://technet.microsoft.com/library/ff431681(office.14).aspx

Understanding Broadcast Slide Show (Office Web Apps)
http://technet.microsoft.com/library/ff431683(office.14).aspx

A comparison of Office Web Apps in Windows Live SkyDrive, SharePoint 2010 On Premises and SharePoint Online
http://technet.microsoft.com/library/ff925944(office.14).aspx

Office Web Apps overview (Installed on SharePoint 2010 Products)
http://technet.microsoft.com/library/ff431685(office.14).aspx

 

.

4/05/2011

SharePoint: File Types Supported by Office Web Apps

 

I’ve had a few questions about the files and extensions supported by SharePoint’s Office Web Apps.

 

Quick Notes:

Only Office 2007 and later formats supported: docx, xlsx, pptx, etc.

Cannot create new documents, so dotx, etc not supported

 

Details:

Rather than copy and paste someone else's work, I’ll just give you the link!

http://support.microsoft.com/kb/2028380

 

For features that only work in the full client applications see:

http://technet.microsoft.com/en-us/library/ff431682.aspx

 

.

3/20/2011

If you missed SharePoint Cincy 2011…

 

SharePoint Cincy 2011

If you missed SharePoint Cincy 2011 then you missed out on a full day of everything SharePoint! Two fantastic keynote presentations from Microsoft and Kroger, twenty breakout sessions with speakers from all over the country and a fantastic group of sponsors. I have not forgotten the most important group… the attendees! There was networking and social collaboration going on in every room and around every table.

SharePoint Cincy 2012 – March 16th 2012

Add March 16th, 2012 to your calendar.  Towards the end of the day I was frequently asked “when is this going to be done again?”  During the 5:00 update the SharePoint Cincy team announced that due to the success of this first event that they are going to do it again. So, see you in March 2012.

 

Thanks to the speakers

(Notice how many of these are local talent. The Cincinnati area has a strong base of SharePoint expertise!)

Fred J. Studerstuder, Microsoft Corporation
Catherine AllshouseCatherine, The Kroger Company
Tim Beamer, Dell
Scott Brickey, Strategic Data Systems
Mike Buob, Sogeti, USA
Steve Caravajal, Ph.D., Microsoft Corporation
Bill Crider, Ascendum
Mario Fulan, Information Control Corp (ICC)
Rob Joy, K2
Pat Kern, Procter & Gamble, Global Shared Services
Rob Kerr, BlueGranite
Sean McDonough, Idera
Jonathan Mast, SharePoint 911
Matt Morse, PointBridge
Raveen Rajavarma, Ascendum
Mike Smith, MAX Technical Training
Matthew Tallman, Sogeti, USA
Tom Washek, Microsoft
Eric Weissmann, DSC Consulting
Shane Young, SharePoint 911

Thanks to the sponsors and exhibitors

Without these people the event could not happen…

Ascendum
AvePoint
BrainStorm Inc.
CBTS
Center for Applied Informatics @ NKU
Dell
Information Control Corporation
K2
MAX Technical Training
Microsoft
PCMS IT Advisor Group
SDS - Strategic Data Systems
Sogeti
The Circuit

The Cincinnati SharePoint User Group
The Dayton SharePoint User Group

 

.

1/31/2011

SharePoint 2010 Internet Site Upgrade Watch Out!

 

I was just updating the list of regional SharePoint User Groups on the Cincinnati SharePoint User Group web site. I did a web search for each group, and then clicked the link…

Many of the user group web sites looked to be inactive!

But most likely they had updated from a SharePoint 2007 Team Site to SharePoint 2010 Team Site.

 

SharePoint 2010 Team Sites have two home pages!

 

In SharePoint 2007 Team Sites had a single home page named default.aspx. In 2010 Team Sites have a new home page named Home.aspx that is stored in the SitePages library. But… there is still a default.aspx page in the root of the site.

If you started out with a 2007 site then the search engines indexed your site as http://yourURL/default.aspx. The same is true for most people who bookmarked your site or linked to it from their site or blog. When you upgraded to 2010 your new home page is http://yourURL/sitepages/home.aspx, but most of the links pointing to your site point to /default.aspx.

 

Fix it

 

There are a number of ways to fix this…

  • Add a message to the default.aspx file (using a Content Editor Web Part) that the URL has changed, and please update your links.
     
  • Add some JavaScript to the default.aspx file (using a Content Editor Web Part or SharePoint Designer) that auto redirects to the new home page.
     

.

1/29/2011

SharePoint: Method 'Post' of object 'IOWSPostData' failed - Excel 2010 Excel Import problems

 

Updated… New version of Office, same old problem!  If you get the IOWSPostData error while trying to import an Excel range into SharePoint, then you need to patch an Excel macro file. The same fix for Office 2007 will also work for Office 2010.

 

Click here for the updated article…

 

.

1/12/2011

Interesting SharePoint Controls

Recently while reviewing a SharePoint 2010 developer class it occurred to me that the class made no mention of any of the SharePoint controls. So as I get the time I’ll write a description and find a sample or two of use for the more interesting controls. I’ll use this page as a “table of contents” for these articles.

 

These controls are all part of the Microsoft.SharePoint.WebControls namespace.

    http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webcontrols.aspx 

 

Here’s the first two:

 

.

12/15/2010

SharePoint: How to get the SharePoint version from JavaScript

 

Update: I found a JavaScript function that returns the version number. Content below has been updated.

 

Simple question:

I’m writing some JavaScript that will run almost identically in SharePoint 2007 and SharePoint 2010. How can I write an IF statement to test the version?

 

So far I have found no simple answer, but I have found a few that work. Each has an “if” or a “risk”, so pick one that works for you.  If you know a better way, please post a comment below.  I propose three methods:

  • Method 1: Check the “_fV4UI” variable
  • Method 2: Check for an element with “V4” or “s4” in its ID or style
  • Method 3: Get the EXACT (almost) version number
  • Method 4: Call a SharePoint 2010 ECMAScript Class Library Object Method

 

SharePoint Versions: (that I’m interested in…)

  • 2007, also called 3.0 or V3, also called version 12
  • 2010, also called 4.0 or V4, also called version 14
  • and one day 201x, called 5.0 or V5? also called version 15?
  • would also love to get WSS vs MOSS and Foundation vs Server

It would be nice if:

  • something in the page had the version number?  (14.xxx)  (I can’t find it)
  • there’s a JavaScript function in one of the core libraries somewhere? (I can’t find one)  (Update: actually there is in 2010)

Solution requirements:

  • Must be available in all site pages, and ideally in all application pages
  • Must be in all templates
  • Must still be there after major master page branding surgery
  • Should still be useful

A few quick ideas:

  • Look for one of the many controls with a tag with “V4” embedded or one of the CSS classes with “V4” embedded. (Risk? Minimal, but site branders who have really hacked the master page or the styles could mess this up.)
  • Look for a unique JavaScript variable (see _fV4UI below). (Risk? Minimal, but a web search for “_fV4UI” finds a number of articles that mention deleting this from the master pages.)

Method 1: Check the “_fV4UI” variable

 

SharePoint 2010 pages have a JavaScript variable named “_fV4UI” that indicates if the page is using the “V4” navigation (Ribbon).  After an upgrade from SP 2007 this variable will be set to “false”. When the user interface is upgraded to the ribbon this will be set to “true”.

So:

  • if _fV4UI does not exist we probably have SP 2007
  • if _fV4UI does exist we probably have SP 2010
  • will there be a _fV5UI in the next version?  (can only wait and see)

The code:

<script type="text/javascript">
  if ( typeof _fV4UI == "undefined" ) 
  {
    // 2007 code here
  }
  else
  {
    // 2010 code here
  }  
</script>

Pros:

  • Probably the easiest test to do
  • Very simple code
    Can even be reduced to one line:

         var SPversion = (typeof _fV4UI == "undefined") ? "12" : "14";

Cons:

  • Your code must be placed after where SharePoint initializes this variable. Be aware that a number of blog articles mention removing the first instance listed below.

    This is where I found it in a Team Site:
    • Line 13 in the <HEAD> section  (this is the only one you will see in the master page)
    • Line 100 in the <BODY> section  (auto generated by a control)
    • Line 1033 near the end of the page  (auto generated by a control)

 

Method 2: Check for an element with “V4” or “s4” in its ID or style

 

The challenge here is, which one? You will need to pick an element that will reliably exist in all branded and unbranded pages.  Just about everything in the master page is up for grabs when custom branded. (Yes, I have seen branded sites without a title, Quick Launch, Tabs, Search, View All Files and Recycle Bin!) 

The control you pick needs to be towards the top of the page and most likely left behind in a branded master page. So let’s pick one… (let me know if there is a better one)  Both SP 2007 and SP 2010 have a hidden <SPAN> or <DIV> named TurnOnAccessibility. In 2010 this DIV has a style named “s4-notdlg”, which SP 2007 will never have, so let’s test for that:

The code:

<script type="text/javascript">
  if ( document.getElementById("TurnOnAccessibility").className == ""  ) 
  {
    // 2007 code here
  }
  else
  {
    // 2010 code here
  }  
</script>

Pros:

  • Easy to test
  • The tag we are testing is at the very top of the page

Cons:

  • This will probably be one of the first things a brander will remove (mostly as they have no idea what it is for)

What is TurnOnAccessibility for? The dropdown menus in SharePoint, such as the Welcome menu or Site Actions, are dynamically generated and somewhat meaningless to a user with vision problems who is using a screen reading program. When “more accessible mode” is enabled, clicking what usually is a dropdown menu will open a popup window with all of the menu options listed.

 

Method 3: Getting the EXACT (almost) version number

 

Now this is what I really want, and it is sent by SharePoint for every page request, but as part of the HTTP Header.  But… most of what’s in that header is not available to JavaScript.

Here’s what’s sent from SharePoint 2010 in the header:

image

Is that version number right?
    14.0.0.4762  reported in the header
    14.0.4763.1000 reported in Central Admin for SharePoint
    14.0.4763.1000 also reported in CA as the database schema version

This number is what is found in IIS under HTTP Response Headers.

image

Anybody know why it does not match any other SP 2010 version number? 

 

Ok, the number is not the correct version, but it is close!

 

SharePoint 2007 reports:

image

At least this is the correct version!

 

So if JavaScript cannot read this header value, how do we get it? Depends on which browser you are using, so I’m using a routine from an MSDN article to deal with the browser version.

 

The code:

<script type="text/javascript">

  /*
    The following copied from:
    http://msdn.microsoft.com/en-us/library/ms537505(v=vs.85).aspx
  */
  var xmlHttp = null;
  if (window.XMLHttpRequest) {
    // If IE7, Mozilla, Safari, and so on: Use native object.
    xmlHttp = new XMLHttpRequest();
  }
  else
  {
    if (window.ActiveXObject) {
       // ...otherwise, use the ActiveX control for IE5.x and IE6.
       xmlHttp = new ActiveXObject('MSXML2.XMLHTTP.3.0');
    }
  }
  /*
    end copy
  */

  xmlHttp.open('HEAD', location.href, false);
  xmlHttp.send();
  var headers =  xmlHttp.getAllResponseHeaders();
  var SPVersion = xmlHttp.getResponseHeader("MicrosoftSharePointTeamServices");

  if ( SPVersion.substring(0,2) == "12"  ) 
  {
    // 2007 code here
  }
  else
  {
    // 2010 code here
  }  

</script>

Note: The XMLHttpRequest call is usually setup with an asynchronous callback as the URL called is usually not the same URL that contains the calling JavaScript.  The example above does not seem to need this as it appears the header is read from the current copy of the page (“location.href”). Test this in your environment!

 

It would be a good idea to wrap this code as a function and add this to a custom JavaScript library that you would load in the master page. You can then call it as needed from other routines.

function getSharePointMajorVersion()
{
 // The following copied from: http://msdn.microsoft.com/en-us/library/ms537505(v=vs.85).aspx
  var xmlHttp = null;
  if (window.XMLHttpRequest) {
    // If IE7, Mozilla, Safari, and so on: Use native object.
    xmlHttp = new XMLHttpRequest();
  }
  else  {
    if (window.ActiveXObject) {
       // ...otherwise, use the ActiveX control for IE5.x and IE6.
       xmlHttp = new ActiveXObject('MSXML2.XMLHTTP.3.0');
    }
  }
  //  end copy

  xmlHttp.open('HEAD', location.href, false);
  xmlHttp.send();
  var SPVersion = xmlHttp.getResponseHeader("MicrosoftSharePointTeamServices");

  return  SPVersion.substring(0,2) 
}  

 

Pros:

  • Gets the version number, so should also work with the “next version” of SharePoint (15?)
  • Should work regardless of “branded” master page changes
  • Works with the browsers I test with: IE6, IE7, IE8 and FireFox 3.5.10

Cons:

  • A lot of code for a just to see if we are in 2007 or 2010
  • The version number returned is stored in the IIS settings and could get changed independent of SharePoint (I don’t know if service packs update this)
  • The SharePoint 2010 version returned is not 100% correct (but the major version “14” is correct)

 

Method 4: Call a SharePoint 2010 ECMAScript Class Library Object Method

SharePoint 2010 supports a JavaScript client object model that can access lists, libraries and other content. Once of the classes is called SP.ClientSchemaVersions and it has a property called currentVersion that returns a version number. This number is not the version of SharePoint itself, but appears to be the version of the library as it returns “14.0.0.0” only.

So:

  • if “SP.ClientSchemaVersions.currentVersion”does not exist we probably have SP 2007
  • if “SP.ClientSchemaVersions.currentVersion” does exist and starts with “14” then we probably have SharePoint 2010
  • And… if we are lucky “SP.ClientSchemaVersions.currentVersion” will return “15.something” for the next version.

The Code:

<script type="text/javascript">

function SampleFunction()
{
  var SPversion = "12"; 

  try { SPversion = SP.ClientSchemaVersions.currentVersion.substring(0,2) } 
  catch (e) {}

  if (SPversion == "12")
  {
      // 2007 code here
  }
  else
  {
      // 2010 (and later) code here
  }
}

ExecuteOrDelayUntilScriptLoaded( SampleFunction, "sp.js" );

</script>

 

Pros:

  • Gets the version number, so should also work with the “next version” of SharePoint (15?)
  • Should work regardless of “branded” master page changes
  • Works with the browsers I test with: IE6, IE7, IE8 and FireFox 3.5.10

Cons:

  • A lot of code for a just to see if we are in 2007 or 2010
  • The version number returned is for the script library, not SharePoint (but that should be OK)
  • Our code can only be run after the page is fully loaded and the “sp.js” library has been loaded (that’s why we need the ExecuteOrDelayUntilScriptLoaded call)
  • Our code must be wrapped up in a JavaScript function  (SampleFunction in the example above)

 

My Preference?

Right now it is Method 1, Check the “_fV4UI” variable.  It’s simple and light weight. But just remember the variable initialization could get deleted by someone working on the master page.

 

 

 

 Know a better way?  Post a comment below!

 

.

12/12/2010

Visio Services: there are no addresses available for this application

 

While doing a demo for Visio Services in SharePoint 2010 I got the following “perfectly clear and obvious” error message.

image

 

The fix was quite simple… go start the Visio service in Central Administration! 

 

This error occurs for other services, such as the Document ID services and BCS, and the solution is generally the same: start the service and/or make sure the configuration is correct.

 

.

10/07/2010

Chat About Microsoft Office and Windows with Microsoft MVP Experts

 

Office 2010 and Windows 7

 

Chat About Microsoft Office and Windows with Microsoft MVP Experts

October 14, 2010
10:00 A.M. - 11:00 A.M. Pacific Time
Additional Time Zones

Would you like to learn more about the cool new features in Office 2010 and Windows 7 and what has changed since previous versions? Do you use Microsoft Office but would like to learn tips and tricks to be more productive at home, school or at work? Perhaps you are a new user who has questions on how to get started with Windows 7 or using the Office ribbon? Or would like to learn how to protect your computer from malware and viruses. Or perhaps you are just stuck and need answers.

The Microsoft Most Valuable Professionals (MVPs) are here to help!

The MVPs are the same people you see in the technical community as authors, trainers, user groups leaders and answerers in the Microsoft forums. For the first time ever we have brought these experts together as a collective group to answer your questions live. MVPs will be on hand to take questions about Microsoft Office 2010 or Office 2007 products such as Word, Excel, PowerPoint, Outlook, Access, Project, OneNote and more. As well as the Windows 7 and earlier versions such as Windows Vista. In addition to Microsoft Office, the chat will cover Windows related topics such as upgrading, setup and installation, securing your PC, Internet Explorer, personalizing your computer desktop or having fun with Windows Live Essentials to share photos, make movies and more. All levels of experience are welcome from beginners and students to intermediate power users.

Please join us for this informative Q&A style chat and bring on your basic and your tough questions!

Join the Chat!


October 14, 2010

10:00 A.M. - 11:00 A.M. Pacific Time
Additional Time Zones

Add to Calendar

You can follow this on Twitter at #msmvpchat

Join the event on Facebook: Chat about Microsoft Office & Windows with MVP Experts!

 

.

2/26/2008

SharePoint: Excel 2003 Import and Outlook problems (Method 'Post' of object 'IOWSPostData' failed)

 

Updated… New version of Office, same old problem!  If you get the IOWSPostData error the same fix for Office 2007 will also work for Office 2010.

Updated again 2/24/13… This time for SharePoint 2013 and Office 2010.

One of my VPC images for SharePoint is acting up. It has MOSS 2007 and Office 2003. The problems are: Import from Excel fails and Connect To Outlook fails. Another VPC created from the same original setup is fine. The only thing really different with this VPC is that it has SharePoint Designer installed.

Errors from Excel: "object doesn't support this property or method"
Errors from Outlook (not consistent) : "Method 'Post' of object 'IOWSPostData' failed"

What appears to have happened is that SharePoint Designer is an Office 2007 product, it installs a bunch of Office 12 files and must be updating default paths or registry entries to point to Office 12 instead of Office 11. For the Excel issue I think it is loading the Office 12 DLL and calling from an Office 11 Excel macro file. I have not found a workaround yet for the Outlook problem. It works sometime and not others. My research so far (thanks to all of the bloggers out there!) has found at least a fix for the Excel Import problem. This requires an edit to the macro used by SharePoint to perform the import.

  • Open the macro file in Excel (Excel 2003 is ok, or at least worked for me)
      C:\Program Files\Microsoft Office 2007\Office12\1033\EXPTOOWS.XLA
    For Office 2010 find the file here:
      C:\Program Files\Microsoft Office\Office14\1033\EXPTOOWS.XLA
    or
      C:\Program Files (x86)\Microsoft Office\Office14\1033\EXPTOOWS.XLA
    Or just do a search of C: for EXPTOOWS.XLA

    You find that this is a hidden file, so you many need to change Windows Explorer to “Show hidden files”
    You may need administrator rights to save the file:
      - Click Start, All Programs, Microsoft Office
      - Hold down the Shift key and right-click Microsoft Excel
      - Click Run as Administrator
      - In Excel, click File, Open and navigate to C:\Program Files\Microsoft Office\Office14\1033
        and open the EXPTOOWS.XLA file.

     
  • Press Alt-F11 to display the Excel macro editor and the find the EXPTOOWS.XLA file
     
  • Find the line containing "lVer = Application.SharePointVersion(URL)" and change it "lVer = 2".
    (That's LVer, not iVer or 1Ver)

    Update: To play it safe, just add the lVer =2 at the end of the Initialize subroutine:
      image
     
  • Save the file. Click “Save changed and discard signature” to overwrite the old file.

More info here: http://msmvps.com/blogs/obts/archive/2006/12/05/384536.aspx

The only problem with this fix is that when you save the change you lose the digital signature from Microsoft on the macro file.

 

.

Note to spammers!

Spammers, don't waste your time... all posts are moderated. If your comment includes unrelated links, is advertising, or just pure spam, it will never be seen.