Access Database with SQL Server Backend: Dramatic Slow Down with Multiple Users -

i've migrated access 2007 database sql server 2008 r2 backend, retaining access front end linked tables. performance fine few users.

yesterday application opened multiple users , in afternoon performance went hell. took literally minutes front end open or close, or anything. delay in closing seemed particularly strange, it's done via button on main menu calls application.quit. doesn't else @ all.

i found old ldbview utility seemed work on .laccdb file. showing 11 users logged on plus 15 no longer logged in. didn't show user names, machine names connecting from. machine names 2 virtual hosts don't know if different users or same user being reported multiple times (don't know enough format of .laccdb files able tell).

i took copy of troublesome access front end file (the .accdb file) , ran copy same network location original. ran fine. problem not seem in network, or in sql server database, or access front end corrupt somehow.

eliminating possibilities, problem seems related multiple users using same access front end simultaneously. original access database, before tables migrated sql server, worked fine same number of users. fundamental design of front end seems able support multiple users.

how go tracking down source of contention issues in access front end? me seems there no visibility of going on, apart viewing number of concurrent users in .laccdb file.

by way, since original access database worked fine multiple users, i've been told there no way each user can have own copy of access front end, maintenance nightmare.

the users should not using same front-end copy. should each have own copy can save in personal drive.

you keep own copy of front-end, make modifications it, , redistribute users, replace old version.

sharing single front-end copy definite no-no. nightmare.. , cause of issues having.