> I have a database (access 2003) divided in back and front end. The
> Back end resides in a server and the front end in each user's
> machine. The users access the database by opening the front end,
> without the need of any password or user ID. Occasionally, some user
> live his office for the day living his computer and the database on
> with an active connection to the back end, therefore, when I try to
> work on the back end exclusively I can't because of the active
> connection with the other computer left on. So, how can I
> force/kill/end that active connections from the back end?

"Joan Wild" wrote:

> Look for KickEmOff2K at http://www.datastrat.com/Download2.html
>
> --
> Joan Wild
> Microsoft Access MVP
>
> Silvio wrote:
> > I have a database (access 2003) divided in back and front end. The
> > Back end resides in a server and the front end in each user's
> > machine. The users access the database by opening the front end,
> > without the need of any password or user ID. Occasionally, some user
> > live his office for the day living his computer and the database on
> > with an active connection to the back end, therefore, when I try to
> > work on the back end exclusively I can't because of the active
> > connection with the other computer left on. So, how can I
> > force/kill/end that active connections from the back end?
>
>
>

> Joan, that program apper to close only the database having the code
> (in my case the backend). I did some test and the linked users are
> still linked after using kickEmOff from the backend. Am I doing
> something wrong?
>
> "Joan Wild" wrote:
>
>> Look for KickEmOff2K at http://www.datastrat.com/Download2.html
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>> Silvio wrote:
>>> I have a database (access 2003) divided in back and front end. The
>>> Back end resides in a server and the front end in each user's
>>> machine. The users access the database by opening the front end,
>>> without the need of any password or user ID. Occasionally, some user
>>> live his office for the day living his computer and the database on
>>> with an active connection to the back end, therefore, when I try to
>>> work on the back end exclusively I can't because of the active
>>> connection with the other computer left on. So, how can I
>>> force/kill/end that active connections from the back end?

"Joan Wild" wrote:

> I haven't actually used it, but after a quick looksee, you should put the
> module and form in the frontend.  Put the KickEm table in the backend, and
> include a link in the frontend to it.  You can open the form in the frontend
> (hidden) at startup.
>
> Then you can set the flag in the backend, and the frontends will close.
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> Silvio wrote:
> > Joan, that program apper to close only the database having the code
> > (in my case the backend). I did some test and the linked users are
> > still linked after using kickEmOff from the backend. Am I doing
> > something wrong?
> >
> > "Joan Wild" wrote:
> >
> >> Look for KickEmOff2K at http://www.datastrat.com/Download2.html
> >>
> >> --
> >> Joan Wild
> >> Microsoft Access MVP
> >>
> >> Silvio wrote:
> >>> I have a database (access 2003) divided in back and front end. The
> >>> Back end resides in a server and the front end in each user's
> >>> machine. The users access the database by opening the front end,
> >>> without the need of any password or user ID. Occasionally, some user
> >>> live his office for the day living his computer and the database on
> >>> with an active connection to the back end, therefore, when I try to
> >>> work on the back end exclusively I can't because of the active
> >>> connection with the other computer left on. So, how can I
> >>> force/kill/end that active connections from the back end?
>
>
>

> Thank you much it works. But I have one more question if you don't
> mind: How can I open the form in the frontend in hidden mode?
>
> I have tried to add the following code in OnOpen event of the form
> forms!myformname.visible = false but the forms still shows :-(
>
>
> "Joan Wild" wrote:
>
>> I haven't actually used it, but after a quick looksee, you should
>> put the module and form in the frontend.  Put the KickEm table in
>> the backend, and include a link in the frontend to it.  You can open
>> the form in the frontend (hidden) at startup.
>>
>> Then you can set the flag in the backend, and the frontends will
>> close.
>>
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>> Silvio wrote:
>>> Joan, that program apper to close only the database having the code
>>> (in my case the backend). I did some test and the linked users are
>>> still linked after using kickEmOff from the backend. Am I doing
>>> something wrong?
>>>
>>> "Joan Wild" wrote:
>>>
>>>> Look for KickEmOff2K at http://www.datastrat.com/Download2.html
>>>>
>>>> --
>>>> Joan Wild
>>>> Microsoft Access MVP
>>>>
>>>> Silvio wrote:
>>>>> I have a database (access 2003) divided in back and front end. The
>>>>> Back end resides in a server and the front end in each user's
>>>>> machine. The users access the database by opening the front end,
>>>>> without the need of any password or user ID. Occasionally, some
>>>>> user live his office for the day living his computer and the
>>>>> database on with an active connection to the back end, therefore,
>>>>> when I try to work on the back end exclusively I can't because of
>>>>> the active connection with the other computer left on. So, how
>>>>> can I force/kill/end that active connections from the back end?