INFO: Visual InterDev 6.0 READMEVI.HTM file

ID: Q191278

The information in this article applies to:

Microsoft Visual InterDev, version 6.0

SUMMARY

Below is the text contents of the Visual InterDev 6.0 Readmevi.htm file. This file is found where Visual Studio or Visual InterDev was installed, for example C:\Program files\Microsoft Visual Studio.

MORE INFORMATION

Visual InterDev Readme Copyright 1998 Microsoft Corporation. All rights reserved.

Other product and company names herein may be the trademarks of their respective owners.

Visual InterDev Readme includes updated information for the documentation provided with Microsoft Visual Studio - Development System for Windows and the Internet. The information in this document is more up-to-date than the information in the Help system. Many of the issues outlined in this document will be corrected in upcoming releases.

For general installation issues on the Visual Studio 6.0 suite of products, including side by side product installation for installing more than one Visual Studio product on the same computer, see the Installation Notes Readme (Install.htm).

For issues that are specific to the Microsoft Visual Database Tools which are installed with Visual InterDev, see the Microsoft Visual Database Tools Readme. For issues on the Help system, see the MSDN, the Microsoft Developer Network Readme.

Visual InterDev Installation Notes

==================================

Installing Visual InterDev

You can install Visual InterDev on a client and on a server. The steps below are required for installing both the client and server portions of Visual InterDev. Note that you will need to install some server components with a client installation.

Insert installation compact disc #1 into your computer.

Setup.exe automatically runs the Installation Wizard. The wizard steps you through the installation process.

NOTE: Depending on your selections and your current configuration, the wizard will prompt you to install different required components and to reboot Windows one or more times during the installation process. After each reboot, the wizard automatically returns to the proper step.

Follow the steps of the Installation Wizard until you are prompted to select either Install Visual InterDev 6.0 or Server Applications.

To install the client portion of Visual InterDev, select Install Visual InterDev 6.0 and then see Client Installation below.

To install the server portion of Visual InterDev, select Server Applications and then see Server Installation below.

If you want to install the client and server portions of Visual InterDev on the same computer, begin with the Client Installation.

Client Installation

If you are using the computer as a client only, you will still need to install certain server components in order to take full advantage of all the product's functionality.

Follow the steps of the Visual InterDev 6.0 Wizard. When prompted, select either a Typical or Custom installation.

After the Visual InterDev client has been installed on your computer, you are prompted to install MSDN, the Microsoft Developer Network. Note that you need to install MSDN in order for F1 Help to work and to have access to the Visual InterDev documentation.

After MSDN is installed, you arrive at the Server Setups screen.

If you are installing the Visual InterDev server on the same computer, stop here and continue with Server Installation below.

If you are installing only the Visual InterDev client on the computer, continue with the following steps for Windows NT or Windows 9x.

If you're installing on Windows NT

The following components are required for the PageNavbar design-time control, remote debugging, and previewing active server pages on your local machine. You may choose not to select these components if you do not want to take advantage of these features.

Select Launch BackOffice Installation Wizard and click Install.

The BackOffice Installation Wizard will prompt you to select a Custom or Visual InterDev Developer option. Select Custom and click Next.

Verify the disk space requirements and click Next.

Select Front Page Server Extensions and MS Data Access Components from the top level of the components list.

Expand the Windows NT Option Pack node and select:

Internet Information Server - for NT Server

Microsoft Management Console

NT Option Pack Common Files

Personal Web Server (PWS) - for NT Workstation

Transaction Server

If you're installing on Windows 9x

The following components are required for the PageNavbar design-time control, remote debugging, and previewing active server pages on your local machine. You may choose not to select these components if you do not want to take advantage of these features.

Select NT Option Pack Common Files and click the Install button. This launches the Microsoft Personal Web Server Setup.

When prompted to select Minimum, Typical, or Custom, select Custom.

When the list of components is displayed, select the following:

Common Program Files

Microsoft Data Access Components 1.5

Personal Web Server (PWS)

Transaction Server

Uncheck the remaining components. As you uncheck the other components, the wizard might display a message that warns you of various dependencies. You can choose Yes to ignore the dependencies because you are using this computer as a client for Visual InterDev, not as a server. Continue with the remaining steps of the Personal Web Server Setup.

When you return to the Server Setups screen, select FrontPage 98 Server Extensions and click Install.

Continue with the remaining steps of the wizard.

Server Installation

You can install the server components on the same computer as the client, or you can install them on a different computer. Follow the steps for Windows NT or Windows 9x below.

Server Installation for Windows NT

Perform the following steps if you're installing the server on Windows NT.

When prompted by the wizard, select Launch BackOffice Installation Wizard and click Install.

The BackOffice Installation Wizard will prompt you to select the Custom or Visual InterDev Developer option. Select the Custom option and click Next.

Select the following options:

Windows NT Option Pack 4.0

MS Data Access Components

Remote Machine Debugging

FrontPage Server Extensions

Visual InterDev Server

Before you click Next, expand the Windows NT Option Pack 4.0 node. In addition to the options selected by default, select the Visual InterDev RAD Remote Deployment Support node. Then expand the Visual InterDev RAD Remote Deployment Support node and select the second instance of Visual InterDev RAD Remote Deployment Support. Make sure that Visual InterDev RAD Remote Deployment Support is selected at both levels.

Click Next and continue with the remaining steps of the BackOffice Installation Wizard.

The following patch corrects problems related to debugging active server pages and for updating the Global.asa file. After the Installation Wizard has finished, apply this patch.

Run \IIS\WinNT\ASP2FIX1.EXE from the installation disc. For Visual InterDev Professional version, it's located on CD1. For Visual Studio Professional version, it's located on CD2. For Visual Studio Enterprise Edition, it's located on CD3.

Reboot when prompted.

Server Installation for Windows 9x

When the Installation Wizard arrives at the Server Setups screen, you will be prompted to make a selection from the Server Components list. Install each of the components as instructed below.

NOTE: In order to assure that your server is set up correctly, you must install the server components in the order that they are listed on the Server Setups screen.

Select NT Option Pack (for Windows 9x) and click Install. This launches the Microsoft Personal Web Server Setup.

When prompted to select Minimum, Typical, or Custom, select Typical. Continue with the remaining steps of the Personal Web Server Setup.

Select FrontPage 98 Server Extensions and click Install.

Select Data Access Components 2.0 and click Install.

Select Visual InterDev Server Components and click Install.

Click Next and continue with the remaining steps of the Installation Wizard.

The following patch corrects problems related to debugging active server pages and for updating the Global.asa file. After the Installation Wizard has finished, apply this patch.

Stop the Web server. In an MS-DOS Prompt window, run the command:


   pws /stop

In the \<windows>\system\inetsrv directory, rename Asp.dll to Asp.old.

Copy \IIS\Win9x\Asp.dll from the installation disc to your \<windows>\system\inetsrv directory.

For Visual InterDev Professional version, it's located on CD1.

For Visual Studio Professional version, it's located on CD2.

For Visual Studio Enterprise Edition, it's located on CD3.

Restart the Web server. In an MS-DOS Prompt window, run the command:


   pws /start

Production Server Installation for Windows NT

To ensure that your Web application will run properly on a production server installed with Windows NT, you must install some of the Visual Studio server components on that computer.

NOTE: Windows 95 and Windows 98 are not recommended as production server platforms for running Visual InterDev 6.0 applications.

The components needed on a production server are:

Windows NT Service Pack 3

Internet Information Server version 3.0 or later (Visual Studio 6.0 includes Internet Information Server 4.0)

Data Access Components (to ensure that your application's data-based operations function correctly)

Visual InterDev server (which installs the proper versions of the scripting engines and the Data Environment run-time files)

Furthermore, if you intend to deploy an application to the production server, you may want to install the FrontPage Server Extensions or the Visual Studio Posting Acceptor.

Perform the following steps to install the server components on a Windows NT production server.

When prompted by the wizard, select Launch BackOffice Installation Wizard and click Install.

The BackOffice Installation Wizard will prompt you to select the Custom or Visual InterDev Developer option. Select the Custom option and click Next.

Select the following options:

Windows NT Option Pack 4.0

MS Data Access Components

Front Page Server Extensions - Optional

Posting Acceptor (2.0) - Optional

Visual InterDev Server

Click Next and continue with the remaining steps of the BackOffice Installation Wizard.

Setting up Your Computer for Stored Procedure Versioning through Microsoft Visual SourceSafe and for Stored Procedure Debugging

If you have the Visual Studio Enterprise Edition, you can set up your computer for versioning and debugging stored procedures. When versioning or debugging stored procedures, the SQL Server will be logging into Visual SourceSafe to perform the necessary operations on the Visual SourceSafe database. Therefore, the SQL Server will require appropriate permissions to perform these actions. To reduce security issues, it is recommended that you set the SQL Server service to run as a logged on user.

To set the SQL Server service to run as a logged on user

Click Start Menu, Control Panel, and then run Services.

Select the service MSSQLServer and click the Startup button.

In the Service dialog box, select the option This Account.

In the This Account text box type a domain and user name (e.g., "domain\username") that has access to the server where the Visual SourceSafe server is installed. Type a password in the Password text box. Click OK.

Stop the MSSQLServer service and then restart it.

If your SQL server is on a different server than your Web server, you need to install the SQL Server Debugging and Visual InterDev Server components on the SQL server. You can install these server components from the BackOffice Installation Wizard.

To install the SQL Server Debugging and Visual InterDev Server components

Run the Visual Studio Enterprise Edition setup.

When prompted, select Launch BackOffice Installation Wizard and click Install.

On the first screen of the BackOffice Installation Wizard, select Custom.

When prompted with a list of BackOffice Programs and Their Components, select SQL Server Debugging and Visual InterDev Server.

Continue with the remaining steps of the wizard.

Installing and Running the Sample Application

In order to run the Sample Gallery application, follow these steps.

To install the Visual InterDev Gallery sample application

In Visual InterDev, if the New Project dialog box isn't visible, choose New Project from the File menu.

In the New tab of the New Project dialog box, select the Sample App Wizard icon, enter a name for the project, and choose Open.

Follow the steps in the Sample Application Wizard.

To run the Visual InterDev Gallery sample

After installing the sample, right-click default.htm in the Project Explorer and choose View in Browser.

If you view the "User Notification" page using Netscape, see Browsing "User Notification" sample using Netscape under "Known Issues".

Note: If you have trouble viewing the data pages, display the Property Pages dialog box for the data connection you created, which appears under the Global.asa file in the Project Explorer. On the Authentication tab, select Save Design time authentication, and make sure that the User name option contains "admin".

Installing FrontPage 98

The installation compact discs include a setup of Microsoft FrontPage 98. It is not necessary to run the FrontPage setup to use Visual InterDev. However, it has been included for your use if you so desire.

To install FrontPage 98

Run \FrontPage\setup.exe from the installation compact disc. Note: If you have the Professional version of Visual InterDev, the FrontPage folder is located on CD 1. If you have the Enterprise version of Visual Studio, the FrontPage folder is located on CD 2.

When prompted on the Setup Type screen to select a Typical or Custom installation, select the Custom option.

On the Select Components screen, make sure that the FrontPage Personal Web Server option is not selected. Visual InterDev does not support the FrontPage Personal Web Server.

NOTE: If you choose to install the FrontPage Personal Web Server on your computer, it is required that you first install IIS version 3.0 or later.

Continue with the FrontPage installation wizard.

=================================================

What's New in Visual InterDev

To find out about the features that are new to this version of Visual InterDev, see the "What's New" topic in the Visual InterDev documentation in the MSDN Library Visual Studio 6.0 documentation. To see the documentation, choose Contents from the Help menu.

For late-breaking news and product updates, be sure to visit the Visual InterDev Web site at http://msdn.microsoft.com/vinterdev.

Known Issues

The following issues are known in this version of Visual InterDev.

Known Issues: Installation

Uninstalling pre-release versions of Visual InterDev WARNING: If you have installed a pre-release version of Visual InterDev 6.0, you must fully remove it before installing this final release version. Some of the older file versions are not compatible with the versions in this release.

It is recommended that you remove previous pre-release versions of Visual InterDev 6.0 by reinstalling the entire operating system on a newly formatted hard drive or on a separate hard drive partition. This will ensure that Visual InterDev and all the components that it depends on are installed properly. The setup program that is used by this final version is new. Therefore, the only way to ensure proper installation of this final version is to install it on a "clean" system.

If installing on a "clean" system is not possible, follow the steps below.

To uninstall a pre-release version of Visual InterDev

Click Start, Control Panel and then run the Add/Remove Programs applet.

Select Microsoft Visual Studio 98 Enterprise Edition.

When prompted, select Remove All.

After you have finished removing the program, open Windows Explorer and delete all files in the \Program Files\Microsoft Visual Studio folder.

Click Start, Run and enter REGEDIT.

In the Registry Editor, delete the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\6.0.

Delete the registry key HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\6.0.

Upgrading Web applications created with a pre-release version

If you used a pre-release version of Visual InterDev to create a Web application, you will need to upgrade the application in order for the script library and the data environment to function correctly.

On the server

Delete the "_ScriptLibrary" directory from the Web application on the server.

On the workstation

Create a new Web project.

When prompted in step 2 of the Web Project Wizard to specify your Web, select Connect to an existing Web application and select your existing Web application from the list box.

If prompted to create a new script library, choose Yes.

NOTE: All developers who use this Web application must create a new Web project on their workstations.

If your project contains data commands, you need to upgrade them. To do this, display the Data Environment, right-click any data command and choose Refresh.

For each page that contains a data-bound control or the PageObject control, you must open the file, switch to Source view, "dirty" it (add and remove a space), switch back to Design view and then save the file.

Because the scripting object model has changed, you need to update all ASP pages that had the scripting object model enabled. You can recognize which pages were enabled by checking to see if they contain the following lines. If the following lines do exist, you need to delete them.

Delete these lines from the top of the ASP page:


   <!--METADATA TYPE="EditorGenerated" startspan <COMMENT>
   Visual InterDev Scripting Object Model - Page Header
   Do not modify between these meta data tags
   </COMMENT> -->
   <!--#include file="_ScriptLibrary/pm.asp"-->
   <% if StartPageProcessing() Then Response.End() %>
   <FORM name=thisForm METHOD=post>
   <!--METADATA TYPE="EditorGenerated" endspan-->

Delete these lines from the bottom of the ASP page:


   <!--METADATA TYPE="EditorGenerated" startspan <COMMENT>
   Visual InterDev Scripting Object Model - Page Footer
   Do not modify between these meta data tags
   </COMMENT> -->
   <% EndPageProcessing() %>
   </FORM>
   <!--METADATA TYPE="EditorGenerated" endspan-->

After deleting the lines, right-click on the editor and choose Properties. Under the ASP settings, select the option Enable the scripting object model. Click OK to close the dialog box and then save the file. Remote Machine Debugging server component must be installed with Windows NT Option Pack

In order to ensure that debugging functions correctly, the Remote Machine Debugging component must be installed when the Windows NT Option Pack is installed. If the Windows NT Option Pack is reinstalled, the Remote Machine Debugging component must also be reinstalled.

Both the Windows NT Option Pack and the Remote Machine Debugging component can be installed by the BackOffice Installation Wizard which is accessed from the Visual InterDev and Visual Studio setup programs.

Installation problems with the Visual InterDev RAD Remote Deployment Support server component

If the Visual InterDev RAD Remote Deployment Support server component was not installed successfully on the server, you will receive the following message when attempting to register a component on the server:

"This feature is not enabled on the master Web server. See the Visual InterDev product documentation to learn how to enable server component registration with FrontPage Server Extensions."

If you receive this message, follow these steps to install the server component in order to avoid the problem when creating new projects:

On the Windows Start menu, choose Settings, and then Control Panel. Double-click Add/Remove Programs.

From the list of software on the Install/Uninstall tab, select Windows NT 4.0 Option Pack.

Click Add/Remove to launch the Windows NT 4.0 Option Pack Setup.

In the Option Pack Setup, click Add/Remove when prompted. This displays a list of the Option Pack components.

Check the Visual InterDev RAD Remote Deployment Support option.

Click Next and continue with the Option Pack Setup.

Then, to correct the problem for existing projects, copy fp30reg.dll from:


   \Program Files\Microsoft FrontPage\version 3.0\isapi\_vti_bin\_vti_aut

to the master server at:


   \inetpub\wwwroot\[projectname]\_vti_bin\_vti_aut

NOTE: If you use the BackOffice Installation Wizard to see which components are installed, the wizard will not display the correct status of the Visual InterDev RAD Remote Deployment Support component. You must view its installation status with Add/Remove Programs on the Control Panel.

Known Issues: Product Related

Source control does not support file names containing semi-colons

If you attempt to enable source control on a Web project that contains a file with a semi-colon (;) in its file name, the product will fail. Avoid using file names containing semi-colons.

Ignore events in the Script Outline view for FRAME, IFRAME, FRAMESET,

OPTION

When you add a FRAME, IFRAME, FRAMESET, or OPTION element to a page, the element's ID will appear in the Script Outline view. If you expand the element in the Script Outline, you will see a list of events. However, these elements do not fire events. Therefore, ignore the events that appear under these elements in Script Outline.

Class names containing underscores are not supported

Class names that contain underscores (e.g., "my_Class") are not supported by Microsoft Internet Explorer 4.0. Therefore, when creating classes in the CSS editor, it is a good idea to create classes without underscores (e.g., "myClass").

The editor does not support "<script>" or "</script>" within JavaScript or VBScript comments

Do not include "<script>" or "</script>" inside JavaScript or VBScript comments. The editor treats the commented <script> tags as if they were uncommented HTML. This results in incorrect color coding and causes event handlers generated by the Script Outline to be inserted in the wrong place.

Visual InterDev does not support the ActiveMovie control

If you manually add the ActiveMovie control to the Toolbox, and then add an ActiveMovie control to a page, Visual InterDev will fail.

When working offline and editing in Design view, relative URLs of image files must be edited manually

You can add an image file to a page by choosing Image on the HTML menu. If you do this when working offline and in Design view, Visual InterDev will create an absolute URL, beginning with "file://", that is local to the machine. To work around this, choose one of the following:

Add the image in Source View.

Add the image in Design view and specify an absolute URL in the Picture Source option of the Insert Image dialog box.

Add the image in Design view and then edit the URL manually in Source view.

Visual InterDev does not support hierarchical recordsets

When you display the properties dialog box for a data command, three tabs appear on the dialog box, General, Parameters, and Advanced. In the Visual Studio help topics for the Command Properties dialog box, there are six tabs listed. Three of these tabs (Relation, Grouping, Aggregates) do not appear in the dialog box when called from Visual InterDev because Visual InterDev does not support hierarchical recordsets.

Changes to Client Script Debugging in ASP Pages

When Internet Information Server (IIS) processes an ASP page, the resulting page sent to the browser can be considerably different than what you see when you edit the ASP page in the editor. Server script can generate new client content dynamically, or conversely, a large quantity of server script can result in only a few lines of client HTML output. This situation introduces problems when you set breakpoints in client script inside an ASP page because the line on which you set the breakpoint can move dramatically within the file by the time the page reaches the browser.

The solution is to enable client-side debugging in ASP pages. Doing so specifies that IIS tracks the location of client script breakpoints in an ASP page, and passes the location of those breakpoints to Internet Explorer, so that Internet Explorer can stop at the correct locations.

The process of enabling client-side debugging for ASP pages is described in the Visual InterDev help topic "Debugging Client Script." However, the process has changed slightly. In the topic, under "Enabling Client Script Debugging for ASP Pages," change Step 3 of the procedure to read:


   Under Server script, make sure that the Automatically enable ASP server-
   side script debugging on launch option is checked.
   Later in the topic, under "Debugging Client Script Within a Solution,"

Step 5 has changed. The text should now read:


   If debugging for client script in ASP pages has not been enabled as
   described above, Visual InterDev displays a message prompting you to
   enable debugging for ASP pages. Your options are:


   Choose Yes if you are working with an ASP page and want Visual InterDev
   to automatically enable debugging.


   Choose No if you if you are working with an HTM page and will not be
   navigating to an ASP page during your debugger session.

Browsing "User Notification" sample using Netscape

The Gallery sample includes a "User Notification" page. In order for this sample to work properly when browsed in Netscape Navigator, you need to enable Basic Authentication for the UserNote directory on the Web server.

To enable Basic Authentication

Open the Microsoft Management Console on your Web server. From the Windows Start menu, select Programs, Windows NT 4.0 Option Pack, Internet Information Server, and then Internet Service Manager.

In the Gallery Web site, right-click the UserNote folder and choose Properties.

On the Directory Security tab, click the Edit button under Anonymous Access and Authentication Control.

In the Authentication Methods dialog box, make sure that Basic Authentication and Windows NT Challenge/Response are selected and that Allow Anonymous Access is not selected.

Click OK to close the dialog boxes.

When browsing the "User Notification" page using Netscape you will be prompted for a user name and password. To be compatible with Microsoft Internet Explorer, enter the domain name and user name (e.g., "YourDomain\UserName") in the User text box.

Issue concerning window_onload event not firing

When you output HTML in server events (for example, by including response.write() statements in the thisPage_onenter event), the browser will create an implied <BODY> tag that overrides the attributes that you may have set on the tag, and the window_onload event is not fired. Therefore, attributes that you may have set on the <BODY> tag will not be used, and the window_onload event is not fired. To avoid this problem, defer all HTML output until the content portion of the page. Use script only to set up state that is used to compose the page. If you need to output HTML prior to the content portion of the page, then you should set the <BODY> tag attributes programmatically using client-side code (for example, window.onload = "return window_onload()").

"[FrontPage vinavbar component]" appears when browsing a page

"[FrontPage vinavbar component]" is displayed by the browser when the navbar bot is not installed properly on the server. To fix the problem, verify that the vinavbar directory exists on the server. It is typically located at "\Program Files\Microsoft FrontPage\version3.0\bots\vinavbar".

If the directory does exist, recalculate the links on the server:

Run Fpsrvadm.exe on the server. Fpsrvadm.exe is typically found in "\Program Files\Microsoft FrontPage\version3.0\bin".

When prompted to "Please enter command," select option #8, "recalculate links."

When prompted to "Enter Web name," press ENTER. Do not type a Web name.

This ensures that links are recalculated for all Webs recursively from the root Web.

If the directory does not exist, reinstall the FrontPage Server Extensions from the installation compact disc by running FP98ext\setup.exe. After they are installed, recalculate the links.

Difference in CSS implementation between Netscape and Internet Explorer

Netscape Navigator and Communicator versions 4.0 through 4.03 implement cascading style sheets (CSS) differently than Internet Explorer. Navigator interprets relative URLs as relative to the document rather than to the linked CSS file. To work around this difference:

Copy, but do not move, all of the images from the directory of the theme that you are using to the directory that contains the document that references the CSS file.

-or-

Change the relative URLs in your CSS files to the appropriate absolute URLs.

Use server-level default document properties only

If you are running an IIS 4.0 Web server, you may encounter a problem with the ability to set a default document (welcome page) for each directory on your Web server. When using Site Designer, the default document information is taken from the Web server's server-level (root-level) properties and not from the directory-level properties. To work around this, set the default document at the Web server's server-level properties page.

NOTE: After you re-set the properties, the change only affects new projects.

Known Issues: Visual Component Manager

"Related Files Tab (Component Properties Dialog Box)" topic incorrect Visual Component Manager User Interface Reference: The topic "Related Files Tab (Component Properties Dialog Box)" incorrectly states that the tab is used to display and enter files that are related to the selected component. In fact, none of the information displayed on this tab can be modified. You can add related files to a component only when publishing or re-publishing the component. For more information, search online, with Search titles only selected, for "Publishing Components" in the MSDN Library Visual Studio 6.0 documentation.

Removing Repository 1.0 Registry Keys

If you installed VCM 5.0 (previously available for Web download) you will have the following Windows Registry keys setup. They were necessary for VCM 5.0 and the 1.0 version of the Repository. If you find the following Registry entries then it is safe to remove them and may, in fact, improve VCM 6.0 performance.


HKEY_LOCAL_MACHINE\Software\Microsoft\Repository\CacheMaxAnnProps
HKEY_LOCAL_MACHINE\Software\Microsoft\Repository\CacheMaxObjects
HKEY_LOCAL_MACHINE\Software\Microsoft\Repository\CacheRelshipMaxCollections
HKEY_LOCAL_MACHINE\Software\Microsoft\Repository\CacheRelshipMaxRows
HKEY_LOCAL_MACHINE\Software\Microsoft\Repository\MaxRowCacheAge

Adding repository tables to an existing .mdb file

If you try to open an existing .mdb file from within VCM that is not a repository database (i.e., it does not contain the repository structure/tables), you will be asked if you want the repository tables added to the database. You should not do this for normal use; the repository should generally be in a separate database. This will work, but it can take as long as 10 minutes to create the repository structure in an existing .mdb file.

To create a brand new .mdb file containing the repository structure, right- click in the folder outline, click Repository, click New, and then enter the name of the file you want to create.

Additional query words: read me readme readme.txt readme.doc

Keywords : kbreadme kbExtension kbFrontPage kbServer kbVisID600 kbGrpASP
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbinfo