mbarkley9872
Technical User
I’ve spent months trying to figure out how to accomplish what seemed like the easiest of objectives, but every time I think I’ve got it figured out I seem to hit another major stumbling block. So, before I throw it all away and forever deem myself as a failure, I’m hoping someone here can take a look at my situation and perhaps get me started on the right path…
Every day we incur numerous service problems “Events”. Each morning we have a global conference call where events which occurred within the previous 24 hours are discussed. Prior to the call, an analyst has to review these events and provide a report, ‘The Morning Report’, to management which contains numerous details including historical events, projects in place addressing that particular problem, a category type, scheduled routine maintenance items that are relevant, etc. The most relevant piece for my question(s) is the historical events – we need to include all like-events which have occurred within the last 180 days.
What’s key is that the reported data is only a snapshot of the situation at that time, and that we need to maintain a history of what was reported. (Events will occur in the 24-hour window, but the records may not be entered until after the cut-off time for the conference call and, those that were added in time may change or even be deleted. In fact, event data is constantly being updated until the 10th of each month, at which time all data for the previous calendar month is “locked”.)
The Morning Report process begins by the analyst downloading a txt file ‘ExDwn’ of all events within a selected date range from a company system (the only access to the data is via the download). tblExDwn in a access database is linked to the download file.
Currently, the Morning Report is created “old school” by users downloading 180 days of events into ExDwn.txt, running a macro in Word which creates headers of event data from last 24 hours, and then running another macro to import the download into Excel. Then they scroll through the rows in Excel and copy and paste the related/relevant events into the Word document.
What I’m shooting for is this: The analyst runs the download, import/update access, opens a form which, amoung a million other things, the new events with a subform containing 180 days history. The user selects the related/relevant records and appends them to a table containing the history events for each current event.
Here’s my thinking so far along with my questions…
tblMR_Ex - The new events (from last 24 hours) will be appended to tblMR_Ex. This table will have additional fields which capture analysis results such as category type, last service date, open projects on that system, etc. See Question 1, below.
tblMR_ExHist – For each event in tblMR_Ex, 180 days of event history. Here’s where it starts getting mind-numbing… See Question 2, below.
frmMR_Ex shows the events for last 24 hours.
sfmMR_ExHist shows 180 days of history for those events using fields [Tail] and [ATA] to link. The analyst selects only those records which are truly related/relevant and appends those records to tblMR_ExHist. See Question 3, below.
tblMR_Ex 1-to-many relationship with tblMR_ExHist.
Q1: During the hour or so the report is being compiled, the analyst needs to be able to re-run the download and update the records which are to be reported on that day. So, if an event is deleted or revised then a status field in tblMR_Ex, would reflect if record has been added, deleted, or updated, and subsequently update the fields which were revised. I found some great code for comparing and updating tables at Roger’s Access Library which could work except for a couple issues – 1) tblMR_Ex not only has the fields in ExDwn but also has about 15 addition fields which capture analysis results. 2) I first need to create a table in Access before comparing and updating. So, how best to handle getting the new event data in and being able to update it several times during the process of creating that morning’s report?
Q2: What would be the record source for tblMR_ExHist – ExDwn? A temp table containing 180 days of history? Or, tblExHist detailed below?
Q3: How can I enable users to select only relevant records in sfmMR_ExHist and append them with the MR_ExID from frmMR_Ex to tblMR_ExHist?
Additional table and key field information:
Key fields available from ExDwn .txt - Tail, Date, Time, ATA (code for effected system), Gtwy (location of problem occurrence), Description, and ActionTaken.
tblExDwn - linked to downloaded txt file which contains last 180 days of Events. No unique field, but 3 fields (ExDate, ExTime, Tail) can be indexed to identify unique records. Currently, during the updating of tblExHist, these fields are concatenated into at text field [ExID] and is set as Primary Key
tblExHist - stores all event history and is updated periodically by running the ExDwn download, and then running delete and append queries to overwrite records within the same date range as was used for the download. This is essentially our main table that we use for multiple purposes, currently none of which is generating the Morning Report. It’s used for trending, analysis, monthly reporting, year over year reporting, etc.
tblMR_Ex - main data table to store events reported on Morning Report. Has all fields from tblExDwn plus a dozen or more additional fields which captures research and analysis findings.
tblMR_ExHist - For each event, the user reviews 180 days of event history and determines if any are prior occurrences or are related to the event under review. If so, this table captures those historical events.
Please post if any of this is confusing or lacking necessary details. And many thanks for any and all assistance!!
Mike
Every day we incur numerous service problems “Events”. Each morning we have a global conference call where events which occurred within the previous 24 hours are discussed. Prior to the call, an analyst has to review these events and provide a report, ‘The Morning Report’, to management which contains numerous details including historical events, projects in place addressing that particular problem, a category type, scheduled routine maintenance items that are relevant, etc. The most relevant piece for my question(s) is the historical events – we need to include all like-events which have occurred within the last 180 days.
What’s key is that the reported data is only a snapshot of the situation at that time, and that we need to maintain a history of what was reported. (Events will occur in the 24-hour window, but the records may not be entered until after the cut-off time for the conference call and, those that were added in time may change or even be deleted. In fact, event data is constantly being updated until the 10th of each month, at which time all data for the previous calendar month is “locked”.)
The Morning Report process begins by the analyst downloading a txt file ‘ExDwn’ of all events within a selected date range from a company system (the only access to the data is via the download). tblExDwn in a access database is linked to the download file.
Currently, the Morning Report is created “old school” by users downloading 180 days of events into ExDwn.txt, running a macro in Word which creates headers of event data from last 24 hours, and then running another macro to import the download into Excel. Then they scroll through the rows in Excel and copy and paste the related/relevant events into the Word document.
What I’m shooting for is this: The analyst runs the download, import/update access, opens a form which, amoung a million other things, the new events with a subform containing 180 days history. The user selects the related/relevant records and appends them to a table containing the history events for each current event.
Here’s my thinking so far along with my questions…
tblMR_Ex - The new events (from last 24 hours) will be appended to tblMR_Ex. This table will have additional fields which capture analysis results such as category type, last service date, open projects on that system, etc. See Question 1, below.
tblMR_ExHist – For each event in tblMR_Ex, 180 days of event history. Here’s where it starts getting mind-numbing… See Question 2, below.
frmMR_Ex shows the events for last 24 hours.
sfmMR_ExHist shows 180 days of history for those events using fields [Tail] and [ATA] to link. The analyst selects only those records which are truly related/relevant and appends those records to tblMR_ExHist. See Question 3, below.
tblMR_Ex 1-to-many relationship with tblMR_ExHist.
Q1: During the hour or so the report is being compiled, the analyst needs to be able to re-run the download and update the records which are to be reported on that day. So, if an event is deleted or revised then a status field in tblMR_Ex, would reflect if record has been added, deleted, or updated, and subsequently update the fields which were revised. I found some great code for comparing and updating tables at Roger’s Access Library which could work except for a couple issues – 1) tblMR_Ex not only has the fields in ExDwn but also has about 15 addition fields which capture analysis results. 2) I first need to create a table in Access before comparing and updating. So, how best to handle getting the new event data in and being able to update it several times during the process of creating that morning’s report?
Q2: What would be the record source for tblMR_ExHist – ExDwn? A temp table containing 180 days of history? Or, tblExHist detailed below?
Q3: How can I enable users to select only relevant records in sfmMR_ExHist and append them with the MR_ExID from frmMR_Ex to tblMR_ExHist?
Additional table and key field information:
Key fields available from ExDwn .txt - Tail, Date, Time, ATA (code for effected system), Gtwy (location of problem occurrence), Description, and ActionTaken.
tblExDwn - linked to downloaded txt file which contains last 180 days of Events. No unique field, but 3 fields (ExDate, ExTime, Tail) can be indexed to identify unique records. Currently, during the updating of tblExHist, these fields are concatenated into at text field [ExID] and is set as Primary Key
tblExHist - stores all event history and is updated periodically by running the ExDwn download, and then running delete and append queries to overwrite records within the same date range as was used for the download. This is essentially our main table that we use for multiple purposes, currently none of which is generating the Morning Report. It’s used for trending, analysis, monthly reporting, year over year reporting, etc.
tblMR_Ex - main data table to store events reported on Morning Report. Has all fields from tblExDwn plus a dozen or more additional fields which captures research and analysis findings.
tblMR_ExHist - For each event, the user reviews 180 days of event history and determines if any are prior occurrences or are related to the event under review. If so, this table captures those historical events.
Please post if any of this is confusing or lacking necessary details. And many thanks for any and all assistance!!
Mike