I have an upcoming clinical project where I anticipate having a tblNotes
with fields for Author and Notes (memo) joined to tblPatients.

I anticipate using user level security with each author (health care
worker) being assigned to an appropriate group.

Once a note is written about a patient and saved, it must not be editable
by anyone. I am not sure of the best way to accomplish this. Complicating
the issue is the fact that an author may be called away from the computer
in the middle of creating a note and would not appreciate losing all that
work if the session times out.

My thoughts are running towards using an intermediate table from which
the finished note is moved to tblPatients via an authorizing process.
Somehow I get the feeling that there is a better way.

Is there? Are there any other gotchas to be aware of?

TIA
--
Len
______________________________________________________
remove nothing for valid email address.

On Sat, 12 Sep 2009 12:06:14 +1000, "Len B"
<(E-Mail Removed)> wrote:

"the session times out"? Are you speaking of a Microsoft Access
application, the subject of this news group?

-Tom.
Microsoft Access MVP


>I have an upcoming clinical project where I anticipate having a tblNotes
>with fields for Author and Notes (memo) joined to tblPatients.
>
>I anticipate using user level security with each author (health care
>worker) being assigned to an appropriate group.
>
>Once a note is written about a patient and saved, it must not be editable
>by anyone. I am not sure of the best way to accomplish this. Complicating
>the issue is the fact that an author may be called away from the computer
>in the middle of creating a note and would not appreciate losing all that
>work if the session times out.
>
>My thoughts are running towards using an intermediate table from which
>the finished note is moved to tblPatients via an authorizing process.
>Somehow I get the feeling that there is a better way.
>
>Is there? Are there any other gotchas to be aware of?
>
>TIA

Yes Tom,
MS Access 2k3 will be running on Terminal Servers. Front end & back-end
MDBs will be on DFS servers (all different boxes). It isn't uncommon for
users to wander off and leave the TS session running so a 1hr timeout
exists to rescue TS server resources. Sorry I didn't say but I didn't
want to over-complicate with what I saw as not relevant.

--
Len
______________________________________________________
remove nothing for valid email address.
"Tom van Stiphout" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
| On Sat, 12 Sep 2009 12:06:14 +1000, "Len B"
| <(E-Mail Removed)> wrote:
|
| "the session times out"? Are you speaking of a Microsoft Access
| application, the subject of this news group?
|
| -Tom.
| Microsoft Access MVP
|
|
| >I have an upcoming clinical project where I anticipate having a tblNotes
| >with fields for Author and Notes (memo) joined to tblPatients.
| >
| >I anticipate using user level security with each author (health care
| >worker) being assigned to an appropriate group.
| >
| >Once a note is written about a patient and saved, it must not be
editable
| >by anyone. I am not sure of the best way to accomplish this.
Complicating
| >the issue is the fact that an author may be called away from the
computer
| >in the middle of creating a note and would not appreciate losing all
that
| >work if the session times out.
| >
| >My thoughts are running towards using an intermediate table from which
| >the finished note is moved to tblPatients via an authorizing process.
| >Somehow I get the feeling that there is a better way.
| >
| >Is there? Are there any other gotchas to be aware of?
| >
| >TIA

On Sat, 12 Sep 2009 18:20:04 +1000, "Len B"
<(E-Mail Removed)> wrote:

If you are concerned about timeout: there is a way to auto-logout
people who have been idle for a long time. The procedure is not 100%
fool-proof, but perhaps good enough for your needs. Check this out:
http://www.accessmvp.com/JConrad/acc...e/kickoff.html

-Tom.
Microsoft Access MVP


>Yes Tom,
>MS Access 2k3 will be running on Terminal Servers. Front end & back-end
>MDBs will be on DFS servers (all different boxes). It isn't uncommon for
>users to wander off and leave the TS session running so a 1hr timeout
>exists to rescue TS server resources. Sorry I didn't say but I didn't
>want to over-complicate with what I saw as not relevant.

Tom van Stiphout <(E-Mail Removed)> wrote:

>If you are concerned about timeout: there is a way to auto-logout
>people who have been idle for a long time. The procedure is not 100%
>fool-proof, but perhaps good enough for your needs. Check this out:
>http://www.accessmvp.com/JConrad/acc...e/kickoff.html

Although I'd make very sure that the kick off logic saves the record
before exiting.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/

On Sun, 13 Sep 2009 23:32:00 -0600, "Tony Toews [MVP]"
<(E-Mail Removed)> wrote:

Agreed, that's one of the concerns. Another one is a modal dialog or
MsgBox that cannot be closed by the KB article code.

-Tom.
Microsoft Access MVP


>Tom van Stiphout <(E-Mail Removed)> wrote:
>
>>If you are concerned about timeout: there is a way to auto-logout
>>people who have been idle for a long time. The procedure is not 100%
>>fool-proof, but perhaps good enough for your needs. Check this out:
>>http://www.accessmvp.com/JConrad/acc...e/kickoff.html
>
>Although I'd make very sure that the kick off logic saves the record
>before exiting.
>
>Tony