Hiba,

<< Yesterday, I realized that  the "Server Administration Utility DBISAM
Database Server" as shown in the attched screenshot can only afford 5
connections to the dedicated server. In my VB.Net application each user has
to open 2 connections to 2 different databases, that's why I was getting the
protocol error on the 2nd connection. I tried to change the "Max # of
connections" but it seems it is not an editable parameter. So is there a way
to increase the number of connections? since we are around 100 employees so
we need a minimun of 200 connections.Please could you advise if there is a
way to increase the number of connections and how? >>

If you could send your customer information via private email to sales
(sales@elevatesoft.com) along with this question, Sam can help you out with
making sure you have the proper product for unlimited connections.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Hello Tim,

Yesterday I realized that I bought the DBISAM ODBC Driver that has a limited number of 5 connections, while browsing your website for other
alternative, i noticed that the following product DBISAM ODBC Client-Server "DBISAM-ODBC-CS-SRC" has an unlimited number of connections.
So, I sent an email to Sam at the Sales department to check for the possiblility of sending a trial version in order to test it on my side and
accordingly either upgrade my version if possible or get the new one. So, do you think this is the solution to my case?


Thank you.

Hiba

Hiba,

<< Yesterday I realized that I bought the DBISAM ODBC Driver that has a
limited number of 5 connections, while browsing your website for other
alternative, i noticed that the following product DBISAM ODBC Client-Server
"DBISAM-ODBC-CS-SRC" has an unlimited number of connections. So, I sent an
email to Sam at the Sales department to check for the possiblility of
sending a trial version in order to test it on my side and accordingly
either upgrade my version if possible or get the new one. So, do you think
this is the solution to my case? >>

If you were trying to use more than 5 connections, then yes, this was the
issue.  The error must be getting translated by the ODBC.NET data provider
into the "protocol error" error message, which sometimes happens with
certain errors.

--
Tim Young
Elevate Software
www.elevatesoft.com