---------------------------------------------------------

MICROSOFT Project 2000 Readme File

February 2000
(c) Microsoft Corporation, 2000. All rights reserved.
---------------------------------------------------------

This document provides late-breaking or other information

that is relevant to Microsoft Project 2000 and is current
as of the date above. After that date, you may find more
current information and resources on the Microsoft Office
Update Web site, accessible from the Help menu by
clicking Office On The Web. Additional information,
including network and administration issues, can be found
on the Microsoft Project Resource Kit Web site at
http://www.microsoft.com./office/project/prk. Note: A
Software Development Kit (SDK) is being developed. Please
visit the Microsoft Project Web site for details about
availability.

For further technical information on Microsoft Project,

please consult Support Online, where you can search for
technical information from Product Support Services.
To begin, go to http://support.microsoft.com/support/
_______________________________________________________
CONTENTS

1. MICROSOFT PROJECT 2000 HELP

2. INSTALLING MICROSOFT PROJECT 2000

2.1 Minimum System Requirements for Microsoft Project 2000
2.2 Disable Virus Protection Before Running Setup
2.3 Using Punctuation Characters in Folder Names During Setup
May Cause Problems
2.4 System Permissions Necessary to Install Microsoft Project
2000
2.5 Installing System Updates
2.6 Installing Microsoft Project 2000 on a Network
2.7 Prompt for CD Key When Setting Up Microsoft Project 2000
from Administrative Installation
2.8 Unexpected Message During Installation
2.9 Installing Microsoft Project 2000 on a System that
Had a Beta Version of Microsoft Project 2000 Installed
2.10 Using Files Created in a Beta Version of Microsoft
Project 2000
2.11 Microsoft Project 2000 Shortcut on the Programs Menu Varies
According to Your Operating System

3. WORKING WITH MICROSOFT PROJECT 2000

3.1 Custom Field Formulas that Contain Nested Date Functions
May Crash
3.2 Working with Multiple Projects and Resource Pools
3.3 Working with Inserted Projects, Resource Pools,
and Cross-Project Links in a Mixed Microsoft
Project 98 and Microsoft Project 2000 Environment
3.4 Having More than One Version of Microsoft Project Installed

4. MICROSOFT VISUAL BASIC FOR APPLICATIONS

4.1 Use F3 to Find Next Text Occurrence in the Code Window
 4.2 New Properties (VBA)
4.3 Modifying Macros Contained in the Global.mpt File

5. MICROSOFT PROJECT CENTRAL

5.1 Installation Requirements for Microsoft Project Central
5.2 Security Setting Changes for RDS Applications

6. EXCHANGING FILES WITH MICROSOFT PROJECT 98

_______________________________________________________
1. MICROSOFT PROJECT 2000 HELP
----------------------------------------------------------
For additional information on Microsoft Project, Microsoft Project
Central, the Microsoft Project database schema, the Microsoft
Project Central schema and OLE-DB, please see the following
documents on the Microsoft Project 2000 CD:

Note: You will need to have browser support such as Microsoft

Internet Explorer or Netscape to open the following documents.

- For Microsoft Project setup (including network setup) instructions,

please read:

[CDDrive]:\PFILES\MSOFFICE\OFFICE\1033\prjsetup.htm

- For Microsoft Project Central Server setup instructions,

please read:

[CDDrive]:\PJCNTRL\HELP\1033\svrsetup.htm

- For a description of table format and specifications required to

create and update project data directly in a database, please read:

[CDDrive]:\PFILES\MSOFFICE\OFFICE\1033\projdb.htm

- For a description of what's necessary to query information

from the Microsoft Project Central database, please read:

[CDDrive]:\PJCNTRL\HELP\1033\svrdb.htm

- For a description on table format and specifications for accessing

Microsoft Project through its OLE-DB provider, please read

[CDDrive]:\PFILES\MSOFFICE\OFFICE\1033\ole_db.htm

_______________________________________________________
2. INSTALLING MICROSOFT PROJECT 2000

2.1 Minimum System Requirements for Microsoft Project 2000

----------------------------------------------------------
To use Microsoft Project 2000, you need:
* PC with a Pentium 75 MHz or higher processor
* Microsoft Windows 95 or later operating system, or
Microsoft Windows NT Workstation operating system
version 4.0 with Service Pack 3 or later, or
Microsoft Windows 2000
* For Windows 95 or Windows 98:
- 16 MB of RAM for the operating system, plus an
additional 4 MB of RAM for Microsoft Project
* For Windows NT Workstation version 4.0 or later or
Windows 2000:
- 32 MB of RAM for the operating system, plus an
additional 4 MB of RAM for Microsoft Project. For
Windows 2000, 64 MB of RAM is recommended.
* Available hard-disk space (Number indicates typical
installation. Your hard-disk usage will vary depending on
configuration and whether common components are
already installed. Choices made during custom installation
may require more or less hard-disk space):
- Typical installation: 100 MB.
* CD-ROM drive
* VGA or higher resolution monitor; Super VGA recommended
* Microsoft Mouse, Microsoft IntelliMouse, or
compatible pointing device
Additional items or services required to use certain features:
* 9600 baud modem; 14,400 or higher baud recommended
* Multimedia computer required to access sound and other
multimedia effects
* Some Internet functionality may require Internet access
and payment of a separate fee to a service provider

2.2 Disable Virus Protection Before Running Setup

--------------------------------------------------------------
Some virus protection programs, such as VSafe.com
and Norton AntiVirus AutoProtect, can interfere
with the Microsoft Project 2000 Setup program. If
you use a virus protection program on your computer,
disable it before running Setup. (Don't forget to
re-enable the virus protection program after Setup
is complete.)

2.3 Using Punctuation Characters in Folder Names During

Setup May Cause Problems
--------------------------------------------------------------
Do not use a comma (,), single quotation mark ('), or
exclamation point (!) in the name of the folder where you
install Microsoft Project 2000. It is recommended that you
use the default folder or use only letters and numbers
in folder names.

2.4 System Permissions Necessary to Install Microsoft Project

2000
--------------------------------------------------------------
To install Microsoft Project 2000 on Windows 2000 or on
Windows NT 4.0, you must run Setup with elevated privileges.
Elevated privileges give an installation program administrator
rights to install software into system areas.

To run the installation with elevated privileges, you can use

one of the following methods:
* Log on to the user�s computer as an administrator before
running the installation program.
* Advertise the Windows Installer package. When the user first
runs the application, the Windows Installer completes
the installation under administrator privileges.
* Use Windows system policies to allow all Windows Installer
packages to install with elevated privileges.
* Use Systems Management Server and run the Package Command
 Manager as a service on the user's computer so that
it runs with administrator privileges.
* Power Users can only install Office on Windows 2000 when
an administrator has advertised the installer package
(MSI file) for the applications

For more information about installing Office-related software

with elevated privileges, see Installing Microsoft Project
with Elevated Privileges on Windows NT 4.0 or Windows 2000
in the Microsoft Project 2000 Resource Kit.

Additional information, including network and administration

issues, can be found on the Microsoft Project Resource Kit Web
site at:

http://www.microsoft.com/office/project/prk

2.5 Installing System Updates

-------------------------------------------------------------
In order to run optimally, your system may need to be updated.
For more information on the available updates and how to apply
them, on the Microsoft Project 2000 CD, go to the Support folder
and read the file named "Readmore.txt".

2.6 Installing Microsoft Project 2000 on a Network

-------------------------------------------------------------
To create an administrative installation point for
Microsoft Project 2000, follow these steps:

1. Create a share on a network server for the administrative

installation point.
The network share must have at least 260 megabytes (MB)
of available disk space.
2. On a computer running Microsoft Windows 95 or 98, or
Microsoft Windows NT or Microsoft Windows 2000 that has
write access to the share, connect to the server share.
3. On the Start menu, click Run, and then click Browse.
4. On the Microsoft Project disc in the CD-ROM drive,
select Setup.exe and click Open.
5. On the command line following Setup.exe, type

/A INSTALL.MSI

and click OK. For example:

E:\SETUP.EXE /A INSTALL.MSI

6. When prompted by Setup, enter the CD Key and enter the

organization name that you want to define for all users
who install Microsoft Project from this location.
7. When prompted for the installation location, enter the
server and share you created.

For additional information about network and administration

issues, see the Microsoft Project Resource Kit Web site at:

http://www.microsoft.com/office/project/prk

2.7 Prompt for CD Key When Setting Up Microsoft Project 2000

 from Administrative Installation
------------------------------------------------------------
When you set up Microsoft Project 2000 on your computer from
an administrative installation on a server, you might be
prompted for a CD Key. This will occur if the system
administrator who created the administrative installation
did not enter the CD Key.

To solve this problem, ask the system administrator to create

a new administrative installation and enter the CD Key in
the first dialog box. Once this is done, you will not be
prompted for the CD Key when you run Setup from this new
administrative installation.

2.8 Unexpected Message During Installation

------------------------------------------------------------
If you get an unexpected message during Microsoft Project
setup, and you get the same message when you try setup again,
you can create a log file that will be useful to Microsoft
Product Support Services in troubleshooting the problem. Once
you create the file, you will need to contact Microsoft Product
Support Services.

To create the log file:

1. Click the Start button on the taskbar, and then click

Run.
2. In the Open box, type:

<PATH>\SETUP.EXE /L*V C:\VERBOSELOG.TXT

where <PATH> is the location of SETUP.EXE.

For example, if you are installing from a CD-ROM drive,
then the text you would type might look like:

E:\SETUP.EXE /L*V C:\VERBOSELOG.TXT

3. Click OK.

Setup will start again and a log file called Verboselog.txt

will be created at the root of your C: drive.

2.9 Installing Microsoft Project 2000 on a System that

Had a Beta Version of Microsoft Project 2000 Installed
-----------------------------------------------------------
When starting Microsoft Project, you may receive the
following message:

"File Format Error

This file was created in a pre-release version of Microsoft

Project and cannot be opened."

When you click OK, everything seems normal. Upon exiting

Microsoft Project 2000, you will see the message:

"A file with this name already exists. To replace the existing
file, click OK. To type a different name for the file, click
Cancel."
You will see this behavior if a beta version of Microsoft
Project 2000 has been installed and if the "profile" copy
of the Global.mpt file has not been removed.

The beta versions of the Global.mpt file are not compatible

with the final version. Therefore, when exiting and when
prompted to replace the file, in most all circumstances you
can click OK.

The exception is if your Global.mpt file contains custom

macros that you wish to preserve. If your Global.mpt file
contains custom macros, you can click Cancel on the Exiting
message to prevent the Global.mpt file from being overwritten.
You will then need to remove Microsoft Project 2000 and
reinstall the beta version. Once the beta version is
installed, you can go into the Visual Basic Editor and export
your modules into text files. All other custom elements such
as views, filters, and tables should not be migrated to the
final release of Microsoft Project.

For more information on exporting modules, while in the Visual

Basic Editor, press key F1 and in the Answer Wizard, type the
query "Import file and Export file"

2.10 Using Files Created in a Beta Version of Microsoft

Project 2000
-----------------------------------------------------------
Project files created in a beta version of Microsoft Project 2000
cannot be opened directly in Microsoft Project 2000. To use beta
files you need to open the files in the beta version that created
them, and then on the File menu, click Save As. In the Save As
dialog box, choose the "Microsoft Project 98 (*.mpp)" format.

2.11 Microsoft Project 2000 Shortcut on the Programs Menu Varies

According to Your Operating System
-----------------------------------------------------------
The Microsoft Project 2000 shortcut on the Programs menu might
have the following problems:
1. It does not self-repair the program.
This problem occurs because your operating system does
not support Windows Installer shortcuts. Only the following
versions of Microsoft Windows support these shortcuts:
* Windows 98
* Windows 95 with Internet Explorer 4.01, Service Pack 1, and
Active Desktop installed
* Microsoft Windows NT version 4 with Internet Explorer 4.01,
Service Pack 1, and Active Desktop installed
* Windows 2000
Note: If you install Internet Explorer 5 on a computer
that has either Windows 95 or Windows NT version 4 and
that has Internet Explorer 4.01, Service Pack 1, and
Active Desktop installed, it will still support
Windows Installer shortcuts.
2. It does not install the program on first use.
This problem occurs because Installed On First Use is not an
option for Microsoft Project in the Selecting Features dialog
box during setup. Installed On First Use is not an option
because your operating system does not support Windows
 Installer shortcuts. The operating systems listed under 1.
support Windows Installer shortcuts.
3. It does not display a path on the Shortcut tab of the
Properties dialog box for the shortcut. This indicates
that the shortcut is a Windows Installer shortcut.
Windows Installer shortcuts do not directly reference
the path of the shortcut target. Instead, they contain
a token that the Windows Installer resolves to the path
of the shortcut target. The operating systems listed
under 1. support Windows Installer shortcuts.

______________________________________________________
3. WORKING WITH MICROSOFT PROJECT 2000

3.1 Custom Field Formulas that Contain Nested Date Functions

May Crash
----------------------------------------------------------
If you create custom field formulas that use the built-in
date functions (those that have a prefix of "Proj"), Microsoft
Project 2000 may crash.

Due to bugs found in the Jet Expression Service system component,

you will need to install a service pack to have this work properly.
Windows 2000 users should install the Service Pack 1 update.
Users of all earlier versions of Windows should install the
"Service Pack 4 update for Jet." For more information on the
Jet service pack, please go to:

http://support.microsoft.com/support/kb/articles/Q239/1/14.ASP

For more information on this issue, please go to:

http://support.microsoft.com/support/kb/articles/Q254/3/92.ASP

3.2 Working with Multiple Projects and Resource Pools

----------------------------------------------------------
The Microsoft Project Specifications topic in Help states:

Sharer files connected to a resource pool

999 (that is, maximum open project files minus 1

for the resource pool itself)

The number of projects you can connect to a resource is

dependent on the version of Windows you're using and the
file format you save to (MPP files vs. ODBC Databases) The
number of sharing projects connected to a resource pool
are:

MPP ODBC

Microsoft Windows NT and

Windows 2000: 773 997

Microsoft Windows 95 and 98 998 997

3.3 Working with Inserted Projects, Resource Pools,

and Cross-Project Links in a Mixed Microsoft
Project 98 and Microsoft Project 2000 Environment
----------------------------------------------------------
Microsoft Project 2000 can save files to the Microsoft
Project 98 MPP format. If you wish to maintain some
projects in the Microsoft Project 98 format with others
in the Microsoft Project 2000 format, to help maintain
the links between projects that will work on both Microsoft
Project 98 and Microsoft Project 2000, it is best to keep
your files in a shared network location. If all files will
be in the 2000 format, then having a mixed situation of some
files on a local hard drive and others on a shared network
folder will work fine.

Note: If your Microsoft Project 98 format projects reside

in a database, (SQL Server, Oracle, or Access), there is
no way to maintain them so that both Microsoft Project 98
and Microsoft Project 2000 users can work on the same
projects. When a project is opened from a database and
saved, all of the data is "copied" to a new database schema,
which Microsoft Project 98 does not understand.

It should also be noted that if the resource pool is a

Microsoft Project 98 version file, that any Microsoft
Project 2000-specific features such as Resource Availability
will be lost when connecting to the resource pool.

3.4 Having More than One Version of Microsoft Project

Installed
----------------------------------------------------------
If you have installed both Microsoft Project 98 and Microsoft
Project 2000 on the same system, some functions may not
work properly. For information on some of these issues,
please go to:

http://support.microsoft.com/support/kb/articles/Q245/8/39.ASP

_______________________________________________________
4. MICROSOFT VISUAL BASIC FOR APPLICATIONS

4.1 Use F3 to Find Next Text Occurrence in the Code Window

----------------------------------------------------------
Press F3 to find the next occurrence of previously specified
search text in the code window, not SHIFT+F4 as stated in the
documentation.

4.2 New Properties (VBA)

----------------------------------------------------------
The following are new properties that apply to class
modules in standalone projects:

* Instancing Property

Sets a value that specifies whether you can create instances

of a public class outside a project, and if so, how they will
behave. Not available at run time.

Settings

The Instancing property has these settings:

 Setting Description

1 Private (default). Other applications are not

allowed access to type library information
about the class and cannot create instances
of it. Private objects are only for use within
your component. The Instancing property default
varies depending on the project type. Private is
the default only for class modules in standalone
projects.

2 PublicNotCreatable. Other applications can use

objects of this class only if your component
creates the objects first. Other applications
cannot use the CreateObject function or the New
operator to create objects from the class.

* Name Property

Returns the name used in code to identify a class.

Read-only at run time.

Syntax

object.Name

The object placeholder represents an object expression that

evaluates to a class.

Remarks

An object's Name property must start with a letter and can

be a maximum of 40 characters long. It can include numbers
and underline (_) characters but can't include punctuation or
spaces. Although the Name property setting can be a keyword,
property name, or the name of another object, this can create
conflicts in your code.

4.3 Modifying Macros Contained in the Global.mpt File

----------------------------------------------------------
The macros contained within the Global.mpt file are
digitally signed. If you change an existing macro
or you add or delete macros, when you exit Microsoft
Project 2000, you will see the following message:

"You have modified a signed project. You do not have the

right key to sign this project. The signature will be
discarded."

When you click OK, the digital signature is removed.

_______________________________________________________
5. MICROSOFT PROJECT CENTRAL

5.1 Installation Requirements for Microsoft Project

Central
----------------------------------------------------------
For more information on installing and configuring Microsoft
Project Central, please see the document on the Microsoft
Project 2000 CD titled "Svrsetup.htm" You can find this
document on the CD in the following folder location:

[CDDrive]:\PJCNTRL\HELP\1033\svrsetup.htm

5.2 Security Setting Changes for RDS Applications

----------------------------------------------------------
When Microsoft Project Central is installed, security for
running Remote Data Service (RDS) applications is changed
on the Internet Information Server (IIS). By default on
Windows 2000, RDS applications are disabled, which would
prevent Microsoft Project Central from working correctly.
The setup program gives all IP addresses and domain names
"Granted Access." For more information on the security
changes made by setup to enable RDS applications to run,
please go to:

http://support.microsoft.com/support/kb/articles/Q243/2/45.ASP

_______________________________________________________
6. EXCHANGING FILES WITH MICROSOFT PROJECT 98

Microsoft Project 2000 allows you to save projects to the

Microsoft Project 98 file format. To do so, on the File
menu, click Save As. In the Save As dialog box, choose
the "Microsoft Project 98 (*.mpp)" format.

In order to ensure that macros are transferred properly

when saving to the Microsoft Project 98 format, Microsoft
Project 2000 adds a VBA statement in the Project_Open event.
This statement forces Microsoft Project 98 to save the macros
in the version of VBA that ships with Microsoft Project 98.
This statement is:

ThisProject.VBProject.Description = ThisProject.VBProject.Description

The comment on this statement says:

"While saving your file to Microsoft Project 98 format, Microsoft

Project 2000 added this line to ensure that your VBA macros
are loaded properly."

This statement simply sets the Description of the VBProject

to its current value. Nothing changes in the file, but this
causes the VBA information in the file to be saved by
Microsoft Project 98.

If a Project_Open event handler exists, Microsoft Project

2000 adds this statement at the beginning of the existing
subprocedure. If the existing subprocedure already has a line
that matches the line Microsoft Project 2000 is trying to
add, the first occurrence of such a line in that subprocedure
will be deleted and the new one will be added to the top of
the subprocedure to ensure that this statement will be executed
by Microsoft Project 98. If a Project_Open event handler does
not exist, Microsoft Project 2000 will create one and add
this statement.

Opening such a project in Microsoft Project 98 will display

the Macro Virus warning dialog. You should click the Enable
Macros button to allow the Project_Open subprocedure to run
and cause Microsoft Project 98 to save the VBA information.
If you click the Disable Macros button and then open the
Visual Basic for Applications editing environment or run a
macro, Microsoft Project 98 will not properly save the VBA
information and will place the VBA information in a state
that will render it inaccessible in both Microsoft Project
98 and Microsoft Project 2000.

If you have saved a project to the Microsoft Project 98 format

and later choose to save to the Microsoft Project 2000 format,
this VBA statement will remain. If you want to digitally sign
the project, you should remove this statement. If you do not,
when the project is opened in Microsoft Project 2000, the
description of the VBProject will be modified, and saving the
project will not retain the digital signature.

For more information, please go to:

http://support.microsoft.com/support/kb/articles/Q255/0/28.ASP