Scott,

<<  4096 >>

Okay, that's what it should be.  I would suggest that you try to get the log
(EDBConfig.EDBLog in the same directory as the configuration file
EDBConfig.EDBCfg) from their site and email it to me.  There should be at
least a clue in there as to the cause of the issue.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim - Can you email me ( swoods80@gmail.com) a simple remote client and server setup that you use to test with and the code?  I have to think its a simple setting that I have that is
causing the issue.  I have upgraded to 1.06 and the issue still exists.

I re-read the thread from Andrew on the application lock and I think I am seeing the same issue.  After upgrading to 1.06 my round robin app no longer freezes, but when I run
a query, close the app, open the app and re-run the query I get the freeze.  Like Andrew I am running the remote client and server on the same machine.

Scott,

<< I re-read the thread from Andrew on the application lock and I think I am
seeing the same issue.  After upgrading to 1.06 my round robin app no longer
freezes, but when I run a query, close the app, open the app and re-run the
query I get the freeze.  Like Andrew I am running the remote client and
server on the same machine. >>

That issue would not cause a failed connection error message.  It simply
causes a lock error eventually.

--
Tim Young
Elevate Software
www.elevatesoft.com

There were two issues they were seeing, one was the 1100 issue that I beleive was fixed with the update to 1.06.  The other is the 300 error running a
simple query, which I am hoping is the same issue reported in the group.

One last post on this subject and I will wait for the patch  Could the issue that Andrew reported have something to do with Socket connections?  I stepped
into the code last night and where my issue came was waiting for a Socket to release (the wait time is 3 minutes).  My theory is the socket connection is
used up when the client connects and runs the SQL the first time which works.  When the app is closed and restarted, running the same query gets locked
waiting on a socket response from the remote server (in this case running on the same machine).  Does this sound plausable?

Scott,

<< One last post on this subject and I will wait for the patch  Could the
issue that Andrew reported have something to do with Socket connections?  I
stepped into the code last night and where my issue came was waiting for a
Socket to release (the wait time is 3 minutes).  My theory is the socket
connection is used up when the client connects and runs the SQL the first
time which works.  When the app is closed and restarted, running the same
query gets locked
waiting on a socket response from the remote server (in this case running
on the same machine).  Does this sound plausable? >>

If you're getting a #300 error, then it most definitely is a general locking
issue and doesn't have anything to do with the sockets.

--
Tim Young
Elevate Software
www.elevatesoft.com