Results 1 to 2 of 2
  1. #1
    Join Date
    Jul 2003

    Unanswered: Access front-end - concurrency

    When I build an MS Access front-end for an SQL Server backend, how does it take care of data integrity and concurrency , if it is only a front-end ?
    Is Access smart enough to do the job ?


  2. #2
    Join Date
    Jun 2003
    Provided Answers: 1
    Data integrity should be handled by SQL Server, using constraints, foreign keys, triggers, etc.
    Concurrency should not be an issue as long as you keep the number of simultaneous users low. Access forms operate by downloading an entire recordset and allowing the user to step through them. This is not the optimal implementation for an Enterprise Application. You can get around this by writing your forms to retrieve one record at a time, but then you sacrifice these simple coding that is one of the big benefits of using Access.
    If it's not practically useful, then it's practically useless.

    blindman "sqlblindman"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts