>1. in normal scenario how many connections could be handled by ADO using sql server or to be more specific how many requests can be handled by one single VB connection.

How will one single VB connection will handle many request? Have you build a data layer? If you have build an application and that each instance of the application will open its connection to the database, each connection will be able to handle evertyhing the application needs.


>2. i was just wondring how to handle the locking mechanism using ADO and sql server when my application is being used by over 100 user symaltaneously ? can u plz brief the best practise !!

I always prefer not to use binding (except for read-only grids and reports). Always open recordset as static read-only and use the SQL INSERT, UPDATE and DELETE commands to modify data into the database. Locking is better handled this way than from using the corresponding ADO or DAO methods.