[AccessD] forced logout

> -----Original Message-----
> That is surely an idea.  OTOH I want to be able to edit a
> record in a table
> dynamically to allow the FE to see that it is time to log
> out.  One problem
> with "the back end directory" is that it may not even exist,
> or it may be
> several different directories.  If you are using SQL Server,
> where is "the
> back end directory"?  If the FE links to 3 different BEs on different
> machines, where is "the BE directory"?  Of course you can
> then define a
> directory field in a table that the logout code looks in to
> see this file.

Store the location in a table :) (like you say)

> And of course, what about web pages hitting the be?  How do
> you tell them to
> stay out for a time period?  With a table they could
> essentially use the
> same logic the FE uses.  this brings up the issue of time
> zones of course.
> The record needs to include the time zone that the database
> server resides
> in since

Actually time zones is probably a bigger issue than individual pc time.  If you
go for the defined time approach, then the app needs to be aware of the time
difference between it and the server.

How does an ASP determine that it shouldn't contact the DB... To be perfectly
honest I'm not sure.  But then you'd have pretty much the same issue even if it
was table based.  In order for it to determine it is not supposed to be in the
database it would need to already be there.  One of the reasons I was favouring
the file based approach (and I haven't done anything other than think about it
... Not implemented) is that it can be checked prior to trying to get into the
database.  So if maintenance/backup/compact is about to occur someone doesn't
inadvertently log in just when the specific action is about to begin.  And thus
throwing the system out for 24 houus or when ever the next automated backup (for
example) is scheduled.

> And sure, different computers could have different times.  If
> that is an
> issue there are programs that can be run on each workstation
> that sync the
> workstations to the server's clock.

Yes ... But many small businesses don't, and the last thing I personally would
want is that you find out this after they can't get their backup working because
someone was in the db at the time.  Maybe I'm just being overally paranoid
though.

Stuart