INFO: Readmeis.htm-Microsoft Visual InterDev Release Notes (167451)


The information in this article applies to:

  • Microsoft Visual InterDev 1.0
This article was previously published under Q167451

SUMMARY

Microsoft Visual InterDev Release Notes

(C) Copyright Microsoft Corporation, 1997. All rights reserved.

This document provides late-breaking or other information that supplements the Microsoft(R) Visual InterDev(TM) documentation. Late-breaking information about Visual Database Tools is provided in a companion Readme. For the most recent information about common questions and solutions to any issues you might have with Visual InterDev, see the FAQ on

http://msdn.microsoft.com/vinterdev/.


Contents

  • Versions
  • Installation Notes
  • Special Notes and Known Problems

Versions

This section lists the versions of all of the components in Visual InterDev:

Client:
  • Internet Explorer: Version 3.01 (build 4.70.1215)
  • Visual InterDev: Version 1.0
Server:
  • FrontPage(TM) Server Extensions: Version 2.0 (build 1112)
  • Active Server Pages: Version 1.0 (build 1.13.24)
  • Personal Web Server: Version 1.0a (build 1181a)
  • ODBC: Version 3.0 (build 2301)

Installation Notes

For information on installing Visual InterDev, see the Getting Results with Visual Studio book or the CD liner.
  • Removing Beta versions of Visual InterDev or Internet Studio components
  • Installing the Oracle ODBC driver
  • Installing the SQL Server Service Pack 2
  • RISC versions of Visual InterDev Server components are available
  • Upgrading from FrontPage Personal Web Servers

Removing Beta versions of Visual InterDev or Internet Studio components

If you have installed any pre-release versions of Microsoft Visual InterDev (formerly known as Internet Studio) or any of the components that are included with Visual InterDev such as the FrontPage Server Extensions or Active Server Pages, you must remove them. This will help to ensure that the released versions of these components will be correctly installed.

NOTE: For the most recent updates to these instructions, please visit the Visual InterDev Web site at http://msdn.microsoft.com/vinterdev/.

To remove all Beta versions of Visual InterDev or Internet Studio:
  1. Double-click the Add/Remove Programs icon in Control Panel, and then remove the Beta client software, labeled "Microsoft Internet Studio" or "Microsoft Visual InterDev".
  2. Restart your computer.
  3. Remove all the Beta components in the same way. This includes Microsoft Active Server Pages, Microsoft FrontPage 97 Server Extensions, and a beta-only component, the Microsoft Internet Studio Server.
  4. After the last item has been removed, or when asked, restart your computer.
  5. Find your Beta software directory, either:

    X:\Program Files\DevStudio\Istudio

    -or-

    X:\Program Files\DevStudio\VInterDev

    where X is the hard drive where you have Windows installed.
  6. Now that you have uninstalled the Beta software, back up any data files in these directories and then delete the Beta software directories. You can remove these Beta directories only if you have already uninstalled the Internet Studio or Visual InterDev Beta using the Add/Remove Programs icon in Control Panel.
  7. Remove several Beta registry keys from your system that were added by the Beta.

    NOTE: If you prefer an automated method of updating the registry, you can download a program from http://msdn.microsoft.com/vinterdev/ that will safely remove these keys for you.

    Be very careful when deleting registry entries: deleting the wrong entries can prevent Windows from restarting. If necessary, you can restore the registry by following the instructions in the "Restoring the Registry" section of the Registry Editor Help system. Before rebooting, be sure to read these instructions in case the system is not restored correctly and does not respond.

    To remove the registry keys from the Beta:

    A. Click the Start button and choose Run.

    B. Type regedit.

    C. Navigate in the left pane to each of the following locations, select the specified folder in the left pane, and then press Delete. If you can't find a folder, skip it. For example, to delete the first key, navigate to: 
             HKEY_CURRENT_USER\Software\Microsoft\Devstudio\5.0\Html

    Then, click the HTML folder, and press Delete. Note Do not delete any of the preceding folders, such as "5.0" or "Devstudio."

    Delete the following registry folders:

    - HKEY_CURRENT_USER\Software\Microsoft\Devstudio\5.0\Html
    - HKEY_CURRENT_USER\Software\Microsoft\DevStudio\5.0\IstudioProject
    - HKEY_CURRENT_USER\Software\Microsoft\FrontPage (Internet Studio Edition)
    - HKEY_CURRENT_USER\Software\Microsoft\FrontPage (Visual InterDev Edition)
    - HKEY_CURRENT_USER\Software\Microsoft\FrontPage (Visual Studio Edition)
    - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevStudio\5.0\Products \Microsoft Visual InterDev
    - HKEY_LOCAL_MACHINE\Software\Microsoft\DevStudio\5.0\Products\ Microsoft Internet Studio
  8. Close the registry editor.
  9. Continue by installing the released version of Visual InterDev.
If you still have problems with the server pieces on Windows NT and you have had a Beta version on your computer

Many install issues can be traced to files with improper version stamps, which can be a by-product of Beta versions. Improper version stamps can prevent a file from getting uninstalled and overwritten when reinstalling, leaving your computer in a less-than-optimal or even a non-working state. In almost every case, uninstalling the Microsoft Internet Information Server and then Internet Explorer will reduce your computer to a generic state from which to rebuild. Previous Beta testers should consider the steps below only if the above steps do not work and you are familiar with the Windows NT operating system.
  • Use the Add/Remove Programs icon in the Control Panel:

    1. Uninstall Microsoft Internet Information Server.
    2. Uninstall Microsoft Internet Explorer.
    3. Uninstall Microsoft FrontPage.
    4. Uninstall any Visual Studio (DevStudio) client programs (including Visual InterDev)
  • Delete the Bin directories manually:
NOTE: You should attempt to delete files and directories manually only after you try to uninstall using the Add/Remove programs icon in the Control Panel.

The Bin directories are usually installed in the \Program Files directory as Microsoft FrontPage\Bin, Microsoft FrontPage\Servsupp, and DevStudio. Back up any personal data files in these directories.
  • After deleting the Bin directories:

    1. Reinstall Microsoft Internet Information Server.
    2. Reinstall Microsoft Internet Explorer 3.01 or later.
    3. Reinstall all the Visual InterDev server pieces again.
    4. Reinstall the client pieces if the client will be run on the same computer as the server components.
Installing Windows NT Workstation Peer Web Services After Installing Visual InterDev

This installation order will install incorrect ODBC files. To correct this problem, rerun the Active Server Pages item in the Visual InterDev Master Setup dialog box.

Installing the Oracle ODBC driver

Microsoft Visual InterDev includes a new, recommended Oracle(R) ODBC driver written by Microsoft that you can install for use with Microsoft Visual InterDev. The Oracle ODBC driver is not included with the typical install.

To install the Oracle ODBC driver:
  1. In the Master Setup dialog box, choose Custom.
  2. Choose ODBC.
  3. Select the Oracle driver.
-or-
  1. Insert the Microsoft Visual InterDev CD-ROM in your CD-ROM drive, and go to the \Server\Oracle directory.
  2. Launch the Setup program in this directory.
Note that this driver should be installed on any Web server computers from which you want to access Oracle databases. Note also that the Oracle driver requires SQL*NET 2.3 or later to run properly. You can obtain this software from Oracle Corporation.

Installing the SQL Server Service Pack 2

If you plan to use Visual InterDev with SQL Server 6.5, you will need to first install Service Pack 2 in order to fix some problems that prevent the Visual InterDev database tools from running properly. Service Pack 2 is included on the Visual InterDev CD ROM.

To install the SQL Server Service Pack 2:
  1. Insert the Microsoft Visual InterDev CD-ROM into the CD-ROM drive on the computer that is running SQL Server 6.5, and go to the \Server\SQLSrvSp directory.
  2. Launch Setup.exe.

RISC versions of Visual InterDev Server components are available

Dec Alpha and Power PC versions of the FrontPage Extensions are available on: http://www.microsoft.com/frontpage/.

Upgrading from FrontPage Personal Web Servers

If you installed Microsoft FrontPage on Windows 95, you might have installed the Front Page Personal Web Server instead of the Microsoft Personal Web Server. In order to use Active Server Pages with Visual InterDev, you need to install the Microsoft Personal Web Server that ships with Visual InterDev.

If you attempt to install the Microsoft Personal Web Server that comes with Visual InterDev on a computer that already has the Front Page Personal Web Server, you can get the following error when you click Personal Web Server on the Visual InterDev Master Setup dialog box:

"An older version of Microsoft Personal Web Server was found on your machine. You must uninstall the existing version before setup can continue."

If you have this configuration on your computer, see http://support.microsoft.com/support/kb/articles/q194/4/48.asp for step-by-step instructions on how to migrate your content to the new Microsoft Personal Web Server for Windows 95, or for information on how to make both Web servers co-exist on the same system.

Special Notes and Known Problems


  • Trouble setting permissions back to root Web permissions using dialog box
  • Trouble using design-time controls or accessing events in Global.asa when using unique permissions on Web
  • Missing DLL in Design-Time Control SDK
  • Problems setting ActiveMovie control properties
  • Running out of virtual memory on the Web server
  • Problems dragging and dropping in Windows 95
  • Large Web pages on Microsoft Windows 95b
  • Detecting required fields in Microsoft Access databases with the Data Form Wizard
  • Problems accessing a page that uses Microsoft Access query and linked table
  • Printing a link view
  • Data Range Footer navigation buttons realigned after automatic link fixup
  • Turning on automatic link fixup in Visual InterDev projects
  • Using aggregate functions with queries in the Data Form Wizard
  • Problems filtering with the Data Form Wizard against fixed-length fields
  • Problems saving Oracle stored procedures
  • Special information on active server pages on double byte character systems
  • Problems fixing links with DBCS files
  • FrontPage Server and international content
  • Personal Web Server international installation issues

Trouble setting permissions back to root Web permissions using dialog box

If you use the Web Permission item on the Project menu to display the Web Permission dialog box to grant unique permissions for your Web (as opposed to using the same permissions as the root Web), you won't be able to use the dialog box to change the unique permissions back to match the root Web. If you select the option "Use Same Permissions as Root Web" in the Web Permission dialog box and click OK, nothing will happen.

To grant the same permissions as the root Web to your project, use the Copy Web command on the Project menu to copy the content of your Web to a new project on the same server. This copies your content but sets your permissions to be the same as the root Web.

Trouble using design-time controls or accessing events in Global.asa when using unique permissions on Web

If you use the Web Permission command on the Project menu to display the Web Permission dialog box, and then select the Use Unique Permissions for this Web option to secure your Web site, the events in your Global.asa file will not execute when users browse your Web. This causes any design-time controls used on your site to stop working properly, because they depend on state that gets set in these events.

This problem occurs because this setting of the Web Permission dialog box removes read permissions for the anonymous user from the Global.asa file, and Active Server Pages requires read permissions for the anonymous user in the Global.asa file in order to process this page.

To give read permissions for the Global.asa file to the anonymous user, follow these steps on Windows NT:
  1. Find the Global.asa file for your project under the WWWRoot directory on your Windows NT Web server.
  2. Right-click this file, and choose Properties.
  3. On the Security tab, click Permissions.
  4. In the File Permissions dialog box, click Add, and then type the name of your anonymous user in the Add Names box. Make sure the Type of Access box has Read selected and click OK.
For example, if the anonymous user is named "IUSR_MYMACHINE" and your server is named "MyMachine" you would type "MyMachine\IUSR_MYMACHINE" in the box.

NOTE: To determine the name of the anonymous user of your Windows NT Web server, run the Internet Service Manager (from the Microsoft Internet Server group on the Windows NT Start Menu), and then double-click the WWW service for your computer. The name of the anonymous user is listed in the Anonymous Logon section of the dialog box that appears.

Missing DLL in Design-Time Control SDK

If you install the Design-Time Control SDK from the \Client\VIntDev\Misc\SDK directory on the Visual InterDev CD ROM, and then try to insert any of the sample controls that get installed into a Web page, Visual InterDev might stop. The install program for this SDK does not properly put one of the required DLLs into the Windows path.

To correct the problem, copy the file Vbiserv.dll from Samples\Vb\Common (where you installed the SDK) into your Windows\System directory, or put the SDK Samples\Vb\Common\ directory on your Windows path.

Problems setting ActiveMovie control properties

If you use the ActiveMovie control in HTML pages or ActiveX Layout pages, you might experience problems setting properties in the Properties window. This is a known problem with the ActiveMovie control.

Running out of virtual memory on the Web server

After creating many new Webs on your Web server, you might get a warning that your server is running low on virtual memory. This is not a problem in normal usage, and will only affect servers where many new Webs are being created without ever stopping and starting the Web server. You can work around this problem by increasing the amount of virtual memory you have available on your Web server computer, and also by periodically stopping and starting the server if you are creating many new Webs.

Problems dragging and dropping in Windows 95

If you installed a previous version of the Microsoft Personal Web Server, included in the public Beta of FrontPage 97 and previously available for download from www.microsoft.com, you might experience problems dragging and dropping. That version of the Personal Web Server was designed to run only on a newer version of Windows 95 shipped by computer manufacturers.

Although the version of the Microsoft Personal Web Server on the Visual InterDev CD-ROM no longer has this problem, installing it will not fix the problem if you installed the previous version. A fix for this problem is available on the Visual InterDev CD-ROM. You should install this fix if you've previously installed versions of Microsoft Personal Web Server from sources other than the Visual InterDev CD-ROM.

To install the fix:
  1. Insert the Microsoft Visual InterDev CD-ROM in your CD-ROM drive, and go to the \Server\PWS\PWSPatch directory.
  2. Read the Readme.txt file in that directory.
  3. Run Pwsfix1.exe.

Large Web pages on Microsoft Windows 95b

If you are running the 'b' version of Microsoft Windows 95 (also known as OS R2), there is a known problem with the version of the Personal Web Server that is included with that platform. If you create a Visual InterDev project on your Windows 95b Web server and add any pages that are bigger than 4K you will get an error: " HTTP Error 500, cannot connect to server." You can correct this problem by installing the version of Personal Web Server that is included with Microsoft Visual InterDev. To install:
  1. Remove the existing version of the Personal Web Server by double- clicking the Network icon in Control Panel, choosing Personal Web Server, and clicking Remove.
  2. Install the version of Personal Web Server from the Visual InterDev Master Setup dialog box.

Detecting required fields in Microsoft Access databases with the Data Form Wizard

There is a known problem with the Microsoft Access ODBC driver that prevents the Data Form Wizard from correctly determining which fields need to be included in the data form in order to properly update records. This means that the fields displayed in the Data Form Wizard as required might not be, and that some fields that are not marked as required might actually be required. To work around this problem, use Microsoft Access to check which fields in your database are actually required before launching the wizard, and ensure that you've included them in your data form.

Problems accessing a page that uses Microsoft Access query and linked table

You might experience Web server problems if you are trying to run a Microsoft Access Query that uses a linked table on a Web page. Microsoft Access queries with linked tables on Web pages are not supported with the version of the Microsoft Access ODBC driver that is included with Visual InterDev. This problem occurs only on a Web page since it allows multiple users to access the database and causes threading issues with the Microsoft Access ODBC driver. This problem will not occur with applications that do not use multiple threads against the Microsoft Access ODBC driver.

Printing a link view

You can print a link view on any printer that supports raster graphics.

By default, your link view is printed at the current zoom level. If you want to enlarge or reduce your link view, select a different zoom setting.

The icons and links that appear in your link view will print exactly as shown on the screen with one exception: objects that are selected in your link view do not appear in their selected state in your printout. If you want to include icon labels in your printout, make sure they are visible in your link view. Labels appear at zoom levels higher than 40%.

Data Range Footer navigation buttons realigned after automatic link fixup

If you have automatic link fixup in your project turned on (the default is off) and link fixup corrects links in a file that contains a Data Range Footer Design-Time control, the file is modified so that the navigation buttons in the footer are aligned vertically instead of horizontally. To fix this problem, open the file with the problem, right-click the Data Range Footer, choose Edit Design-Time Control, and then immediately close the Object editor that is opened. This causes the Data Range Footer control to automatically replace its output with the correct output.

For information about automatic link fixup, see the next item.

Turning on automatic link fixup in Visual InterDev projects

When you move or rename a file in a Visual InterDev project, Visual InterDev can automatically fix any links that referred to this file so that they point to the new file name or location. This useful feature can save you a lot of time fixing broken links. However, this feature is turned off by default since it has two side-effects that some users dislike. If link fixup is turned on, the process of fixing up links also reformats the white space in pages that are affected, according to an algorithm that tries to make the pages look reasonable. However, this changes the original formatting in the page. In addition, this process might automatically add tags that the link fixup engine believes are missing, even though the tags aren't missing, just embedded in script. In pages that contain server-side script, this can sometimes result in errors when the page is viewed in a browser.

If you want to turn on link fixup so that Visual InterDev automatically fixes links to files when they are moved, follow these steps:
  1. On the File menu, click Open, and then open your project.
  2. In FileView, right-click the project node and click Properties.
  3. On the General Tab, set Link Repair to On.
This feature is stored on a per-project basis, so you will need to turn it on in all the projects whose links you want to be automatically fixed.

Using aggregate functions with queries in the Data Form Wizard

If the Data Form Wizard cannot determine the result columns in your query, check that you're not using aggregate functions (for example, Count or Sum) in the SQL statement you supplied to the wizard. To use aggregate functions with the Data Form Wizard, you must use a SQL alias in order for the data form to generate proper references for the query.

For example, the following Group By query: 
   Select city, Count(population) From state Group By city

would need to be changed to: 
   Select city, Count(population) as Persons From state Group By city

Problems filtering with the Data Form Wizard against fixed-length fields

If you use the filter mode of the pages created by the Data Form Wizard, you need to specify a wildcard character ("%") after data you want to filter on if that data is contained in a fixed-length character field in the database. This is because Active Data Objects (ADO) pads the field with spaces up to the field width. For example, if you want to search for all entries called "Cars" in a fixed-length field of eight characters, the filtering tries to compare "Cars" with "Cars " which doesn't match. In this example, the workaround would be to specify "like 'Cars%'" as the search criteria.

Problems saving Oracle stored procedures

This problem happens only if you try to save twice after creating an Oracle stored procedure without closing the editing window after the first save. When you create an Oracle stored procedure, Visual InterDev adds the following line as part of the default text of your stored procedure: 
   Create /*OR REPLACE*/....

The "OR REPLACE" part of the line is commented out to prevent users from accidentally overwriting stored procedures with the same name that already exist on the system. However, after you save the procedure once, you need to remove the comment characters in this line if you want to save again before closing. Otherwise, you will get an error that says "Can't save because this object already exists" when you try to save for the second time. If you close and reopen the stored procedure, the comment characters surrounding "OR REPLACE" are automatically removed.

Special information on active server pages on double byte character systems

There are some known problems with double-byte character sets (used in Far East systems) and the version of Active Server Pages shipping in Version 1.0 of Visual InterDev. A new version of Active Server Pages that has these problems fixed will be posted on the Web very soon after Visual InterDev is available in stores. To get the new version when it is available, visit the Visual InterDev Web site at http://msdn.microsoft.com/vinterdev. Information on how to download the fixed version will be posted there.

The following is a list of known DBCS issues:
  • DBCS Project names return "HTTP/ 1.0 404 object not found" when used with the Personal Web Server on Windows 95
If you name a Web created with Visual InterDev using DBCS characters, and you are creating this Web on the Personal Web Server for Windows 95, you will get the error "HTTP/ 1.0 404 object not found" when trying to access any pages in the Web. If you name your Web using SBCS (single byte character system) characters, you will be able to access pages, even if the pages themselves use DBCS names. In addition, if you create the Web on a server on Windows NT, you will also be able to access the pages. This problem occurs only on the Personal Web Server on Windows 95.
  • DBCS named query string elements or form elements always return an empty value from Request.QueryString() method
If you pass variables from page to page using an HTTP query string or HTML form element, and either type of variable is named using DBCS characters, when you try to access them using the Request.QueryString() method in server script, you might get an empty string instead of the actual value of the variable. The workaround is to name your HTTP query string variables or form elements using SBCS characters.
  • Extra characters might be returned when using Request.QueryString() and Request.Cookies() methods with DBCS data
If you pass variables from page to page using an HTTP query string or HTML form elements, and either type of variable is passing data that contains DBCS characters, extra characters might be appended to the end of the data when it is retrieved using the Request.QueryString() method in server script. This can occur even if the name of the element is SBCS. It is the DBCS data, not the name, that causes the problem in this case. The workaround is to pass only SBCS data from page to page using cookies, form elements, or query strings.
  • Using PATH_INFO and PATH_TRANSLATED values with Request.ServerVariable() method might return extra characters
If you use the Server.ServerVariable() method and pass it values of PATH_INFO or PATH_TRANSLATED, the value returned might have extra characters on the end of the path if any part of the path has DBCS characters in it. The workaround is to use only SBCS names for Web names, path names, and file names.
  • Server.MapPath() method might return extra characters when used with DBCS path
If you call the Server.MapPath() method any DBCS characters in the path, extra characters might get appended onto the end of the value returned by the method. The workaround is to use only SBCS names for Web names, path names, and file names.

Problems fixing links with DBCS files

If you name a file using double-byte characters and then move or rename it, files with HTML links to this file will not be automatically fixed to point to the new location. To work around this problem, name your files using SBCS (single byte character set) characters instead.

FrontPage Server and international content

For the FrontPage97 Server Extensions to work properly with international Web content, the Web server on which the extensions are installed must have code pages installed for each language used by the content stored on that server. For example, if you store Japanese documents on a US English Web server and wish to view and author those Japanese documents using FrontPage97, then the Web server computer must have the Japanese code pages installed.

Several language packs are available on the Visual InterDev CD ROM so that you can add the appropriate code pages to your server. Look in the \Server\LangPack directory on the Visual InterDev CD ROM to find the language packs and a Readme file that describes how to use them.

Personal Web Server international installation issues

The Visual InterDev master setup prevents users from installing a language version of the Personal Web server that does not match the language of the operating system. If you are running a non-English Windows 95 and would like to install Personal Web Server, please download your language version from the Microsoft Web site.

This check was implemented because of a problem with the Win95 file Rpcrt4.dll that Personal Web Server installs. There are three versions of Rpcrt4.dll with different base addresses shipping across the different language versions of Windows 95. Overwriting an existing Rpcrt4.dll with an incorrect base address version of this file will cause your Windows 95 installation to become unstable.

If there is no Personal Web Server version for your language available, please check with your local Microsoft Technical Support for the proper Personal Web Server installation process for your language.

------------------------------------------------------------------------
PhotoDisc Credits

Some of the images in the Visual InterDev sample files were obtained from PhotoDisc, Inc. This credit information is a requirement for using those images.

A Powerful Edge.

PhotoDisc award-winning photos give you an exciting edge and more visible impact in your Web projects. To obtain high-resolution images, contact PhotoDisc online or over the phone.

We've Taken Care of Everything For You.

As the highest-rated producer of professional digital photography, PhotoDisc has the keys to getting the image right, every time. Each of the photographs is chosen from the portfolios of award-winning photographers, carefully scanned with the highest quality scanning technology, color- corrected and stored in full-color for dazzling impact.

Ready for More?

The PhotoDisc digital photography series currently features over one hundred high-resolution Volumes on CD-ROM with a broad offering of subjects and over 50,000 images available online. Approximately 4,000 new images are released every quarter. PhotoDisc Volume subjects range from Business to Italian Fine Art to American Retro images and Everyday Objects.

In a hurry? Look to our World Wide Web site for incredible image-searching tools and immediate single-image purchase and downloading!

http://www.photodisc.com

For more information about PhotoDisc, please contact us directly.

Please call or fax for a FREE product catalog or for further assistance.

Within the US: 800-528-3472 Fax (206) 441-9379
Outside the US: (206) 441-9355 Fax: (206) 441-9379
From Europe+ 44 (0) 181 332 2020 Fax + 44 (0) 181 1506 461 510
UK Free Phone0800 697 622

Online

World Wide Web: http://www.photodisc.com Internetsales@photodisc.com
techsupport@photodisc.com Supportwebtech@photodisc.com
No other source can provide you with images of such high quality and breadth, royalty-free and ready for immediate use.

PhotoDisc Inc.
2013 4th Avenue
Seattle, WA 98121
USA

Copyright 1997 PhotoDisc, Inc.

REFERENCES

Readmeis.htm

For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site:

http://support.microsoft.com/search/default.aspx?qu=vinterdev

Modification Type:MajorLast Reviewed:5/2/2006
Keywords:kbExtension kbinfo kbreadme kbServer KB167451
©2004 Microsoft Corporation. All rights reserved.