MultiUser Winform Application

Sign in to answer this question.

• ZA

  Zeeshan Ahmad16y agoPosted Aug 12, 2010, 4:46 AM

  Thanks Maninder Wadhya for your quick response.
  
  Most of solutions seems to applicable and my comments are as following:
  
  

  (1) Which Data Access method is feasible i.e: DataSet or DataReader.

  (Ans) Dataset is todays need because Now, there are times when only a DataSet will suffice. Often, you'll need to serialize your results, or pass the query results on to the next tier of your application. In these cases, a collection is required, and the DataSet provides a well-supported mechanism for doing this

  Comment:
  

  What will happen when the target table contains million records and the dataset make its local available copy for its use? does it slow down the startup?

  (2) if DataSet what will happen when two users has open dataset of same table and one user delete a record does the deleted record still visible to second user?

  (ans) Implement Distributed transaction while updating/deleting/inserting into  table shared by users

  Comment:
  

  I think distributed transactions required more than one database servers which can synchronize their databases with the help of replication facility provided by SQL Server but this will happen when both the servers runs replication process so the data does not seems to be live across all users till the replication take place and this also seems to be time consuming job.
  

  I think if all the users access the same database which resides on central location / ISP with the help of  DataReader can solve the problem and there will be no issue regarding serialization of data between users.
  
  

  (3) Is there any VB6 DB Connection style locking types like adOpenStatic, adOpenDynamic and Cursor types like adLockOptimistic, adLockPessimistic in ADO.Net 2.0?

  (ans) No.

  Comment:
  

  OK, So how Ado.net handle this situation when more than one users accessing/modifying the same table in same time?
  
  

  (4) What will be connection string to connect remote database from different locations?
  (ans)
             
     
  

  Comment:
  

  This connection string seems to be for the purpose of connecting SQL Server Database Files (.MDF) but actually i need to know the database resides in installed SQL Server at some location.
  

  (5) Any other precautions regarding development of this type of application.

  (ans)  Take care while updating/deleting/inserting into  table shared by users and last but not the lease Implement Distributed transaction

  Comment:
  

  Any other alternative except Distributed transactions.

  
  
• 

  Shankey16y agoPosted Aug 12, 2010, 2:01 AM

  Hi Zeeshan,

  Please mark my answer as accepted if it helped you........!!!!!!!!!

  
  

  (1) Which Data Access method is feasible i.e: DataSet or DataReader.

  (Ans) Dataset is todays need because Now, there are times when only a DataSet will suffice. Often, you'll need to serialize your results, or pass the query results on to the next tier of your application. In these cases, a collection is required, and the DataSet provides a well-supported mechanism for doing this
  
  (2) if DataSet what will happen when two users has open dataset of same table and one user delete a record does the deleted record still visible to second user?

  (ans) Implement Distributed transaction while updating/deleting/inserting into  table shared by users
  
  (3) Is there any VB6 DB Connection style locking types like adOpenStatic, adOpenDynamic and Cursor types like adLockOptimistic, adLockPessimistic in ADO.Net 2.0?

  (ans) No.
  
  (4) What will be connection string to connect remote database from different locations?
  (ans)
             
     
  (5) Any other precautions regarding development of this type of application.

  (ans)  Take care while updating/deleting/inserting into  table shared by users and last but not the lease Implement Distributed transaction