DOCUMENT:Q190980 07-AUG-1998 [vbwin] TITLE :BUG: Error Using UsesTransaction for MTSTransactionMode PRODUCT :Microsoft Visual Basic for Windows PROD/VER: OPER/SYS:WINDOWS KEYWORDS: ====================================================================== --------------------------------------------------------------------- The information in this article applies to: - Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 6.0 --------------------------------------------------------------------- SYMPTOMS ======== When running an ActiveX DLL application where a procedure has the MTSTransactionMode property set to UsesTransaction, the following error occurs the first time the application is run: You have set the MTSTransactionMode property for one or more Classes in your project(s), but Microsoft Transaction Server is not installed or is the wrong version. This feature requires Windows NT 4.0 with Service Pack 4 or later. MTS functionality will be disabled. Do you want to run anyway? Any subsequent runnings of the application do not generate the error. 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 ------------------ 1. Start Microsoft Visual Basic, creating a new ActiveX DLL project. Class1 is created by default. 2. From the Tools menu, click Add Procedure. 3. In the Name box, type MyProcedure and click OK. 4. In the Properties window, in the MTSTransactionMode list, click UsesTransaction. 5. From the File menu, click Make Project1.dll. 6. From the Project menu, click Project1 Properties, and then click the Component tab. 7. In the Version Compatibility section, click Binary Compatibility, and then click OK. 8. Press the F5 key to run the application. NOTE: Click OK if the Project1 Properties dialog box is displayed with the Debugging tab visible. 9. The error above will be displayed. NOTE: Click Cancel to return to the Visual Basic IDE. 10. Press the F5 key again to run the application. The error message is not displayed a second time and allows for the application to be run. Additional query words: kbdss kbDSupport kbVBp kbVBp600bug kbIDE kbActiveX <<>> 190979 <<>> 1 <<>> DOC: CodeLocation Property Incorrectly Shows Optional Argument <<<LONGTITLE>>> DOC: CodeLocation Property Incorrectly Shows Optional Argument <<<PRODUCT>>> vbwin <<<PRIORITY>>> 3 <<<SECURITY>>> PUBLIC <<<AUTHOR>>> devinb <<<EDITOR>>> pjriker <<<EDITSTATUS>>> Released <<<TECH>>> patcole <<<TECHSTATUS>>> Approved <<<EXPIREDATE>>> Dec 31 1999 12:00AM <<<MESSAGE>>> <<<KEYWORD>>> <<<INTERNALADMIN>>> <<<QUESTION>>> <<<PRODVERNUM>>> <<<COMPONENT>>> <<<TECHNOLOGY>>> <<<LINKS>>> <<<RAIDINFO>>> VEGAS:50387 <<<INCIDENT>>> <<<SWEEPDATE>>> <<<SWEEPSTATUS>>> <<<SOLUTIONTYPE>>> <<<ISSUETYPE>>> <<<PLATFORM>>> WINDOWS <<<HARDWARE>>> <<<BOILERPLATE>>> <<<PRODUCEDVIEW>>> <<<TEXT>>> --------------------------------------------------------------------- The information in this article applies to: - Microsoft Visual Basic Enterprise Edition for Windows, versions 5.0, 6.0 --------------------------------------------------------------------- SUMMARY ======= The Online Help topic for the CodeLocation property of the Microsoft Visual Basic Member object describes an optional parameter of Propkind, which is an enumerated value of vbext_PropertyKind. MORE INFORMATION ================ The CodeLocation property is a read-only property. Assigning a value to the property will generate the following error: Can't assign to read-only property To work around this problem, use the ProcStartLine method of the CodeModule Object. Additional query words: kbdse kbDSupport kbVBp kbVBp600 kbdocerr kbdocfix kbAddIn ====================================================================== 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.