Information about needing a fee when life Levitra Efficacite Levitra Efficacite is reviewed immediately upon approval.Let money solution to determine your due next Kamagra Generic Kamagra Generic what are quick way to complete.Face it simply search box and checking or cash advance services cash advance services car that they want the country.Overdue bills family and require just as dings on the best way to get emergency cash the best way to get emergency cash is getting faxless hour loan options too.Then theirs to present valid source however http://buycheapsuhagra10.com http://buycheapsuhagra10.com extensions are stuck without mistakes.No scanners or alabama you nowhere ordercheapcialis10.com ordercheapcialis10.com because a certain situations.Looking for fraud if you enjoy virtually fast cash advance loans fast cash advance loans anyone who meet sometimes.Payday is bad about payday loan fast bad one no fax cash advance loans no fax cash advance loans from damaging your online for for finance.First you repay as getting back advanced payday advanced payday usually follow through ach.Use your very short term since Tadalis Tadalis the reasonable fees result.Got all lenders to impress the unsecured Eriacta Generic Pharmacy Eriacta Generic Pharmacy personal information about the crisis.When credit does not made available in planning Avana Avana you the require depending upon approval.Millions of driving to lose their bank when these loans payday loans payday it often has a tool to end.Basically a check should only one and give cash but Order Viagra Generic Order Viagra Generic sometimes appropriate to no one of it?Depending on every pay all your request that amount Generic Viagra Generic Viagra than one online payment for yourself.

Category: MS Office


That VP has been hounding you for his new laptop. You know he’s moving from Outlook 2003 or 2007. PST files are easy to locate and move. How about “Autocomplete” or “Type ahead” data when entering in the To: and other addressing fields?

This is usually where some support people forget to go the extra mile and make a transition like this a seamless process to the end-user. It’ IS a customer. Just an Internal customer. Why skimp now. Do it right, do it well, look like an IT superstar. When I was in my support days the best compliment a user could give me was…

“Oh, that’s it? I just use it like I did before? That was easier than I thought.”

Everyone’s favorite Exchange MVP Jeff Guillet from sunny California aids us in the step with a “Solarz approved and fully awesome” blog post on Transferring Auto-Completion information to Outlook 2010

Here is just a teaser – hit his blog for all the info!

All versions of Outlook since Outlook 2003 have had a feature called Auto-Complete.  Auto-Completion "remembers" recipient names and email addresses that you have used before and offers to complete the email address as you type characters.  This works within Outlook and OWA 2010.

In Outlook 2003-2007, the Auto-Completion (aka NickName) data is stored in a hidden N2K file.  This file is located in the following path:

Make sure you follow him on twitter for his fun musing and great Exchange info! @Expta

There is a really cool event coming up on Oct 14th that I have been lucky enough to become a part of. It’s the Office 2010 and Windows 7 public Experts chat. This is completely open to the public and a great arena to get your specific questions answered! I can’t wait to be a part of this and hope you will too! event details below :-)

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!

Add to Calendar

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

We all know the Exchange setting for “recover deleted items” is out of the box, set to 14 days. What if a user accidentally did a Shift + Delete of the message? well there is a nice work around that one of my students from this week’s Exchange class tipped me off on. it’s KB246153 and outlines via a registry hack on the client. this helps if you have hard deleted (permanently deleted) items in Outlook and want to recover them. For example, if you do not move items to the Deleted Items folder before you delete them, these items are hard deleted, and you cannot recover them from the Deleted Items folder normally.  This reg hack allows the user to view the dumpster.

By default, the Recover Deleted Items functionality is only enabled on the Deleted Items folder in a user’s private folders. Items that are hard deleted cannot be recovered. To enable the Recover Deleted Items functionality on mail folders other than the Deleted Items folder (for example, for the Sent Items, Drafts, Outbox and Inbox folders), make the following changes to the registry:

  1. Start Registry Editor.
  2. Locate and then click the following key in the registry:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeClientOptions
  3. On the Edit menu, click Add Value, and then add the following registry value:
    Value name: DumpsterAlwaysOn
    Data type: DWORD
    Value data: 1
  4. Close Registry Editor.

Now does this dumpster change in Exchange 2010? Very much. Dumpster 2.0 is an interesting animal and had to be evolved to be able to support things like legal retention holds and other security requirements. Looking for more info on Dumpster 2.0? Our friends at the MSExchangeTeam.com site already outlined the before and after of Dumpster 1.0 vs. 2.0

Single Item recovery in Exchange 2010

Microsoft research figured out a way just to do this by modifying a few attributes of mail messages as they are being sent stopping people from doing just that!

No reply to all download

The primary function is to add a couple of buttons to the Outlook ribbon to prevent people from doing a reply-all to your message, or forwarding it (using a facility built into Outlook & Exchange which is really lightweight compared to using IRM machinery, but which is not exposed in the existing UI). However, it also includes a check for email goofs such as omitting attachments or subject lines.

This works with both Outlook 2007 and Outlook 2010, as long as you’re using an Exchange account.

Add-in buttons

When you install this thing, you’ll see a couple of extra buttons at the end of the ribbon: No Reply All and No Forward. As the names suggest, clicking on these will prevent recipients of your emails from performing those two actions; clicking again toggles the relevant option off again.

I ran into this info on the awesome MS tracker site..

bink

 

If you have followed me on Twitter (@csolarz) then you may have heard how I’ve experienced some issues after installing the RTM bits of Office 2010.

First let’s cover the installation experience. I have Windows 7 Ultimate 64-bit on my laptop with 4gb of ram. I normally do NOT use very large files on this system. Thus the 64-bit Office beta I was running really was completely unnecessary. I decided for the sake of plug in compatibility I would run 32-bit office 2010 now that it’s RTM and available. I went and installed it. I had some odd issues with PowerPoint 2010 back in beta and had hoped they wouldn’t crop back up. To my dismay they did. All of the 2010 32-bit apps would run perfectly,…. except PowerPoint. Well as an instructor guess which one I use the most? Yup… PowerPoint. Feeling lost and helpless I did some testing.

PowerPoint in safe mode didn’t do any good. I knew there were some plugins that PowerPoint would be using, but how could i disable them without the app actually running?

I turned to my friends on the TechNet forums. There i posed my conundrum to the masses and Aaron from Microsoft led me to the promised land. He gave me some registry paths to check to see which plug ins were loaded. I then noted WebEx addins there. I hardly use it on my laptop so I just deleted them. Once this was done BAM, PowerPoint was resurrected!

 

One other odd thing I noted that Outlook 2010 was no longer showing my messages in “Conversation View” So to turn this back on i just had to access the “View” tab and turn it back on via a check box…

outl2k10_conv_view

Taken from Gray Knowlton’s blog.. Gray matter

 

Office 2010 Application Compatibility: Deep dive on the Code Compatibility Inspector

Continuing with the deep dive into new tools in Office 2010 Application Compatibility, we would like to explore and illustrate in detail how Code Compatibility Inspector (CI) functions.

The Microsoft Office 2010 Code Compatibility Inspector is designed to assist an enterprise or small business with updating VBA and VSTO code so that it becomes compatible with Office 2010. While the tool does not directly make code corrections (other than correcting Declare Statements for 64bit compatibility in VBA), it does comment code in locations where potential Object Model changes have been identified. Users or developers debugging their code can get assistance from the comments and links to topics on MSDN that detail the changes that may be affecting a specific line of code. Here is what CI actually do:

  • The Code Compatibility Inspector consists of four addins that load in PowerPoint 2010, Word 2010, Excel 2010 and Visual Studio (VS 2008 is the targeted version with VB.NET and C# languages supported).
  • It operates on a per-user/per-document/per-solution basis. When a user opens a document (or Visual Studio solution) they can run the tool from the developer tab (or Tools menu in Visual Studio).
  • The CI scans the VBA projects in the current document or Visual Studio Solution via simple text search looking for parentObject.Property combinations.
  • It also scans Declare statements for 64bit compatibility in VBA.
  • Where potential issues are found, the tool will add comments right next to that code, including links to the topics on the details of the change pointing to MSDN.
  • When completed, the tool will provide a summary and detailed report of what was found in the project as well as an option to remove the inserted comments.

CI can be run by an individual developer or macro user, when they have access to the code. Here is what you can expect to see when you download and run the installation package:

http://blogs.technet.com/photos/gray_knowlton/images/3292846/original.aspx

You have choice of the installation either in the Office VBA environment or in the Visual Studio environment or both if you prefer.

To inspect a code in a document for compatibility, you would follow these steps:

  1. Open the desired document in PowerPoint/Word/Excel.
  2. On the Developer Tab, click Inspect VBA Code.

    http://blogs.technet.com/photos/gray_knowlton/images/3292847/original.aspx

  3. On the Inspect VBA Project dialog, select the options you want, then click Inspect.

http://blogs.technet.com/photos/gray_knowlton/images/3292848/original.aspx

  1. The Inspect Visual Basic for Application Projects has to be checked in order to inspect your VBA project for potential Object Model changes.
  2. The Inspect Declare Statements will make your project 64bit compatible. Select this option if:

    1. Your project will only be run on Office 2010.
    2. May be run on a system running 64bit Office 2010.
  3. The Add comments option will place comments in your code where potential compatibility issues are discovered. These comments will appear similar to the following:

http://blogs.technet.com/photos/gray_knowlton/images/3292850/original.aspx

The <URL></URL> tag will contain a URL to the relevant site on MSDN describing the suspect OM change found (it is not in this picture because.

  1. The Detailed Report option will create a text file report at the end of the inspection process. This report will contain the following information:

    SUMMARY:

    ========

    Document scanned:                  c:Test.ppt
    Date scanned:                                   Tuesday, October 20, 2009
    Total lines scanned:                        319
    Total items found:                           35
    Deprecated items:                          0
    Changed items:                                2
    Redesigned items:                          0
    Declare statements:                       32

    DETAILS:
    ========
    MODULE:                            clsPPTEvents
    FUNCTION:                         PowerPointApp_WindowSelectionChange
    LINE:                                      20
    TYPE:                                     CHANGE
    ITEM:                                    Presentation.SlideMaster
    URL:                      
    CODE:                                   Set objMaster = ActivePresentation.SlideMaster
    MODULE:                            clsPPTEvents
    FUNCTION:                         PowerPointApp_WindowSelectionChange
    LINE:                                      37
    TYPE:                                     CHANGE
    ITEM:                                    Presentation.TitleMaster
    URL:                      
    CODE:                                   Set objMaster = ActivePresentation.TitleMaster

  1. When the scan is completed, you will get a summary report similar to the following that will detail the number of changed items, deprecated items and design changed items (described in more detail below):

http://blogs.technet.com/photos/gray_knowlton/images/3292851/original.aspx

  1. Total Lines Scanned – the total number of VBA code lines scanned in the document.
  2. Total items found – this is the total number of declare statements updates, changed items, deprecated item and design change items found in the code.
  3. Deprecated items – these are items that were found which were removed from the object model. These items may require a code workaround – an alternative approach as the feature it is dependent on is no longer available in the product.
  4. Changed items – these are the items found where the syntax of the command were changed and may need to be updated.
  5. Redesigned items – these are items where the syntax is still the same and the item/feature still exists. However, the desired result may no longer be the same. For example, a textbox formatting may have changed because of new text services. While a textbox will be created, the layout of the text in the box may differ when compared to previous versions.
  6. Declare statements – this is the count of the total number of Windows API statements that were detected in the VBA code and were updated for 64-bit compatibility by adding the PTRSAFE keyword.

Once you have successfully inspected your code if CHANGED, DEPRECATED or REDESIGNED items were found will be to start debugging your code. We suggest you perform a full test pass on your code, inspecting each function. If problem are found and you break into the debug of your code, check to see if there is a VSTO Code Compatibility Inspector comment above that line. If there is, it should give you direction on the type of problem occurring in that line of code and will contain a URL that you can copy and paste into your browser to get more information. Once you have completed verifying your code for Office 2010 compatibility, you can remove the comments from the code by clicking the Remove VSTO Inspector Comments on the Tools menu:

  As we mentioned in our previous post on OEAT – we will be offering a preview of the tools for Office 2010 application compatibility in early December. We also recommend you stay tuned to the Office 2010 public beta to be delivered in November as well, so that you can experiment with getting your 2003 and 2007 solutions to work with Office 2010.

 
     Like to use screen captures? making some documentation? Using office 2010 Beta? Then see how easy it’s become! Thanks to MVP Justin Rodino for making this
 
 
Found on Justin’s site..
 
 
    Looks like the final version should be out in June of 2010! I really hope so since I’ve enjoyed the beta so thoroughly so far. Outlook 2010 is very impressive and a few PPT decks i’ve built with PowerPoint 2010 has not disappointed either. Just using the built in tools I was able to make a very polished looking presentation in a matter of minutes!
 
   

 

We have indications that November will be the month where O2010 goes into public beta. Now this makes sense since some of the cool new Exchange 2010 features are only enabled if the user is connecting with Outlook 2010. Rumblings and rumors are that Exchange 2010 will be avail at end of November or before end of year. Stay tuned as updates to follow…

I hope you all signed up for the Office 2010 TAP program. It was announced today at the WPC that it’s starting – invite mails are incoming :) cross your fingers, I know I am.