>I have a situation that I have been strugling with for about two months now. I have an Application Center which is running several VFP and VB Com components. These components are accessed by a web server and other apps via SOAP for the front end. On the back end for data we access SQL Server and FOX tables. My fox tables are on a WARP server which is connected to several client server apps and a telecommunications switch. The tables are fox 2.6 native.
> I believe the problem that I am having is with NetBEUI. About once a day give or take at different times. Warp will not let anyone connect to the server stating that connections are full. When I bounce my Application Center everything comes back to normal and people with client server apps and app center can connect with no problems. Therfor I asume that App Center is locking connection objects to Warp.
> Here is where it gets tricky. When I look at perfmon and put a sniffer at NetBeui it stats that we only have 7 open connections when we are having the problem.
> In my VFP Components I have put a close all statement at the end of every procedure and in my error captures.
> My Fox tables are huge. Catch this. My main table has 15 millon records (it was 25 millon but we shrunk it last week) and the other ten have about 2 millon each. So FOX OLE is still out of the question.
> I told you this was a good error. Please send me your thoughts.

I don't know anything about Warp, but is it possible it's licensed on a connection basis? You might have only 7 connections yourself but the other C/S apps and/or telco switch app(s) may count as connections as well.

Do you need to use NetBEUI? Could you use TCP/IP instead?