PRB: Error "Too many client tasks" When Using Jet

 Last reviewed: January 20, 1997
Article ID: Q154869
The information in this article applies to:
  • Professional and Enterprise Editions of Microsoft Visual Basic, 16-bit only, for Windows, version 4.0
  • Standard and Professional Editions of Microsoft Visual Basic, Version 3.0

SUMMARY

When trying to use the database features of Visual Basic, you may receive the error message "Too many client tasks." This occurs when more than 10 applications running on the same machine try to use the Jet database engine.

CAUSE

The Jet database engine versions 1.1, 2.0, and 2.5 can only be used by 10 client applications simultaneously on any one machine.

WORKAROUND

It is not possible to have more than 10 client applications making use of the 16-bit Jet database engine on one machine. If it is essential that a software system have more than 10 executables on the same machine with access to one or more databases, the system could be designed with one "server" exe accessing the database and multiple "client" programs making requests for data from this "server" via an inter-process communication (IPC) mechanism. For example, with Visual Basic version 4.0, this could be achieved using OLE automation.

STATUS

This behavior is by design.

(This is not an issue with Jet 3.0 as used by Visual Basic 4.0 32-bit.)

REFERENCES

Visual Basic Online Help.

KBCategory: kbusage kbole kbprg
KBSubcategory: APrgDataAcc
Additional reference words: 4.00 vb4win vb416 kbuk




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: January 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.