Formula errors in Excel when list separater is not set correctly
“We found a problem with this formula. Try clicking Insert Function on the Formulas tab to fix it, or click Help for more info on common formula problems.”
- The list separator in Windows – Regional Settings does not match what is being typed for the Excel formula.
- The ‘Use system separators’ option is set in Excel Advanced Options and does not match what is being typed for the Excel formula.
If the ‘Use system separators’ is enabled then look in the Region (Regional) Settings in the Windows Control Panel. The list separator is specified in the Additional settings.
2. Use the same character as the designated list separator in Windows settings when creating the formula(s).
3. Use the Reset button to reset the options to match the default for the selected country or modify the Windows List Separator to a different character (some special characters cannot be used).
(http://office.microsoft.com/en-us/excel-help/change-the-separator-for-thousands-and-decimals-HP003089676.aspx)
Note: The comma is the default list separator for US – English Locale.
More information
Changing the List separator in the Windows Region settings will affect the delimiter used when opening or saving a Comma-separated value (.csv) file as Excel utilizes the Windows list separator character for the delimiter in .csv files.
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.
Article ID: 2853427 – Last Review: May 23, 2013 – Revision: 1.0
View the original here:
Formula errors in Excel when list separater is not set correctly
How to find a Web Presence Provider for your FrontPage 2000 Web
the Web that you created in Microsoft FrontPage on the Internet.
Several features of your Web require the FrontPage Server Extension to be
installed on the server hosting your Web. Some features may not function if
they are hosted on a server that does not support the FrontPage Server
Extensions.
How to see the latest list of WPP referrals
- Open a Web in FrontPage.
- On the File menu, click Publish Web.
- Click WPP’s.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/151725/
)
How to import Web content from a server without Front Page Extensions
Article ID: 196247 – Last Review: May 23, 2013 – Revision: 3.0
| kbhowto kbhowtomaster KB196247 |
See the original article here:
How to find a Web Presence Provider for your FrontPage 2000 Web
OWA redirection and SSL offloading fail after you install an Exchange Server service pack
Note By default, the “Require SSL” configuration option is enabled on the default website when you install an Exchange Server service pack. Additionally, the “Require SSL” configuration is enabled on the virtual directories under the default website.
- Start IIS 7 Manager.
- Select the default website, and then make sure that you are in Features View.
- Double-click SSL Settings.
- Click to clear the Require SSL check box.
- Run the IISRESET command.
- Repeat steps 1 through 5 for all virtual websites under the default website.
For more information about issues that can occur when you use a third-party SSL offloader in an Exchange Server 2007 environment, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/945453/
)
You cannot log on to Outlook Web Access in an Exchange Server 2007 environment, and you receive an error message: “HTTP Error 403.4″
Article ID: 2839692 – Last Review: May 22, 2013 – Revision: 1.0
Applies to
- Microsoft Exchange Server 2007 Service Pack 1
- Microsoft Exchange Server 2007 Service Pack 2
- Microsoft Exchange Server 2007 Service Pack 3
- Microsoft Exchange Server 2010 Service Pack 1
- Microsoft Exchange Server 2010 Service Pack 2
- Microsoft Exchange Server 2010 Service Pack 3
| kbsurveynew kbprb kbfix KB2839692 |
Read More:
OWA redirection and SSL offloading fail after you install an Exchange Server service pack
USB device is not recognized when you attach it immediately after your Windows XP-based computer resumes from standby or hibernation
Unrecognized device has been found.
- Host controller hardware
- Attached hubs
- Attached devices
- USB driver versions
- Support for USB 2.0
- Additional system hardware or configurations that may change the timing
For other causes that prevent a USB device from being detected, go to the “Similar Problems and Solutions” section to view related Microsoft Knowledge Base articles.
Method 1: Initiate recognition of the USB device by using Device Manager
To initiate recognition of the USB device by using Device Manager, follow these steps:
- Click Start, click Run, type Devmgmt.msc, and then click OK. The Device Manager window opens.
- Click to select your computer as the location for the scan.
- On the Action menu, click Scan for hardware changes.
Windows XP recognizes the new device.
- Close the Device Manager window.
If this method resolves the issue, you are finished.
If this method does not resolve the issue, go to method 2.
Method 2: Disable power management of the USB hub
Note If you perform the following procedure, you may also reduce the battery life on a portable computer.
Use this method if method 1 does not work. To disable power management of the USB hub, follow these steps:
- Click Start, click Run, type Devmgmt.msc, and then click OK. The Device Manager window opens.
- Expand Universal Serial Bus controllers.
- Right-click a USB Root Hub in the list, and then click Properties. The USB Root Hub Properties dialog box is displayed.
- Click the Power Management tab.
- Click to clear the Allow the computer to turn off this device to save power check box, and then click OK.
- Repeat steps 3 through 6 for each USB Root Hub in the list.
- On the Action menu, click Scan for hardware changes.
Windows XP recognizes the new device.
- Close the Device Manager window.
If this method does not resolve the issue, go to method 3.
Method 3: Restart the computer
To initiate recognition of the USB device, first unplug the USB device and restart the computer. Then, wait five to ten seconds before you plug the USB device into the computer or hub.
Windows XP recognizes the new device.
If this method does not resolve the issue, you might want to review the articles in the “Similar Problems and Solutions” section, or contact Support. For information about how to contact Support, visit the following Microsoft Web site:
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.
For more information about advanced troubleshooting tips for general USB problems, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/310575/
)
Advanced troubleshooting tips for general USB problems in Windows XP
For more information about how to troubleshoot unknown devices in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/314464/
)
How to troubleshoot unknown devices that are listed in Device Manager in Windows XP
If these articles do not resolve the issue, visit the following Microsoft Web site for information about how to contact Support:
Article ID: 871233 – Last Review: May 22, 2013 – Revision: 4.0
Applies to
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Professional
- Microsoft Windows XP Tablet PC Edition
- Microsoft Windows XP Media Center Edition 2004
- Microsoft Basic Optical Mouse
- Microsoft Comfort Optical Mouse 1000
- Microsoft Comfort Optical Mouse 3000
- Microsoft Habu Laser Gaming Mouse
- Microsoft IntelliMouse Explorer 4.0
- Microsoft Laser Mouse 6000
- Microsoft Natural Ergonomic Keyboard 4000
- Microsoft Compact Optical Mouse 500 v2.0
- Microsoft Comfort Curve Keyboard 2000
- Microsoft Wireless Laser Desktop 6000 v2.0
- Microsoft Mobile Memory Mouse 8000
- Microsoft Natural Wireless Laser Mouse 6000
- Microsoft Notebook Optical Mouse 3000
- Microsoft Optical Mouse by Starck
- Microsoft SideWinder Mouse
- Microsoft Wireless IntelliMouse Explorer with Fingerprint Reader
- Microsoft Wireless Laser Mouse 6000
- Microsoft Wireless Laser Mouse 7000
- Microsoft Wireless Laser Mouse 8000
- Microsoft Wireless Notebook Laser Mouse 6000
- Microsoft Wireless Notebook Laser Mouse 7000
- Microsoft Wireless Laser Mouse 5000
| kbresolve kbtshoot kbpowerman kbusb kbprb KB871233 |
"The Windows Installer Service Could Not Be Accessed" error message when you install a program in Windows XP
oneMscomBlade,oneMsomNav,oneMscomFooter,
See more here:
"The Windows Installer Service Could Not Be Accessed" error message when you install a program in Windows XP
Description of Microsoft Product Activation
For more information about how to contact the Microsoft Product Activation Center, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/950929/
)
How to contact the Microsoft Product Activation Center
Casual copying accounts for a large part of the piracy losses that the software industry experiences. If software piracy were to be reduced, the software industry could invest much more money in product development, in product quality, and in product support. This would lead to better products and more innovation for customers.
How product activation works
Product activation is a simple, straightforward process that is completely software based. It requires no hardware add-ons or any other external tool. In most cases, the only information that is needed to activate a product is an installation ID, which is created by the software itself. The information that is collected during activation will not be used to personally identify the user.
If you activate your product over the Internet, product activation takes less than a minute. When you activate your product in this way, the product itself will do most of the work. Very little user effort is required. If you would rather activate your product over the telephone, you can do this by contacting the regional Microsoft Product Activation Center.
For more information about how to contact the Microsoft product activation Center, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/950929/
)
How to contact the Microsoft product activation Center
Important Product activation does not track users of Microsoft software in any way. Its sole purpose is to activate legitimate licenses for Microsoft software.
When to activate a Microsoft product
Software that is bought in stores or as part of a new computer that is sold by an OEM must be activated. As mentioned earlier, product activation is easy, and many users only have to activate a product one time during the life of the product. However, some products may have to be activated again if the product is moved to another computer or if significant changes are made to the computer on which the product is installed.
Note OEMs may activate the software at the factory before they deliver the computer to the customer.
To make activation convenient, Microsoft products do not have to be activated immediately after they are installed. You can start Microsoft Office up to 50 times before you have to activate it. For Microsoft Windows, you have 30 days from the first time that you use the operating system before you have to activate it.
How to activate a Microsoft product
To activate a Microsoft product, select either the Internet option or the telephone option in the Product Activation Wizard.
- With Internet-based activation, Microsoft servers process the activation and activate the product.
- With telephone-based activation, you activate your product by contacting a Microsoft Product Activation Center and following the steps that are provided by an automated telephone system or by a customer service representative.
Important You should have your installation ID when you speak with a customer service representative. This ID is displayed in the product activation wizard.
For more information about how to contact the Microsoft product activation Center, click the following article number to view the article in the Microsoft Knowledge Base:
950929(http://support.microsoft.com/kb/950929/
)How to contact the Microsoft product activation Center
Web sites
For more information, visit the following Microsoft Web sites:
Microsoft Knowledge Base articles
For more information about how to contact a Microsoft Product Activation Center, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/950929/
)
How to contact the Microsoft product activation Center
(http://support.microsoft.com/kb/299840/
)
How to use Sysprep with Windows product activation or Volume License media to deploy Windows XP
(http://support.microsoft.com/kb/291997/
)
How to activate Windows XP using an Unattend.txt file
(http://support.microsoft.com/kb/300273/
)
Cannot activate OEM edition more than once in Office XP
(http://support.microsoft.com/kb/298088/
)
How to obtain a Volume License key for Enterprise Editions of Office XP
(http://support.microsoft.com/kb/293477/
)
Information about the Microsoft Activation Wizard Privacy Policy for Visio
(http://support.microsoft.com/kb/293466/
)
Reduced functionality, missing menu commands, and unavailable features in Visio
(http://support.microsoft.com/kb/299056/
)
An error message is displayed when you run Windows product registration
(http://support.microsoft.com/kb/289657/
)
Out of Box Experience (OOBE) does not run after Setup completes
Article ID: 302806 – Last Review: May 22, 2013 – Revision: 17.0
Applies to
- Customer Service and Support Information
- Windows Vista Home Premium 64-bit Edition
- Windows Vista Home Basic 64-bit Edition
- Windows Vista Ultimate 64-bit Edition
- Windows Vista Business
- Windows Vista Business 64-bit Edition
- Windows Vista Home Basic
- Windows Vista Home Premium
- Windows Vista Starter
- Windows Vista Ultimate
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows XP Professional
- Microsoft Windows XP Home Edition
- Microsoft Windows Small Business Server 2003 Premium Edition
- Microsoft Windows Small Business Server 2003 Standard Edition
- Microsoft Office Basic 2007
- Microsoft Office Home and Student 2007
- Microsoft Office Standard 2007
- Microsoft Office Professional 2007
- Microsoft Office Professional Plus 2007
- Microsoft Office Ultimate 2007
- Microsoft Office Word 2007
- Microsoft Office Visio Standard 2007
- Microsoft Office InfoPath 2007
- Microsoft Office Publisher 2007
- Microsoft Office Project Professional 2007
- Microsoft Office Project Standard 2007
- Microsoft Office PowerPoint 2007
- Microsoft Office Outlook 2007
- Microsoft Office OneNote 2007
- Microsoft Office Excel 2007
- Microsoft Office SharePoint Designer 2007
- Microsoft Office Professional Edition 2003
- Microsoft Office Access 2003
- Microsoft Office Excel 2003
- Microsoft Office FrontPage 2003
- Microsoft Office Outlook 2003
- Microsoft Office PowerPoint 2003
- Microsoft Office Publisher 2003
- Microsoft Office Small Business Edition 2003
- Microsoft Office Basic Edition 2003
- Microsoft Office XP Developer Edition
- Microsoft Office XP Professional Edition
- Microsoft Office XP Proofing Tools Standard Edition
- Microsoft Office XP Small Business Edition
- Microsoft Office XP Standard Edition
- Microsoft Access 2002 Standard Edition
- Microsoft Excel 2002 Standard Edition
- Microsoft FrontPage 2002 Standard Edition
- Microsoft Outlook 2002 Standard Edition
- Microsoft PowerPoint 2002 Standard Edition
- Microsoft Word 2002
| kmcustomerservice kbresolve kbmsccsearch kbpubtypekc kbenv KB302806 |
Follow this link:
Description of Microsoft Product Activation
How to create a Smart Tag DLL in Visual Basic for use in Office XP
This article was previously published under Q286267
provide Office users more interactivity with the content of their Office
documents. A Smart Tag is an element of text in an Office document that is
recognized as having custom actions associated with it. An example of one of
these special elements of text might be an e-mail name that is typed into a
Word document or an Excel workbook. If the e-mail name is recognized as a Smart
Tag, the user is presented with one or more actions to perform on the given
text. Possible actions associated with an e-mail name are to look up additional
contact information, or send a new e-mail message to that contact.
You can extend the capabilities of Office XP by developing your own Smart Tag
Recognizer/Action dynamic-link library (DLL) for use in Office documents. This
article describes how to build a Smart Tag DLL by using Visual Basic 6.0 and
discusses what registry settings are required for Office XP to identify and use
your Smart Tag DLL.
Note Excel 2002 and Word 2002 are the only Office XP applications
that support Smart Tags. However, you can apply the information that is
presented in this article to Smart Tag development for any application that
adopts the Smart Tag technology.
A Smart Tag DLL is a standard
Component Object Model (COM) DLL that implements two special interfaces: ISmartTagRecognizer and ISmartTagAction. The ISmartTagRecognizer interface is responsible for recognizing text that is typed into
a document as a Smart Tag. The ISmartTagAction interface is responsible for performing actions on a particular
Smart Tag string at the user’s request. It is not required that these
interfaces be implemented in the same DLL. You can have a recognizer DLL and
one or more action DLLs that extend a single Smart Tag type for different
actions.
Create the Smart Tag DLL in Visual Basic
The following steps create a simple Smart Tag DLL that recognizes the Microsoft Network (MSN) Instant Messenger contacts and gives the user the ability to send e-mail or instant messages to a recognized contact. Instant Messenger is required to use this sample.
- In Visual Basic, create a new ActiveX DLL
project. - On the Project menu, click Project1 Properties. Change the project name to MessengerSmartTag, and then click OK.
- On the Project menu, click References. Select the Microsoft Smart Tags 1.0 Type Library and the MSN Messenger 1.0 Type Library, and then click OK.
Note If the specified type libraries are not listed, you can browse
for them. The default location for the Microsoft Smart Tags 1.0 Type Library is
C:Program FilesCommon FilesMicrosoft SharedSmart TagMstag.tlb, and the default
location for the MSN Messenger 1.0 Type Library is C:Program
FilesMessengerMsmsgs.exe. - Change the name of Class1 to Action.
- Paste the following code into the code window for the Action class:
Private Declare Function ShellExecute Lib "shell32.dll" Alias _ "ShellExecuteA" (ByVal hwnd As Long, ByVal lpOperation As String, _ ByVal lpFile As String, ByVal lpParameters As String, _ ByVal lpDirectory As String, ByVal nShowCmd As Long) As Long Implements ISmartTagAction Private Property Get ISmartTagAction_ProgId() As String ' Return the ProgID of the Action interface. ISmartTagAction_ProgId = "MessengerSmartTag.Action" End Property Private Property Get ISmartTagAction_Name(ByVal LocaleID As Long) As String ' Return a short name describing the Action. ISmartTagAction_Name = "Messenger Smart Tag" End Property Private Property Get ISmartTagAction_Desc(ByVal LocaleID As Long) As String ' Return a long description describing the action. ISmartTagAction_Desc = "Provides actions for the Messenger Smart Tag" End Property Private Property Get ISmartTagAction_SmartTagCount() As Long ' Return the number of Smart Tags this action supports. ISmartTagAction_SmartTagCount = 1 End Property Private Property Get ISmartTagAction_SmartTagName( _ ByVal SmartTagID As Long) As String ' This method is called the same number of times as you ' return in SmartTagCount. This method sets a unique name ' for the Smart Tag. ISmartTagAction_SmartTagName = "microsoft/messenger#contacts" End Property Private Property Get ISmartTagAction_SmartTagCaption( _ ByVal SmartTagID As Long, ByVal LocaleID As Long) As String ' This caption is displayed on the menu for the Smart Tag. ISmartTagAction_SmartTagCaption = "Messenger Smart Tag" End Property Private Property Get ISmartTagAction_VerbCount( _ ByVal SmartTagName As String) As Long ' Return the number of verbs we support. If (SmartTagName = "microsoft/messenger#contacts") Then ISmartTagAction_VerbCount = 2 End If End Property Private Property Get ISmartTagAction_VerbID( _ ByVal SmartTagName As String, ByVal VerbIndex As Long) As Long ' Return a unique ID for each verb we support. ISmartTagAction_VerbID = VerbIndex End Property Private Property Get ISmartTagAction_VerbCaptionFromID( _ ByVal VerbID As Long, ByVal ApplicationName As String, _ ByVal LocaleID As Long) As String ' Get a caption for each verb. This caption is displayed ' on the Smart Tag menu. Select Case VerbID Case 1 ISmartTagAction_VerbCaptionFromID = _ "Send this contact an Instant Message" Case 2 ISmartTagAction_VerbCaptionFromID = _ "Send email to this contact" End Select End Property Private Property Get ISmartTagAction_VerbNameFromID( _ ByVal VerbID As Long) As String ' Return a string name for each verb. Select Case VerbID Case 1 ISmartTagAction_VerbNameFromID = "SendInstantMessage" Case 2 ISmartTagAction_VerbNameFromID = "SendEmail" End Select End Property Private Sub ISmartTagAction_InvokeVerb(ByVal VerbID As Long, _ ByVal ApplicationName As String, ByVal Target As Object, _ ByVal Properties As SmartTagLib.ISmartTagProperties, _ ByVal Text As String, ByVal Xml As String) ' This method is called when a user invokes a verb ' from the Smart Tag menu. Dim oMessenger As Messenger.IMessengerApp2 Dim oMsgrObj As Messenger.MsgrObject Dim oUsers As Messenger.IMsgrUsers Dim oUser As Messenger.IMsgrUser Dim i As Integer ' Create an instance of Instant Messenger. Set oMessenger = CreateObject("Messenger.MessengerApp") Set oMsgrObj = CreateObject("Messenger.MsgrObject") ' Get a list of contacts. Set oUsers = oMsgrObj.List(0) ' Loop through the contacts. For i = 0 To oUsers.Count - 1 ' Set a specific contact. Set oUser = oUsers(i) ' Check to see if the contact is the correct one. If LCase(oUser.FriendlyName) = LCase(Text) Then Select Case VerbID Case 1 ' The user wants to display the Instant Message ' box to send the contact a message. oMessenger.LaunchIMUI oUser Case 2 ' Shell the "mailto" protocol to start the ' user's mail program and create a new message. ShellExecute 0&, "open", "mailto:" & oUser.EmailAddress, _ vbNullString, vbNullString, 1 End Select End If Next End Sub - Add a new class to the project, and change the class name
to Recognize. Paste the following code in the code window for the Recognize class:Implements ISmartTagRecognizer Dim Contacts() As String Private Sub Class_Initialize() Dim oMsgrObj As Object Dim oUsers As Object Dim oUser As Object Dim i As Integer ' Create an instance of Instant Messenger. Set oMsgrObj = CreateObject("Messenger.MsgrObject") ' Get a list of contacts. Set oUsers = oMsgrObj.List(0) ' Loop through the contacts. For i = 0 To oUsers.Count - 1 ' Set the user. Set oUser = oUsers(i) ' Redimension the array for the new contact. ReDim Preserve Contacts(i) ' Add the user to the contacts list (in lower case). Contacts(i) = LCase(oUser.FriendlyName) Next End Sub Private Property Get ISmartTagRecognizer_ProgId() As String ' Return the ProgID of the Recognizer interface. ISmartTagRecognizer_ProgId = "MessengerSmartTag.Recognizer" End Property Private Property Get ISmartTagRecognizer_Name(ByVal LocaleID As Long) As String ' Return a short title about your recognizer. ISmartTagRecognizer_Name = _ "Microsoft Messenger Contacts Visual Basic Recognizer" End Property Private Property Get ISmartTagRecognizer_Desc(ByVal LocaleID As Long) As String ' Return a long description of your recognizer. ISmartTagRecognizer_Desc = _ "Microsoft Messenger recognizes your Instant Messenger Contacts" End Property Private Property Get ISmartTagRecognizer_SmartTagCount() As Long ' Return the number of Smart Tags that you support. ISmartTagRecognizer_SmartTagCount = 1 End Property Private Property Get ISmartTagRecognizer_SmartTagName( _ ByVal SmartTagID As Long) As String ' This method is called the same number of times as you ' return in SmartTagCount. This method sets a unique name ' for the Smart Tag. ISmartTagRecognizer_SmartTagName = "microsoft/messenger#contacts" End Property Private Property Get ISmartTagRecognizer_SmartTagDownloadURL( _ ByVal SmartTagID As Long) As String ' Return the URL that gets embedded in documents. ISmartTagRecognizer_SmartTagDownloadURL = nil End Property Public Sub ISmartTagRecognizer_Recognize(ByVal Text As String, _ ByVal DataType As SmartTagLib.IF_TYPE, ByVal LocaleID As Long, _ ByVal RecognizerSite As SmartTagLib.ISmartTagRecognizerSite) ' The Recognize method is called and passed a text value. ' You should recognize strings in the text and set up the actions. Dim i As Integer Dim startpos As Integer Dim strlen As Integer Dim propbag As SmartTagLib.ISmartTagProperties ' Convert the text to lower case. Text = LCase(Text) ' Loop through all contacts. For i = 0 To UBound(Contacts) ' Look for a contact name in the text. startpos = InStr(Text, Contacts(i)) ' Find the length of the contact name. strlen = Len(Contacts(i)) ' Look for all occurrences of contacts in the string While (startpos > 0) ' Create a new property bag. Set propbag = RecognizerSite.GetNewPropertyBag ' Commit the Smart Tag to the property bag. RecognizerSite.CommitSmartTag "microsoft/messenger#contacts", _ startpos, strlen, propbag ' Continue looking for contacts in the string. startpos = InStr(startpos + strlen, Text, Contacts(i)) Wend Next i End Sub - Compile and build the DLL.
Register the Smart Tag DLL
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Before you can use any Smart Tag DLL, it must be
registered on the system. Normal COM registration is done for you when you
compile the project, distribute the DLL with the Package and Deployment Wizard,
or call Regsvr32.exe with the DLL name. You must create additional registry
entries that are not part of normal COM registration so that Office
applications can identify the DLL as a Smart Tag DLL. To do this, follow these
steps:
- From a command line, start Regedit.exe.
- Locate the following key in the registry:
HKEY_CURRENT_USERSoftwareMicrosoftOfficeCommonSmart TagActions
- Add a new subkey named MessengerSmartTag.Action.
- Locate the following key in the registry:
HKEY_CURRENT_USERSoftwareMicrosoftOfficeCommonSmart TagRecognizers
- Add a new subkey named MessengerSmartTag.Recognize.
- Close the Registry Editor.
Test the Smart Tag DLL
Smart Tags obey the same security model as macros. If the
security settings of the application are set to High, the Smart Tag DLL will
not load unless the DLL is digitally signed (as do VBA macros). For more
information on digital signing, see the “References” section.
To test
the custom Smart Tag Recognizer/Action DLL in Word, follow these steps:
- Start Instant Messenger, and log on.
Note The sample Smart Tag requires that you log on to Instant
Messenger. If you are not logged on to Instant Messenger, the custom DLL loads
but does not recognize any contacts. - Start Word 2002. On the Tools menu, point to Macro, and then click Security. Set the macro security to Medium, and then click OK. If the macro security setting was previously set to High, restart Word.
- Type the friendly name of a contact in a new document (for
example, John Smith), and then press ENTER. A faint line appears beneath the
friendly name to indicate that it is recognized as a Smart Tag. Move the mouse
over the friendly name, and the Smart Tag Action button appears. - Click the Smart Tag button, and select one of the custom
action items from the drop-down menu. You can send an e-mail or instant message
to the contact from your new document.
You can use similar steps to test the Smart Tag DLL in Excel
2002.
Troubleshooting
If you have problems getting your custom Smart Tags to work,
first check that the custom Smart Tag DLL is being loaded. In Word or Excel, on
the Tools menu, click Auto Correct Options, click the Smart Tag tab, and ensure that the Label Text with Smart Tags check box is selected and that your Smart Tag DLL is listed and
selected. If your Smart Tag is not listed, it may not be properly
registered.
If the execution of the custom Recognizer or Action class is the source of the problem, you can debug a Smart Tag DLL
as you would any Visual Basic COM DLL. Run the DLL from the Visual Basic
Integrated Development Environment (IDE), and click Wait for components to be created if you are prompted for a debug method. Set a breakpoint in the Initialize event for the class item that you want to debug. When Excel or
Word starts and loads the Smart Tag, your code breaks at the breakpoint, and
you can step through the code for debugging.
Your Smart Tag DLL
should trap and handle any run-time errors. If a Visual Basic error is raised
in your code and the error is not handled, Office immediately unloads the DLL
and clears the item so that it is not loaded again. This behavior is identical
to the way that Office treats COM Add-Ins and can give you the impression that
Office is not loading the DLL when it is in fact doing so but was forced to
unload it because of an unhandled run-time error.
type library that defines them, is provided in the Smart Tag Software
Development Kit (SDK). If you have not already done so, you should install the
Smart Tag SDK before you proceed with the steps to create the sample Smart Tag.
You can obtain the Smart Tag SDK from the Microsoft Office XP Developer (MOD)
CD-ROM, or you can download it from the following MSDN Web site: For more information on creating custom Smart Tag
Recognizer/Action DLLs, see the Smart Tag Development Help file included with
Smart Tag SDK.
For more information about digital signatures, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about using CLSIDs to register the Smart Tag DLL instead of ProgIDs, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/294422/
)
BUG: Status flag is not updated when you enable or disable Smart Tags
Continued here:
How to create a Smart Tag DLL in Visual Basic for use in Office XP
The Generic Description field in Integration Manager is overwritten by the Generic Description field in the Class ID window when you import new items into Microsoft Dynamics GP
Integration Manager for Microsoft Dynamics GP 9.0
To resolve this problem, obtain the latest service pack for Integration Manager for Microsoft Dynamics GP 9.0. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.
Partners
Customers
Integration Manager for Microsoft Business Solutions – Great Plains 8.0
To resolve this problem, obtain the latest service pack for Integration Manager for Microsoft Business Solutions – Great Plains 8.0. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.
Partners
Customers
Integration Manager for Microsoft Dynamics GP 9.0
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. This problem was first corrected in Integration Manager Service Pack 3 for Microsoft Dynamics GP 9.0.
Integration Manager for Microsoft Business Solutions – Great Plains 8.0
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. This problem was first corrected in Integration Manager Service Pack 5 for Microsoft Business Solutions – Great Plains 8.0.
This problem occurs only if the destination edit mode in Integration Manager is set to Insert Only. This problem does not occur if the destination edit mode is set to Update Only.
The 2008 year-end update (round 2) is available for Canadian Payroll in the French-Canadian (FRCA) version of Microsoft Dynamics GP 10.0
Update information
Problems that are fixed in this update
After you apply the 2008 year-end update for Canadian Payroll in the FRCA version of Microsoft Dynamics GP 10.0, the value in the Quebec Basic Amount field and the value in the Total Deduction Amount field are not set as expected when you perform the Reset Masters process. Therefore, if you use the FRCA version of Microsoft Dynamics GP 10.0 for the Quebec employees, you must apply the 2008 year-end update (round 2) for Canadian Payroll in the FRCA version of Microsoft Dynamics GP 10.0.
For more information about the 2008 year-end update for Canadian Payroll in the FRCA version of Microsoft Dynamics GP 10.0, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/959567/
)
The 2008 year-end update is available for Canadian Payroll in the French-Canadian (FRCA) version of Microsoft Dynamics GP 10.0
NotesFor more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer:
Partner
CustomerThe .msp file of this update also includes the
updates that are described in the following Microsoft Knowledge Base articles:
Collapse this tableExpand this table
| Knowledge Base article | Title |
|---|---|
| 959567
(http://support.microsoft.com/kb/959567/EN-US/ |
The 2008 year-end update is available for Canadian Payroll in the French-Canadian (FRCA) version of Microsoft Dynamics GP 10.0 |
| 957744
(http://support.microsoft.com/kb/957744/EN-US/ |
Update 957744 is available for the French-Canadian (FRCA) version of Microsoft Dynamics GP 10.0 that is used in a multilingual environment |
| 955681
(http://support.microsoft.com/kb/955681/EN-US/ |
The French-Canadian (FRCA) version of Microsoft Dynamics GP 10.0 Service Pack 3 is now available |
| 951968
(http://support.microsoft.com/kb/951968/EN-US/ |
Hotfix rollup 951968 is now available for the French-Canadian (FRCA) version of Microsoft Dynamics GP 10.0 |
| 943895
(http://support.microsoft.com/kb/943895/EN-US/ |
The French-Canadian (FRCA) version of Microsoft Dynamics GP 10.0 Service Pack 2 is available |
| 948882
(http://support.microsoft.com/kb/948882/EN-US/ |
An update for the French-Canadian version of Microsoft Dynamics GP 10.0 is available if you want to use the French-Canadian version of Microsoft Dynamics GP 10.0 in a multilingual environment |
| 947359
(http://support.microsoft.com/kb/947359/EN-US/ |
Hotfix rollup 947359 is now available for the French-Canadian (FRCA) version of Microsoft Dynamics GP 10.0 |
| 946604
(http://support.microsoft.com/kb/946604/EN-US/ |
Hotfix rollup 946604 is available for the French-Canadian (FRCA) version of Microsoft Dynamics GP 10.0 |
| 943981
(http://support.microsoft.com/kb/943981/EN-US/ |
The 2007 year-end update for Canadian Payroll for the French-Canadian version of Microsoft Dynamics GP 10.0 is available |
| 940548
(http://support.microsoft.com/kb/940548/EN-US/ |
The French-Canadian (FRCA) version of Microsoft Dynamics GP 10.0 Service Pack 1 is available |
Additionally, this update includes updates that are described in the FRCA version of Microsoft Dynamics GP 10.0 Service Pack 1 installation guide.
For more information about the installation guide, visit the following Microsoft Web site:
Installation information
To obtain this update for Microsoft Dynamics GP, visit one of the
following Microsoft Web sites, depending on whether you are a partner or a
customer.
Partner
CustomerFor more information about installing the update, visit Microsoft Dynamics Technical Support and enter a new support request:
Select your Microsoft Dynamics GP product, and then select Install in the subcategory list. You can also contact Microsoft Dynamics Technical Support by telephone at 888-477-7877.
Article ID: 961355 – Last Review: May 22, 2013 – Revision: 5.0
| kbmbspayrolltaxupdate kbqfe atdownload kbexpertiseadvanced kbsurveynew kbexpertiseinter kbhowto kbinfo kbmbsmigrate kbexpertisebeginner KB961355 |
How to upgrade applications to use the GPConn.dll file or the GPConnNet.dll file in Microsoft Dynamics GP
Microsoft Dynamics GP 9.0 and 10.0 include a change in the password policy that affects Dexterity in Microsoft Dynamics GP and also affects the Crypto.dll file. Therefore, you must replace code that calls the Crypto.dll file by using code that calls the new GPConn.dll file or the new GPConnNet.dll file.
If you are specifically using either of the .dll files from Visual Basic for Applications (VBA) or from VBScript in Integration Manager, the best integration option is to use the RetrieveGlobals9.dll file that is available on the Mod/VBA samples pages. In these situations, download the updated RetrieveGlobals9.dll file instead of requesting keys for the GPConn.dll file or the GPConnNet.dll file. To download the RetrieveGlobals9.dll file, visit the following Microsoft Web site:
You can open a Dexterity support incident to obtain help that is unavailable in the documentation. You will not be charged for the initial support incident to request the .dll files. However, you may be charged for any additional support incidents about how to implement a solution.
For more information about the new connection objects in VBA that replace the RetrieveGlobals.dll and RetrieveGlobals9.dll files in Microsoft Dynamics GP 10.0 , click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/936115/
)
Information about the new connection objects in VBA that replace the RetrieveGlobals.dll and RetrieveGlobals9.dll files in Microsoft Dynamics GP 10.0
For more information about technical support options for Microsoft Business Solutions partners, customers, and ISVs, visit the following Microsoft Web site:
Article ID: 912960 – Last Review: May 22, 2013 – Revision: 7.0
Applies to
- Microsoft Dynamics GP 2010
- Dexterity, when used with:
- Microsoft Dynamics GP 10.0
- Microsoft Dynamics GP 9.0
| kbmbsmigrate kbhowto KB912960 |
View the original here:
How to upgrade applications to use the GPConn.dll file or the GPConnNet.dll file in Microsoft Dynamics GP
Recent Comments