You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ado/guide/data/ado-error-reference.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ The **ErrorValueEnum** constant describes the ADO error values. For a complete l
58
58
|**3724**|**adErrCantConvertvalue**|Data value cannot be converted for reasons other than sign mismatch or data overflow. For example, conversion would have truncated data.|
59
59
|**3725**|**adErrCantCreate**|Data value cannot be set or retrieved because the field data type was unknown, or the provider had insufficient resources to perform the operation.|
60
60
|**3726**|**adErrColumnNotOnThisRow**|Record does not contain this field. An incorrect field name was specified or a field not in the **Fields** collection of the current record was referenced.|
61
-
|**3727**|**adErrURLDoesNotExist**|Either the source URL or the parent of the destination URL does not exist. There is a typographical error in either the source or destination URL. You might have `http://mysite/photo/myphoto.jpg` when you should actually have `http://mysite/photos/myphoto.jpg` instead. The typographical error in the parent URL (in this case, *photo* instead of *photos*) has caused the error.|
61
+
|**3727**|**adErrURLDoesNotExist**|Either the source URL or the parent of the destination URL does not exist. There is a typographical error in either the source or destination URL. You might have `https://mysite/photo/myphoto.jpg` when you should actually have `https://mysite/photos/myphoto.jpg` instead. The typographical error in the parent URL (in this case, *photo* instead of *photos*) has caused the error.|
62
62
|**3728**|**adErrTreePermissionDenied**|Permissions are insufficient to access tree or subtree. The user named in the connection string does not have the appropriate permissions.|
63
63
|**3729**|**adErrInvalidURL**|URL contains invalid characters. Make sure the URL is typed correctly. The URL follows the scheme registered to the current provider (for example, Internet Publishing Provider is registered for http).|
64
64
|**3730**|**adErrResourceLocked**|Object represented by the specified URL is locked by one or more other processes. Wait until the process has finished and attempt the operation again. The object you are trying to access has been locked by another user or by another process in your application. This is most likely to arise in a multi-user environment.|
Copy file name to clipboardExpand all lines: docs/ado/guide/data/namespaces.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ The XML persistence format in ADO uses the following four namespaces.
27
27
|rs|Refers to the namespace containing elements and attributes specific to ADO Recordset properties and attributes.|
28
28
|z|Refers to the schema of the current rowset.|
29
29
30
-
A client should not add its own tags to these namespaces, as defined by the specification. For example, a client should not define a namespace as "urn:schemas-microsoft-com:rowset" and then write out something such as "rs:MyOwnTag." To learn more about namespaces, see the [W3C Namespaces in XML Recommendation](http://www.w3.org/TR/REC-xml-names/).
30
+
A client should not add its own tags to these namespaces, as defined by the specification. For example, a client should not define a namespace as "urn:schemas-microsoft-com:rowset" and then write out something such as "rs:MyOwnTag." To learn more about namespaces, see the [W3C Namespaces in XML Recommendation](https://www.w3.org/TR/REC-xml-names/).
31
31
32
32
> [!IMPORTANT]
33
33
> The ID for the schema tag must be "RowsetSchema," and the namespace used to refer to the schema of the current rowset must point to "#RowsetSchema."
Copy file name to clipboardExpand all lines: docs/ado/guide/data/persisting-hierarchical-recordsets.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ manager: craigg
19
19
# Persisting Hierarchical Recordsets
20
20
You can save a hierarchical **Recordset** to a file in either ADTG or XML format by calling the [Save](../../../ado/reference/ado-api/save-method.md) method. However, two limitations apply when saving hierarchical **Recordset**s in XML format: You cannot save in XML if the hierarchical **Recordset** contains pending updates, and you cannot save a parameterized hierarchical **Recordset**.
21
21
22
-
For more information about the Data Shaping provider, see [Microsoft Data Shaping Service for OLE DB](../../../ado/guide/appendixes/microsoft-data-shaping-service-for-ole-db-ado-service-provider.md) (ADO) and [Overview of the Data Shaping Service for OLE DB](http://msdn.microsoft.com/9f51e471-8e85-448e-9fb8-b64bbf767bf3).
22
+
For more information about the Data Shaping provider, see [Microsoft Data Shaping Service for OLE DB](../../../ado/guide/appendixes/microsoft-data-shaping-service-for-ole-db-ado-service-provider.md) (ADO) and [Overview of the Data Shaping Service for OLE DB](https://msdn.microsoft.com/9f51e471-8e85-448e-9fb8-b64bbf767bf3).
Copy file name to clipboardExpand all lines: docs/ado/guide/data/schema-section.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ The schema section is required. As the previous example shows, ADO writes out de
93
93
Similarly, because there is no alias defined for `CompanyName` in the previous example, `CompanyName` must be used consistently throughout the document.
94
94
95
95
## Data Types
96
-
You can apply a data type to a column with the dt:type attribute. For the definitive guide to allowed XML types, see the Data Types section of the [W3C XML-Data specification](http://www.w3.org/TR/1998/NOTE-XML-data/). You can specify a data type in two ways: either specify the dt:type attribute directly on the column definition itself or use the s:datatype construct as a nested element of the column definition. For example,
96
+
You can apply a data type to a column with the dt:type attribute. For the definitive guide to allowed XML types, see the Data Types section of the [W3C XML-Data specification](https://www.w3.org/TR/1998/NOTE-XML-data/). You can specify a data type in two ways: either specify the dt:type attribute directly on the column definition itself or use the s:datatype construct as a nested element of the column definition. For example,
Copy file name to clipboardExpand all lines: docs/ado/guide/data/service-providers-and-components.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,6 @@ Service providers are components that extend the functionality of data providers
21
21
22
22
Universal Data Access provides a *component architecture* that allows individual, specialized components to implement discrete sets of database functionality, or "services," on top of less capable stores. Thus, rather than forcing each data store to provide its own implementation of extended functionality or forcing generic applications to implement database functionality internally, service components provide a common implementation that any application can use when accessing any data store. The fact that some functionality is implemented natively by the data store and some through generic components is transparent to the application.
23
23
24
-
For example, a cursor engine, such as [The Cursor Service for OLE DB](http://msdn.microsoft.com/57638feb-4ecd-4051-becb-8f828d21cf44), is a service component that can consume data from a sequential, forward-only data store to produce scrollable data. Other service providers commonly used by ADO include the [Microsoft OLE DB Persistence Provider (ADO Service Provider)](../../../ado/guide/appendixes/microsoft-ole-db-persistence-provider-ado-service-provider.md) (for saving data to a file), the [Microsoft Data Shaping Service for OLE DB (ADO Service Provider)](../../../ado/guide/appendixes/microsoft-data-shaping-service-for-ole-db-ado-service-provider.md) (for hierarchical **Recordsets**), and the [Microsoft OLE DB Remoting Provider (ADO Service Provider)](../../../ado/guide/appendixes/microsoft-ole-db-remoting-provider-ado-service-provider.md) (for invoking data providers on a remote computer).
24
+
For example, a cursor engine, such as [The Cursor Service for OLE DB](https://msdn.microsoft.com/57638feb-4ecd-4051-becb-8f828d21cf44), is a service component that can consume data from a sequential, forward-only data store to produce scrollable data. Other service providers commonly used by ADO include the [Microsoft OLE DB Persistence Provider (ADO Service Provider)](../../../ado/guide/appendixes/microsoft-ole-db-persistence-provider-ado-service-provider.md) (for saving data to a file), the [Microsoft Data Shaping Service for OLE DB (ADO Service Provider)](../../../ado/guide/appendixes/microsoft-data-shaping-service-for-ole-db-ado-service-provider.md) (for hierarchical **Recordsets**), and the [Microsoft OLE DB Remoting Provider (ADO Service Provider)](../../../ado/guide/appendixes/microsoft-ole-db-remoting-provider-ado-service-provider.md) (for invoking data providers on a remote computer).
25
25
26
26
For more information about service and data providers, see [Appendix A: Providers](../../../ado/guide/appendixes/appendix-a-providers.md).
Copy file name to clipboardExpand all lines: docs/ado/guide/data/shape-commands-in-general.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Data shaping defines the columns of a shaped **Recordset**, the relationships be
40
40
41
41
You can access the **Recordset** components of the shaped **Recordset** programmatically or through an appropriate visual control.
42
42
43
-
Microsoft provides a visual tool that generates shape commands (see the [Data Environment Designer](http://go.microsoft.com/fwlink/?LinkId=5689) in the Visual Basic 6 documentation) and another that displays hierarchical cursors (see "Using the Microsoft Hierarchical Flexgrid Control" in the Visual Basic 6 documentation).
43
+
Microsoft provides a visual tool that generates shape commands (see the [Data Environment Designer](https://go.microsoft.com/fwlink/?LinkId=5689) in the Visual Basic 6 documentation) and another that displays hierarchical cursors (see "Using the Microsoft Hierarchical Flexgrid Control" in the Visual Basic 6 documentation).
44
44
45
45
For information about navigating a hierarchical **Recordset**, see [Accessing Rows in a Hierarchical Recordset](../../../ado/guide/data/accessing-rows-in-a-hierarchical-recordset.md).
0 commit comments