Search results

  1. J

    Multi-frontend performance?

    I have a split database with a single back-end accessed from two identical copies of a front-end. The back-end and front-ends are all located on a 1Gbps LAN. In this configuration, performance is abysmal because all query execution happens on the front-end systems, and involves shipping all...
  2. J

    Multi-user with network-shared FrontEnd?

    Thanks for all the excellent info. The automatic front-end update might be doable. There will be issues when a combined BE/FE upgrade is pushed, and some clients still have a running FE instance that's no longer compatible with the new BE table structure... I guess checking the "required...
  3. J

    Multi-user with network-shared FrontEnd?

    I understand that's one canonical solution, but it isn't optimal when pushing out FE updates. I want to understand the actual source of the problem to determine if the no-tables solution will work.
  4. J

    Multi-user with network-shared FrontEnd?

    I have to update a split Access DB from single-user to multiple users. All persistent data is in the BE, FE contains the app plus a few tables that would be TEMPORARY if Access supported the concept. The client has access only to the runtime, not the development environment. I see three...
Back
Top Bottom