The information in this article applies to:
SUMMARY
This article contains a copy of the Remote Data Service 1.5 Release Notes included with the Windows NT 4.0 Option Pack. It is listed here so that the issues it covers are included in queries performed against the Knowledge Base. MORE INFORMATION
This document provides late-breaking or other information that supplements
the Microsoft(R) Remote Data Service 1.5 documentation. The following sections are included in this document: Microsoft Remote Data Service (RDS) is a fast and efficient data connectivity
and data publishing framework for applications hosted in Internet Explorer. It
is based on a client/server, distributed technology that works over HTTP, HTTPS
(HTTP over Secure Sockets layer), and DCOM application protocols. Using
data-aware ActiveX controls, RDS provides data access programming in the style
of Microsoft(R) Visual Basic(R) to Web developers who need to build distributed,
data-intensive applications for use over corporate intranets and the
Internet. The name, Microsoft(R) Advanced Data Connector (ADC) is changing to Microsoft(R)
Remote Data Service (RDS), a feature of Microsoft(R) ActiveX(TM) Data Objects (ADO).
ADC has always relied on ADO and this change represents a move to more closely
integrate and clarify the relationship between these two components. ADO is a
programming interface which allows easy and flexible access to OLE DB and ODBC
data sources. Remote Data Service builds on ADO to provide an easy, disconnected
recordset, and remoting service. The functionality of Advanced Data Connector
has not been affected by this change, and you will see a number of great new
features with the release of version 1.5. The following are new features in Remote Data Service 1.5. For more
information on these features, refer to the documentation. Before you install Microsoft Remote Data Service, make sure that your client
and server computers meet the minimum hardware and software requirements. To install Remote Data Service, you must meet certain hardware requirements,
which include the following: Before you install Remote Data Service on a server computer, your server
computer must meet the following software requirements: To access Remote Data Service applications from client computers, client
computers must meet the following software requirements: Note Remote Data Service has not been tested with the
Netscape browser technology. To build client Web pages, you can use typical HTML authoring tools, such as
Notepad or the more fully featured Microsoft ActiveX Control Pad. To program server-side business objects, you can use any ActiveX(TM)/COM
DLL-compatible tool, such as Microsoft(R) Visual Basic(R) 4.0 or later, or
Microsoft(R) Visual C++(R). For Remote Data Service to work correctly, you should ensure that the Remote
Data Service server and client components are installed correctly. The server
component is installed via the setup program (mdac_nts.exe for Windows NT
Server; mdac_ntw.exe for Windows NT Workstation; mdac_95.exe for Windows 95;
mdac_as for Alpha server; mdac_aw.exe for Alpha workstation) or with the IIS 4.0
integrated setup. The client files required are provided with Internet Explorer
4.0, so no .cab file or setup program is required. You will install the Microsoft Remote Data Service server components on your
Web server computer, which should have Windows NT Server version 4.0 with SP3 or
later. Setup assumes that your computer meets all of the software
requirements. The Setup program installs the program files to the <device>:\Program
Files\Common Files\System\MSADC directory. (This location is adjacent to other
complementary Microsoft technologies such as ActiveX Data Objects and OLE DB.)
The following subdirectories are created under the \MSADC directory with the
setup program. The server installation program (mdac_nts.exe) also creates a Microsoft
Internet Information Server virtual root on your Web server computer. The root
is designated http://<servername>/msadc and you can use it to reference
the files in that directory tree from the browser. Once you have followed this procedure to set up Microsoft Remote Data Service
on your Web server computer, you can validate your installation (see Validating
Setup, below). Microsoft Internet Explorer 4.0 already includes the necessary Remote Data
Service (RDS) client components. Therefore, you don't need to include a .cab
file on your Web page because client computers will already have the RDS client
component DLLs. See the Technical Notes for a list of client files if your
application needs to provide the client files. You can use the ADCTest.asp sample application to validate your Microsoft
Remote Data Service installation. http://<servername>/MSADC/Samples/adctest.asp If the grid displays a resultset, your installation is
correct. If you run into any problems, review the setup instructions and see
"Troubleshooting Remote Data Service" and "Other RDS Configuration Information"
in online Help. If you have a technical question about Remote Data Service, please visit the
Microsoft Data Access Web Site at http://www.microsoft.com/data/ for information
about support available from Microsoft Technical Support. You can visit the Microsoft Remote Data Service Home Page on the World Wide
Web for documentation updates and information about other related technologies.
The address is http://www.microsoft.com/data/rds. To facilitate discussion and information sharing, Microsoft has set up a
public newsgroup: microsoft.public.ado.rds. You are welcome to post articles and
messages to this unmoderated, unsupported newsgroup. Microsoft does not
guarantee responses or direct support. For more information, visit the Remote
Data Service Web site, http://www.microsoft.com/data/rds/. If you access Visual FoxPro data, you must use the latest Visual FoxPro ODBC
driver (version 5.0.0.402 or later), which is available from
http://www.microsoft.com/vfoxpro/vfdownload. If you don't use the latest driver,
you may not be able to execute queries correctly. To load the grid in the RDS sample applications, you need to be able to
access the Internet (as opposed to your intranet). If you try to load the
samples that use the Sheridan grid, the Sheridan cab file referenced in the
CODEBASE line attempts to download the mfc42.dll file patch from the Microsoft
general fixes Web site. If it is unable to access this patch, the grid will not
load. If the ActiveX control for the grid (ssdatb32.ocx) already resides on the
client computer, the CODEBASE line will not need to unpack the .cab file, and
the patch download prompt will not be encountered. If you receive the error "System error: out of virtual memory error" from the
Web Server requiring a reboot, the following may address the error. Your Web
server machine may be out of virtual memory, or the SQL data source server may
require more TempDB space to handle the size of the query you are attempting to
run. Virtual memory can be adjusted from Control Panel (click the System icon,
select the Performance tab, and click the Virtual Memory button to see if there
is extra hard disk space available). More information on how to adjust the
TempDB space can be found in the "Performance" Help topic's subtopic,
"Ensuring Sufficient TempDB Space." For Web client convenience, the Microsoft Data Access Components client files
are included with Internet Explorer version 4.0. Provided below is a list of
files and their install locations if you wish to make these files available to
your non-Internet Explorer client components using the MDAC server. Files marked with an asterisk (*) should be self-registered with regsvr32.dll
which can be found in the \system (or \system32) directory of your machine. The
notation for \system below refers to \winnt\system32 directory on Windows NT
machines, or \win95\system on Windows 95 machines. It is important that these
files are consistently installed to these locations, to ensure that all programs
which rely on them will continue to function correctly in this and later
versions. msadce.dll* - installed to \Program Files\Common
Files\system\msadc The Filter property is not currently able to search for Null
values. The setting might be set as follows 'zipcode', '=', '<null>'
(which gets converted to NULL by the VBScript code), followed by the
Reset method to run the filter action. You will get a type
mismatch error. OnReadyStateChange - Fires whenever the
ReadyState property changes. This event is not available in
JScript. OnDataSetComplete - Fires when all data is fetched. OnDataSetChanged - Fires when a new
Recordset is returned but not yet fully populated. During an async fetch, the following sequence of events occurs: OnReadyStateChange - The ReadyState
property is set to adcReadyStateInteractive while data is being
fetched. OnDataSetComplete - All data is fetched, but
ReadyState is still set to
adcReadyStateInteractive. OnReadyStateChange - The ReadyState
property changes to adcReadyStateComplete. To get a disconnected recordset via ADO, you can use the following
syntax. Rather than: cnn.Connectionstring =
"provider=msdasql;dsn=MySQL;uid=SalesMgr;pwd=Secret" you can use:
cnn.Connectionstring = "provider=MS Remote;Remote Server=http://MyServer;Remote
Provider=msdasql;dsn=MySQL;uid=sa;pwd=" The following is a list of Remote Data Service 1.5 known issues. OnDataSetChanged event will be issued when the
Recordset exists, the query execution is complete, but not all
rows are present. Immediately after the OnDataSetChanged event
is issued, the ReadyState property is a value of 3. OnDataSetComplete event will be issued when the
Recordset exists, and all rows are present. Immediately after
the OnDataSetComplete event is issued the
ReadyState property a value of 4. (C) 1997 Microsoft Corporation These materials are provided "as-is," for informational purposes only. Neither Microsoft nor its suppliers makes any warranty, express or implied
with respect to the content of these materials or the accuracy of any
information contained herein, including, without limitation, the implied
warranties of merchantability or fitness for a particular purpose. Because some
states/jurisdictions do not allow exclusions of implied warranties, the above
limitation may not apply to you. Neither Microsoft nor its suppliers shall have any liability for any damages
whatsoever including consequential, incidental, direct, indirect, special, and
lost profits. Because some states/jurisdictions do not allow exclusions of
implied warranties, the above limitation may not apply to you. In any event,
Microsoft's and its suppliers' entire liability in any manner arising out of
these materials, whether by tort, contract, or otherwise shall not exceed the
suggested retail price of these materials. Additional query words: rds iis kbreadme readme adcrlnts.htm adcrlnts ntop
Keywords : |
|||||||||||
|
Last Reviewed: August 9, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |