Microsoft Access hint wanted

[DeepSea]

Hello,

I am new to Access programming and have run across a problem in developing
an application. I know most of you Access wizards out there have better
things to do than hand-hold newbies so I'm not looking for a complete
solution to my problem (although I'm not above taking one if you've got
one...;-) ). I would very much appreciate any hints or references you
could point me to:

The application is a simple interactive event log. I want to be able to
build a data base of event descriptions, along with the date and time they
occured, and a yes or no flag to determine if a follow-up action is
required. The problem I'm having is with the follow-up action required
function. While I can build a query to determine which entries require
follow-up, its not quite what I want.

I want to be able to review all of the entries that require follow-up, and
be presented with a button to close out the entry (without being given the
opportunity to erase or edit the specific entry. This is very important -
within the normal use of the database ie: no hackers or access geniuses,
there can be no editing of an entry once it has been made. The entry must
stand and be closed out with an explantion of the error that would have
required editing)

What I want to do is on pressing the closeout button, I want another entry
to be made with the time and date the button was pressed, a copy of the
original entry text, an 'ENTRY CLOSED' text to be added to the new entry,
and the opportunity to add more comments. Once this new entry is completed,
I want the follow-up required flag on the original entry set to 'no' so it
cannot be closed out again.

Any hints, ideas, or help would be greatly appreciated.

Thanks

 

[DeepSea]

Hello,

I am new to Access programming and have run across a problem in
developing an application. I know most of you Access wizards out
there have better things to do than hand-hold newbies so I'm not
looking for a complete solution to my problem (although I'm not above
taking one if you've got one...;-) ). I would very much
appreciate any hints or references you could point me to:

The application is a simple interactive event log. I want to be able
to build a data base of event descriptions, along with the date and
time they occured, and a yes or no flag to determine if a follow-up
action is required. The problem I'm having is with the follow-up
action required function. While I can build a query to determine
which entries require follow-up, its not quite what I want.

I want to be able to review all of the entries that require
follow-up, and be presented with a button to close out the entry
(without being given the opportunity to erase or edit the specific
entry. This is very important - within the normal use of the database
ie: no hackers or access geniuses, there can be no editing of an
entry once it has been made. The entry must stand and be closed out
with an explantion of the error that would have required editing)

What I want to do is on pressing the closeout button, I want another
entry to be made with the time and date the button was pressed, a
copy of the original entry text, an 'ENTRY CLOSED' text to be added
to the new entry, and the opportunity to add more comments. Once this
new entry is completed, I want the follow-up required flag on the
original entry set to 'no' so it cannot be closed out again.

Any hints, ideas, or help would be greatly appreciated.

Thanks

A real quick reply.

You can create a form and format it not to allow edits.

Take a look at user level security. It may or may not be helpful
to
you.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex
product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can easily
lock you out of your database, which might require the paid services
of a professional to help you get back in.

Practice on some copies to make sure you know what you are doing.

Mr. Meehan:

Thanks for your hint. Its been a rather interesting all-nighter, but I
believe we have the security issues of the application wrapped up. Now I
just have the closing entry feature to take care of and I should be done!

Thanks again for your fast and wll-aimed 'pointer'.