DOCUMENT:Q190846 07-AUG-1998 [vbwin] TITLE :BUG: Calling AsyncRead on a File Twice Causes Error 698 PRODUCT :Microsoft Visual Basic for Windows PROD/VER: OPER/SYS:WINDOWS KEYWORDS: ====================================================================== --------------------------------------------------------------------- The information in this article applies to: - Microsoft Visual Basic Learning and Enterprise Editions for Windows, version 6.0 --------------------------------------------------------------------- SYMPTOMS ======== When the all of the following conditions are true: - You are calling AsyncRead on local files. - You are using the same value for the PropertyName argument. - You make the two calls successively. the following error message is displayed: Error 698: PropertyName parameter conflicts with the PropertyName of an AsyncRead in progress Because the AsyncRead is being performed on a local file, the download should be happening synchronously. This means that it should be okay to issue AsyncRead twice in succession. RESOLUTION ========== If you wish to force Synchronous download, use the AsyncReadOption: "vbAsyncReadSynchronousDownload" in your call to AsyncRead. STATUS ====== Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATION ================ Steps to Reproduce Behavior --------------------------- 1. Create a ActiveX Document DLL project in Visual Basic. 2. Put the following code into your Userdocument_Click() handler: AsyncRead "c:\windows\Triangles.bmp", vbAsyncTypePicture, "def" AsyncRead "c:\windows\Triangles.bmp", vbAsyncTypePicture, "def" 3. Compile the project into a DLL. 4. Start Internet Explorer 4.x and navigate to your .VBD file. 5. Click on the Document and note that you see the above-mentioned error message. Additional query words: kbDSupport kbVBp600bug kbdsi kbVBp kbInternet kbNoKeyWord <<>> 190814 <<>> 1 <<>> HOWTO: Display a ReadMe File at the End of Setup <<<LONGTITLE>>> HOWTO: Display a ReadMe File at the End of Setup <<<PRODUCT>>> vbwin <<<PRIORITY>>> 2 <<<SECURITY>>> PUBLIC <<<AUTHOR>>> susanvi <<<EDITOR>>> pjriker <<<EDITSTATUS>>> Released <<<TECH>>> KWKOU <<<TECHSTATUS>>> Approved <<<EXPIREDATE>>> Dec 31 1999 12:00AM <<<MESSAGE>>> <<<KEYWORD>>> <<<INTERNALADMIN>>> <<<QUESTION>>> <<<PRODVERNUM>>> <<<COMPONENT>>> <<<TECHNOLOGY>>> <<<LINKS>>> <<<RAIDINFO>>> <<<INCIDENT>>> <<<SWEEPDATE>>> <<<SWEEPSTATUS>>> <<<SOLUTIONTYPE>>> <<<ISSUETYPE>>> kbhowto <<<PLATFORM>>> WINDOWS <<<HARDWARE>>> <<<BOILERPLATE>>> <<<PRODUCEDVIEW>>> <<<TEXT>>> --------------------------------------------------------------------- The information in this article applies to: - Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 6.0 --------------------------------------------------------------------- SUMMARY ======= This article demonstrates how to modify the Setup Toolkit project (Setup1.vbp) to display a text file, such as a ReadMe.Txt, at the end of an application's setup. NOTE: Microsoft Technical Support does not support the modification of the setup process or any of the setup files. Support is provided for the Package and Deployment Wizard on an "as is" basis only. MORE INFORMATION ================ Follow these steps to modify the Setup Toolkit project to display a text file at the end of Setup: Step By Step ------------ NOTE: This example assumes that NotePad is already installed on the end user's computer and is located in the same folder as Windows. 1. Create a text file named ReadMe.txt. 2. Make a backup copy of the VB98\Wizards\PDWizard\Setup1 folder. 3. Open VB98\Wizards\PDWizard\Setup1\Setup1.vbp. 4. Open the basSetup1 module, and go to the ExitSetup Sub procedure. 5. At the beginning of Sub ExitSetup, add the following statement: Dim vRetVal As Variant 6. Locate the following statement in Sub ExitSetup: If IsWindowsNT4WithoutSP2() Then above this statement, add the following statement: vRetVal = Shell(gstrWinDir & "NotePad.exe " & gstrDestDir & _ "ReadMe.txt", 1) 7. Save the project, and make Setup1.exe. NOTE: Save Setup1.exe in the VB98\Wizards\PDWizard folder. When you save setup1.exe in this folder, you will be bounced back to VB98\Wizards\PDWizard\Setup1 unless you click the original setup1.exe in that folder to overwrite it explicitly. 8. Use the Package and Deployment Wizard to create a Standard Setup Package for a simple project, such as Calc.vbp. In the Included Files screen, add the ReadMe.txt file you created earlier. 9. Run Setup.exe from the file distribution set you created in step 8. If the application's Setup completes successfully, NotePad displays the ReadMe.txt file at the end of Setup. 10. Restore the original Setup Toolkit files before using the Package and Deployment Wizard to distribute applications that do not have a ReadMe file. REFERENCES ========== "Programmer's Guide," "Distributing Your Applications" chapter, "The Setup Toolkit" section Additional query words: kbdss kbDSupport kbVBp kbVBp600 kbAppSetup ====================================================================== Platform : WINDOWS Issue type : kbbug ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 1998.