Append Q/Form question

Wulf13

Registered User.
Local time
Today, 07:59
Joined
Jul 6, 2004
Messages
85
Hello out there in the world. I am seeking an answer to a problem. Ok, not really an answer but more like looking for a better way to do this if possible.

Scenario is this, I have a table with several fields. When a record is deleted in this table, I have an append query that places three pieces of info from this table to a "30 day history" table. This history table contains these three pieces of information along with date the record was deleted and supervisor who made the notification. Once the appen query is done, a form (filtered to that single record in the historic table) opens and allows the user to add input the date and supervisor information for that record just added.

My question is: Is there a way to do this without the form, or is this the best I'm going to get? I look forward to any suggestions or thoughts on the matter.
 
The append query can use the current date as a data source, look up function Date() or Date$() depending on desired format and field type.

The query can also use the CURRENTUSER() function as a data source. Look up that one, too.

You can also search the forum for articles on getting the user's network name from the environment. Keywords 'network name' or 'environment'
 
Doc Man, thank you for the input. The problem is the date the change is made may not be the date its requested. I know it sounds pretty goofy but the date put it could be either today our yesterday. I'm trying to get the 'client' to let me just use the current date.

In regards to the currentuser() idea, the name that is inputted is the name of supervisor, not the person inputing the data.

If I can get the date requirement changed, I just need to find some way to input the name of the supervisor.
 
I'm no expert, but it seems to me that access cannot automatically input information that it doesn't have. I see no way around having the user input your request date and supervisor via your form (unless you have a table that specifies the duty roster of supervisors and uses the user-supplied date to lookup the supervisor on duty when the request was made).
 
I'm with Craig on this one. If the date isn't today and the supervisor isn't the person making the entry, you need to enter these items. After all, the last time I looked, Access wasn't psychic. So mind-reading is out of the question.

There is a rule about databases that applies here. A DB cannot tell you anything you didn't tell it first.
 
I feel silly

Ok..now I feel silly. After looking at from Craig's POV, it was silly to begin with. Thank you gentlemen for being patient enough to show me the error in my logic. Next time I think it through a little better.

Thank you
 

Users who are viewing this thread

Back
Top Bottom