db open for long periods of time

[GBalcom]

I'm thinking of creating a database that simply looks for records in a query every 15 minutes...when it finds a record that it hasn't acted upon before, it emails said record. I'm pretty confident I can handle the vba for this db.

I will have the db auto open with task scheduler at say 7:30 am, then I will have code to close the db after 5pm. Other than that, it will have a timer and requery every 15 minutes.

Should I expect any issues with having a database open for such a long period of time? Just want to know what I'm up against.

Thanks! I love this forum.

 

[gemma-the-husky]

I have a programme that does a similar thing

An external scheduler collects files and puts them in a certain folder.
My database checks every so often to see if there are any new files in the folder. It works fine.

 

[GBalcom]

Glad to hear it works fine. Thanks for sharing.

 

[GBalcom]

One more thing I hadn't considered....Ocassionally someone works at the computer that this will be on. I'm entertaining figuring out a way to run Access in the "background", so it will not disrupt the user. Ideas welcome

 

[GBalcom]

I think the code in this thread may do it...but I'll have to wait until later to tell:

http://www.access-programmers.co.uk...=217400&highlight=open+access+in+hidden+state

 

[gemma-the-husky]

I actually have a form open that has the timer running.

Users can do other stuff at the same time. The timer just runs at the appropriate time

 

[The_Doc_Man]

As long as the form is minimized AND the user doesn't do something to LOG OUT the session you are on - which has implications regarding security - the timer on the form will still be active and can "do its thing." I am not entirely clear whether a "Switch User" allows that form to continue to run, but it is possible that it would do so. That has implications on publishing procedures for the terminal you would put in conflict this way.

If the site enforces distinct user logins for security purposes, this might not work since you would be allowing someone else to run under your security ID. I can't speak to YOUR site rules, but at the Dept. of Defense, this would be at the "you are fired now, we'll send you your stuff in a box later" level of offense.