none
Broken links in MSDN Excel 2003 VBA Reference documentation RRS feed

  • Question

  • Hi, folks,

    In the online MSDN reference documentation for Office 2003 VBA, at least in the Excel VB section, there are a bunch of broken links for properties and methods. For some alphabetical ranges of methods and properties, the links to them appear broken, so the doco for those items is unavailable. The method and property names will appear in navigation lists, but when when I click on them, they don't lead anywhere.

    For example, here's the "A" properties. AutoAttach on down are broken. http://msdn.microsoft.com/en-us/library/aa174789(v=office.11).aspx

    Or here's the Application object. Several ranges of links in the Properties and Methods sections are broken. http://msdn.microsoft.com/en-us/library/aa213696(v=office.11).aspx

    When I view source on these pages, the "a" elements for these items are missing their href attributes. Tried in IE 8, Chrome, and Firefox.

    Unfortunately, today I need the doco on IgnoreRemoteRequests and AutomationSecurity. Is there another location where this doco can be found with working links? Or a way to get to individual items without a working link? I've sent feedback to MSDN on it but don't expect a quick fix.

    Cheers,
    Andrew


    • Edited by Andrew Janke Tuesday, October 11, 2011 3:15 PM added "documentation" term for searchability
    Tuesday, October 11, 2011 3:13 PM

Answers

  • Yes I see what you mean, I've added to the feedback. If it's not fixed soon I'll report elsewhere.

    Unfortunately, today I need the doco on IgnoreRemoteRequests and AutomationSecurity

    It'll be the same as 2003 VBA help, as copied here to get you out of trouble!
     IgnoreRemoteRequests Property
    See AlsoApplies To, Example, SpecificsTrue if remote DDE requests are ignored. Read/write Boolean.

    Example
    This example sets the IgnoreRemoteRequests property to True so that remote DDE requests are ignored.

    Application.IgnoreRemoteRequests = True

    AutomationSecurity Property
    See Also, Applies To, Example, Specifics,
    Returns or sets an MsoAutomationSecurity constant that represents the security mode Microsoft Excel uses when programmatically opening files. This property is automatically set to msoAutomationSecurityLow when the application is started. Therefore, to avoid breaking solutions that rely on the default setting, you should be careful to reset this property to msoAutomationSecurityLow after programmatically opening a file. Also, this property should be set immediately before and after opening a file programmatically to avoid malicious subversion. Read/write.

    MsoAutomationSecurity can be one of these MsoAutomationSecurity constants.
    msoAutomationSecurityByUI Uses the security setting specified in the Security dialog box.
    msoAutomationSecurityForceDisable Disables all macros in all files opened programmatically without showing any security alerts.
    msoAutomationSecurityLow Enables all macros. This is the default value when the application is started.

    expression.AutomationSecurity
    expression    Required. An expression that returns one of the objects in the Applies To list.

    Remarks
    Setting ScreenUpdating to False does not affect alerts and will not affect security warnings. The DisplayAlerts setting will not apply to security warnings. For example, if the user sets DisplayAlerts equal to False and AutomationSecurity to msoAutomationSecurityByUI, while the user is on Medium security level, then there will be security warnings while the macro is running. This allows the macro to trap file open errors, while still showing the security warning if the file open succeeds.

    Example
    This example captures the current automation security setting, changes the setting to disable macros, displays the Open dialog box, and after opening the selected document, sets the automation security back to its original setting.

    Sub Security()
       Dim secAutomation As MsoAutomationSecurity
        secAutomation = Application.AutomationSecurity
        Application.AutomationSecurity = msoAutomationSecurityForceDisable
       Application.FileDialog(msoFileDialogOpen).Show
        Application.AutomationSecurity = secAutomation

    End Sub

    Tuesday, October 11, 2011 9:19 PM
    Moderator

All replies

  • Yes I see what you mean, I've added to the feedback. If it's not fixed soon I'll report elsewhere.

    Unfortunately, today I need the doco on IgnoreRemoteRequests and AutomationSecurity

    It'll be the same as 2003 VBA help, as copied here to get you out of trouble!
     IgnoreRemoteRequests Property
    See AlsoApplies To, Example, SpecificsTrue if remote DDE requests are ignored. Read/write Boolean.

    Example
    This example sets the IgnoreRemoteRequests property to True so that remote DDE requests are ignored.

    Application.IgnoreRemoteRequests = True

    AutomationSecurity Property
    See Also, Applies To, Example, Specifics,
    Returns or sets an MsoAutomationSecurity constant that represents the security mode Microsoft Excel uses when programmatically opening files. This property is automatically set to msoAutomationSecurityLow when the application is started. Therefore, to avoid breaking solutions that rely on the default setting, you should be careful to reset this property to msoAutomationSecurityLow after programmatically opening a file. Also, this property should be set immediately before and after opening a file programmatically to avoid malicious subversion. Read/write.

    MsoAutomationSecurity can be one of these MsoAutomationSecurity constants.
    msoAutomationSecurityByUI Uses the security setting specified in the Security dialog box.
    msoAutomationSecurityForceDisable Disables all macros in all files opened programmatically without showing any security alerts.
    msoAutomationSecurityLow Enables all macros. This is the default value when the application is started.

    expression.AutomationSecurity
    expression    Required. An expression that returns one of the objects in the Applies To list.

    Remarks
    Setting ScreenUpdating to False does not affect alerts and will not affect security warnings. The DisplayAlerts setting will not apply to security warnings. For example, if the user sets DisplayAlerts equal to False and AutomationSecurity to msoAutomationSecurityByUI, while the user is on Medium security level, then there will be security warnings while the macro is running. This allows the macro to trap file open errors, while still showing the security warning if the file open succeeds.

    Example
    This example captures the current automation security setting, changes the setting to disable macros, displays the Open dialog box, and after opening the selected document, sets the automation security back to its original setting.

    Sub Security()
       Dim secAutomation As MsoAutomationSecurity
        secAutomation = Application.AutomationSecurity
        Application.AutomationSecurity = msoAutomationSecurityForceDisable
       Application.FileDialog(msoFileDialogOpen).Show
        Application.AutomationSecurity = secAutomation

    End Sub

    Tuesday, October 11, 2011 9:19 PM
    Moderator
  • Thanks Peter!

    That covered the items I needed. I think I'm going to leave this as un-Answered until the links get fixed on the site, since I'll probably run in to this again next time I'm working with the Excel object model.

    Wednesday, October 12, 2011 5:41 PM