INF: Using DBLIBRARY in a threaded application

 Last reviewed: May 2, 1997
Article ID: Q151607

The information in this article applies to:
  • Microsoft SQL Server, version 6.0

SUMMARY

There are a few tips to be aware of when creating a threaded DBLIBRARY application.

MORE INFORMATION

  1. Make sure you call the dbinit and dbexit functions only once on your application.

  2. Be sure to use per process error and message handling.See dbprocerrhandle and dbprocmsghandle for more details.

    If you use global error and message handlers you may need to synchronize access in your error and message handler routines.

  3. Make sure to call dbsetmaxprocs if you are going to have more than 25 connections open.

  4. Be sure you are compiling/linking with the multi-threaded C/C++ runtime libraries. By default a Visual C/C++ project is linked with the single threaded runtime libraries.

  5. If you use the same LOGINREC to open multiple connections, access to the LOGINREC must be serialized.

Additional query words:
Version : 6.0
Platform : WINDOWS

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.

Last reviewed: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.