Results 1 to 2 of 2
  1. #1
    Star Lounger
    Join Date
    Oct 2003
    Thanked 0 Times in 0 Posts

    Killing Connections (2000)

    I have a FE/BE1/BE2 application - meaning the users read information from two sources but only write back to one source. It came to be this way due to corruption of the entire BE when only one table was being used to write data to. (OUR NETWORK S**KS...constant network drops) I moved that one critical table into its own BE (<200kb) which is a lot quicker to recreate and replace when it becomes corrupted. My question is can I disconnect the users to the BE2 from inside the BE1 database. BE1 is always open on a seperate machine. Info - our users are spread out over an entire state with various network speeds and hardware setups. It has become a constant battle to keep BE2 available.

  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Evergreen, CO, USA
    Thanked 58 Times in 58 Posts

    Re: Killing Connections (2000)

    Your situation is a common problem with Jet-based back-end databases. This recent thread starting with <post#=412959>post 412959</post#> should provide some direction in setting up a mechanism for dropping users. In addition, there are some commercial packages that provide even greater control - I believe FMS has one which you can check out at

Posting Permissions

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