[AccessD] shutting down

>As for queries and tables: an application that allows users to view queries
and tables directly does not need an idle time detection process, it need to
the rewritten. :-)

LOL, well...  I can and do make read-only queries and display them to the
client.  Sometimes viewing data in a tabular format is just useful, and you
can set a property for a query to be read-only.  The client can use all of
the built-in query functionality like sorting on any column (or set of
columns), filtering for specific values etc.  Sometimes they like that.


John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert
Sent: Monday, December 17, 2007 4:09 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] shutting down

<snip>

Not saying my method (which, by the way, I have never used, because I don't
create Access Front End's very often) is some stellar approach. But it is
light weight, and much truer towards detecting inactivity. (keep in mind,
Access has reports, queries and tables, the active form isn't going to
detect that)

Drew

</snip>

Now that's an interesting point: reports not showing up in Screen.Active*,
but if someone is viewing a report on screen for so long that the inactivity
detection process kicks in I would argue that they probably are not doing
anything useful anyway.

As for queries and tables: an application that allows users to view queries
and tables directly does not need an idle time detection process, it need to
the rewritten. :-)

Lambert


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com