SQL
____________________________________________________________
C:\Program Files\Common Files\Microsoft
Shared\web server extensions\40\bin\FPSREAD9.TXT
o Support FrontPage Database Integration *
Set Up a Guest Account to Establish Connection to SQL
Server After Clean Install with IIS3 and NT 4.0 MICROSOFT FRONTPAGE 2000 SERVER
EXTENSIONS HELP * Running Microsoft Management Console Help for Standalone
FrontPage Server Extensions RESOURCES FOR FURTHER INFORMATION * Server
Extensions Resource Kit * Server Extensions Resource Kit Update * Microsoft
Knowledge Base INSTALLING MICROSOFT FRONTPAGE 2000 SERVER EXTENSIONS Disable
Virus Protection
____________________________________________________________
C:\Program Files\Common Files\Microsoft
Shared\web server extensions\40\bin\FPSREAD9.TXT
ee http://www.microsoft.com/data/21info.htm
Set Up a Guest Account to Establish Connection to SQL
Server After Clean Install with IIS3 and NT 4.0 When using Microsoft SQL Server
with Integrated or Mixed Security on a computer with Microsoft Internet
Information Server, it may be necessary to access SQL
Server from a guest account. You can set up a guest account to work around
problems connecting an IIS computer to SQL
Server on a separate computer over a trusted connection. For more information,
go to the Microsoft Knowledge Base at
http://support.microsoft.com/support/ and read articles Q176380 and Q176377. MICROSOFT
FRONTPAGE 2000 SERVER EXTENSIONS HELP Running Microsoft Management Console Help
for Standalone FrontPage Server Extensions Online Help for the FrontPage Server
____________________________________________________________
C:\Program Files\Microsoft Office\Office\ACREAD9.TXT
er Colors May Not Display Correctly on 256-Color Monitors MICROSOFT JET
ANSI-92 Compliant SQL COUNTER and IDENTITY
CONVERSION AND COMPATIBILITY Compatibility Library Turning On Name AutoCorrect
in a Converted Access Database MICROSOFT ACCESS
PROJECTS Unexpected Behavior When SQL Statement
Output Contains Two Fields with Same Name Can't Refer To Controls in Forms or
Reports in Aggregate Functions Rebooting Your Computer after Installing
Microsoft Data Engine (MSDE) "Order by
clause may not be used in this query type" When View Has TOP Clause
Incoming Named Pipe Connections Not Supported on Windows 95 or Windows 98
Microsoft Data Engine Rules for Naming
Identifiers OFFICE WEB COMPONENT ISSUES Editing
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\ACREAD9.TXT
rator" When Modifying Page Connection String Non-U.S., Non-East
Asian: Northwind SQL Project Not Advertised in
the User Interface Hyperlink to Database Object
Doesn't Work with Object Type Name in Local Language RIGHT-TO-LEFT LANGUAGES
Printing in Right-to-Left Languages Expression Builder Limitations for
Right-to-Left Languages Hijri Database Calendar
in Sample Applications Input Mask Restrictions for Right-to-Left Languages
Hijri Calendar Support in Data Access Pages and
Web Pages
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\ACREAD9.TXT
MICROSOFT JET ANSI-92 Compliant SQL The Microsoft Jet 4.0 database engine supports two forms of SQL
syntax; one mode supports the same Jet SQL
commands used in previous versions of Access, and another new mode supports new
Jet SQL commands and syntax that are more compliant
with the ANSI SQL-92 standard. The mode that
supports the SQL commands used in previous
versions of Access is the only mode that is available through the Access 2000
user interface. The newer SQL syntax is
currently available only in Visual Basic for Applications (VBA) procedures that
use ActiveX Data Objects (ADO) and the Microsoft
OLE DB provider for Jet version 4.x. When you use the OLE DB provider for Jet
version 4.x through ADO, you can execute temporary queries (i.e., queries that
are not stored and are used as part of a recordset's source by using
Connection.Execute or Command.Execute) or create stored queries (by using the
new CREATE VIEW, CREATE PROCEDURE
____________________________________________________________
C:\Program Files\Microsoft Office\Office\ACREAD9.TXT
ble in the Objects list in the Database
window. For more information about ANSI-92 compliant SQL
with the Microsoft OLE DB Provider for Jet version 4.x, type COMPARISON OF JET SQL AND ANSI SQL in the
Office Assistant or on the Answer Wizard tab in the Help window, and then click
Search. COUNTER and IDENTITY - COUNTER and IDENTITY are Microsoft Jet SQL reserved words, but they are not Jet SQL data types. For
more information about the Microsoft Jet data
types, see the Microsoft Jet Database Engine
Programmer's Guide published by Microsoft Press. CONVERSION AND COMPATIBILITY
Compatibility Library Access 2000 does
not ship with the DAO 2.5/3.x compatibility library. If you attempt to convert
an Access database in which the code contains
older versions of DAO objects, methods, and prop
____________________________________________________________
C:\Program Files\Microsoft Office\Office\ACREAD9.TXT
MICROSOFT ACCESS PROJECTS Unexpected Behavior When SQL Statement Output Contains Two Fields with Same
Name In an Access project (*.adp), you
might see unexpected results when you use an SQL
statement whose output contains two or more fields with the same name. For
example, you might see unexpected behavior when you work with a view that is based on two tables and that contains two fields that
have the same name but are located in different tables. To prevent unexpected
behavior, specify an alias for one of the fields to ensure that every field in
the output has a unique name. Can't Refer to Controls in Forms or Reports in
Aggregate Functions
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\ACREAD9.TXT
You cannot connect to a remote Microsoft Data
Engine (MSDE) or SQL Server 7.0 Desktop database located on a Windows 95 or Windows 98
computer unless you use a protocol other than Named Pipes. These platforms do
not support incoming Named Pipe connections. To connect to the database, run the Client Network Utility Cliconfg.exe,
which is located in the Windows\System folder on the client computer; add a
server alias that specifies the remote server you need to connect to, and
select TCP/IP as the default network library. Microsoft Data Engineering
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\ACREAD9.TXT
with double number signs (##) denotes a global temporary object. Some
Transact-SQL functions have names that start
with double at signs (@@). To avoid confusion with these functions, it is
recommended that you do not use names that start with @@. 2. Subsequent
characters can be: Letters as defined in the Unicode Standard 2.0. Decimal
numbers from either Basic Latin or other national scripts. The @, $, #, or _
symbols. The identifier must not be a Transact-SQL
reserved word. MSDE reserves both the uppercase and lowercase versions of
reserved words. 3. Embedded spaces or special characters are not allowed. OFFICE
WEB COMPONENT ISSUES Editing a Formula in a Cell That Contains a Hyperlink The Help topic "Change a formula in a
spreadsheet" incorrectly states that if a cell you want to edit contains a
hyperlink
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\ACREAD9.TXT
d be replaced with "JRFilterTypeTable" and
"JRFilterTypeRelationship" respectively. Topic: "SQL Reserved Words" When you click COUNTER or IDENTITY, you jump to the topic "SQL Data Types."
COUNTER and IDENTITY are Microsoft Jet SQL
reserved words, but they are not Jet SQL data types. Topic: "SQL
Data Types" Under DATETIME in the Data type
table, replace "(See DOUBLE)" with "(See FLOAT)". Topic:
"Microsoft Office 2000 Developer contents" Under "Office Developer Tools CD-ROM," ignore the
following paragraph: "Microsoft Office WebBot Components, with which you
create applets embedded inside Office 2000 documents. With the user interface
these applets provide, users don't need to author script
____________________________________________________________
C:\Program Files\Microsoft Office\Office\ACREAD9.TXT
xt "Microsoft Access for Windows". Under "Installed on
first use (default)," add "Northwind SQL
Project File" to the "Feature column; in the corresponding
"Location in the installation program" column, add the text
"Microsoft Access for Windows; Sample Databases".
Under "Not installed (custom installation only)": * Ignore
"Calendar Control" in the "Feature" column and the
corresponding text "Microsoft Access for Windows" in the
"Location in the installation program" column. * Ignore
"Northwind SQL Project File" in the
"Feature" column and the corresponding text "Microsoft Access
for Windows; Sample Databases" in the
"Location in the installation program" column. * Ignore the last
paragraph containing the note about the Calendar Control and the Northwind SQL Project File. Topic: "Set Options from Visual
Basic" Under "View Tab":
* In the "Option text" column, replace "Use taskbar for each
document" with "Windows in Taskbar"; in the corresponding
"String argument" column, replace "Use Taskbar For Each
Document" with "ShowWindowsInTaskbar". Under "General
Tab," in the "Option text" column: * Replace "Compact
current database" with "Compact On
Close". * Add the text "Use four-dig
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\ACREAD9.TXT
e Must Match Code Page of Server For SQL Server international
applications, you may see unexpected behavior if the system code page of client
machines doesn't match the character set of Microsoft SQL
Server on the server. On the client, the system code page is the character set
that is used by the language specified in operating system; if you are running
Windows NT Workstation 4.0 or Windows NT Server 4.0, this is the Default
Locale. On the server, the character set is specified during SQL Server installation. In an Access project (*.adp),
result sets containing ANSI text fields are not displayed correctly if the
system code page of the client computer does not match the character set of the
SQL Server to which the client is connected.
This problem does not occur for data that is
stored as Unicode on the server. Create Registry Keys To Temporarily Enforce a
Code Page During Conversion Access
normally uses the code page of the operating system to convert previous-version
databases to Access 2000. If you are converting
an Access database in which the code page is
different from that of the operating system o
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\ACREAD9.TXT
MS-DOS Prompt. 4. Change to the \Binn directory of MSDE; by default, this
directory is C:\MSSQL7\Binn. 5. Type the
following in the case shown: sqlservr -c -T1806 6. Repeat steps 3 and 4. 7. In
the second MS-DOS Prompt window, type the following in the case shown: osql
-Usa -P use msdb checkpoint go shutdown go Note that the checkpoint command
generates a warning that the sort order in the database
differs from the server sort order. 8. Close the MS-DOS Prompt windows, and
restart the MSDE service. Cannot Log On As "Administrator" When
Modifying Page Connection String - In non-English versions of Access, if you
attempt to establish a c
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\ACREAD9.TXT
ess page, use the English word "Admin" as the logon name.
Non-U.S., Non-East Asian: Northwind SQL Project
Not Advertised in the User Interface In
non-U.S. English and non-East Asian versions of Access, the Northwind SQL Project File is not advertised in the user
interface. You must run the Office 2000 installation program or Access 2000
installation program, and change the installation setting of the Northwind SQL Project File from "Installed on First
Use" to "Run from My Computer." Hyperlink to Database Object Doesn't Work with Object Type Name in
Local Language If you click a hyperlink
whose subaddress specifies a database object,
you might receive a message that Access is not able to follow the hyperlink.
This problem occurs if the object type string is in the local language instead
of in English. For example, you might rec
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\OEMEULA.TXT
1 of this EULA, you may only install and use one copy of the SOFTWARE
PRODUCT on the COMPUTER. · SQL Server,
Workstation System Installation and Use. If the SOFTWARE PRODUCT is SQL Server, Workstation System, the following applies
to your installation and use of the SOFTWARE PRODUCT subject to the
restrictions set forth in Section 2. For each Processor Version (defined below)
supplied, the SOFTWARE PRODUCT consists of "Server Software",
"Client Software", and "Development Tool" components. You
may install and use one copy of one Processor Version of the Server Software
component only on the COMPUTER. You may install the Client Software and
Development Tool components
____________________________________________________________
C:\Program Files\Microsoft Office\Office\OEMEULA.TXT
licensor. You must comply with all applicable laws regarding the use of
the SOFTWARE PRODUCT. · SQL Server, Workstation
System. If the SOFTWARE PRODUCT is SQL Server,
Workstation System the following applies to your use of the SOFTWARE PRODUCT.
Open Data Services. The Open Data Services component of the Server Software is
licensed only for use with SQL Server and SQL Server extended stored procedures, and for
developing and testing Open Data Services-based software applications. Any other use of the Open
Data Services component, such as for general
operation of (i) stand-alone gateways or (ii) custom Open Data Services-based
applications, requires a separate license even if they are run on the same
computer as SQL Server. Run-Time Software - You
have a limited nonexclusive, royalty-free right to reproduce and distribute
those DB-Library, Net-Library and ODBC files included in Microsoft SQL Server which are required for run-time execution
of compiled applications ("Run-Time Files") in conjunction with and
as a part of your application software product that is created using the
Microsoft SQL Server Server Software
("Application"), provided that: (a) you comply with the export
restrictions in Section 6; (b) you do not use Microsoft's or MSLI's name, logo,
or trademarks to market your Application; (c) you include a valid copyright
notice in your Application; (d) if your Application contains ODBC files, (i)
your Application must operate in conjunction with Microsoft SQL Server, and (ii) you agree to distribute all ODBC
components specified in the README file in conjunction with your Application;
(e) you do not charge separately for the Run-Time Files; (f) you do not modify
the Run-Time Files; and (g) you agree to indemnify, hold harmless, and defend
Microsoft, MSLI, Manufacturer, and their suppliers from and against any claims
or lawsuits, including attorneys' fees, that arise or result from the use or
distribution of your Application.
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\OEMEULA.TXT
tion and technical data, or (ii) your
Application, as described above in Section 2, developed with SQL Server Server software, or process, or service
that is the direct product of the SOFTWARE PRODUCT to any country to which such
export or transmission is restricted by any applicable U.S. regulation or
statute, without the prior written consent, if required, of the Bureau of
Export Administration of the U.S. Department of Commerce, or such other
governmental entity as may have jurisdiction over such export or transmission.
If SOFTWARE PRODUCT is labeled "North America Only Version" above,
____________________________________________________________
C:\Program Files\Microsoft
Office\Office\XLREAD9.TXT
If you attempt to publish a PivotTable report with interactivity that
uses a query or SQL command that uses the same
field name twice, you will receive an error when you try to open the Web page
in Internet Explorer. You can work around the problem by changing the column
heading used for one of the duplicate fields in Microsoft Query. To do this,
follow these steps: 1. Open the Excel workbook containing the PivotTable report
that was used to publish the Web page. 2. Select a cell within the PivotTable
report, and then click PivotTable And PivotChart Report
____________________________________________________________