Here are the API methods that have been further restricted for safety when running Internet Explorer:įor the ADO Stream object, if the LoadFromFile or SaveToFile methods are used.įor the ADO Recordset object, if either the Save method or the Open method, such as when either the adCmdFile option is set or the Microsoft OLE DB Persistence Provider (MSPersist) is used.įor these limited sets of potentially disk-accessible functions, the following behavior occurs for ADO 2.8 and later, if any code that uses these methods is run in Internet Explorer:
If user does not trust the site, clicking Cancel blocks the ADO code for data access from running and executing in its entirety.ĭisk-accessible code limited now to trusted sitesĪdditional design changes were made in ADO 2.8 that specifically restrict the ability of a limited set of APIs, which might expose the potential to read from or write to files on the local computer.
If user trusts the site, clicking OK will allow all disk-safe code (all ADO methods and properties with the exceptions of the disk-accessible APIs described later in this topic) to run and execute in the browser window. The preceding message allows the user to make informed decision, while knowing the consequences for either choice: Website, click OK, otherwise click Cancel. Instead, the following message appears in this context: This Website uses a data provider that may be unsafe. Your Trusted Sites zone on the Security tab of the Internet Options dialogįor ADO 2.8 and later, the preceding message no longer appears. Do you want to allow this? ToĪvoid this message in Internet Explorer, you can add a secure Web site to Revised and improved security warning message box now used to alert usersįor ADO 2.7 and earlier, the following warning message appears when a scripted Web page tries to run ADO code from an untrusted provider: This page accesses data on another domain. The following features effect how ADO 2.8 and later works when it is used in scripted Web pages in Internet Explorer.
This way, you can ensure you are aware of any compatibility issues before you deploy your updated application. If you are updating your application from an earlier version of ADO, it is recommended that you test your updated application on a non-production computer before you deploy it to customers.
0 kommentar(er)
