[AccessD] (Don't) Force Closing the FE

Hi Robert et al

I can confirm this observation. 
It just doesn't work reliably and can cause serious trouble for data consistency unless you somehow - while any important function runs  - inhibits the timer, which may imply coding on a higher level than you are used to - using classes, WithEvents or the like.

/gustav


>>> robert at servicexp.com 14-02-2011 23:09 >>>
The only problem with a "timer" solution is that in heavily used /
complicated databases, running a timer can cause some very unexpected result
with other code procedures. For some reason Access (at least with the
programs I use to build (large complex)) has never liked timers, internal
(form) or external (API).. I think it has something to do with running them
in the same thread Access uses.

I had to use network commands inside of access (ActiveX) to shut a user
down.  Not automatic, but very effective (and more complicated)

WBR
Robert



-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer Gross
Sent: Monday, February 14, 2011 4:53 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Force Closing the FE

Beautiful.  I knew this had to be a problem that others had faced in the
past.  Was always able to get around it because of my network permissions -
with this database I can't do that.

Appreciate all your help - including the idea of an entry/exit log - that's
a great one.

Jennifer