S
Suzan
I have looked somewhat diligently in groups and on the web for a
solution to allowing a user to change calculation results. They want
to be able to override a calculation to a value of their choice. I'm
coming up with a solution similar to tracking changes or doing some
kind of audit trail. The problem is I want to store new manual
overrides of calculations, AND if I have to, store the original
calculation...yuck, who wants to store a calculation. They want to be
able to override calculations up to 18 months in the future. I would
delete overrides in the past. There are basically 6 types of
calculations times 18 months of possible monthly calculations. I
would also like to be able to store comments on the overrides.
Basically, this reminds me of Excel ease of change but with tracking.
In the end, I produce a report that replaces original calculations
with manual overrides by the user. This sounds like some violations
of theory, but hey, that's what they want. I figure I could get
something to work if no one decides to help, but I really want to look
at more options than what I could think of.
My main idea is to store every record's calculations in a table and
then do a type of audit trail on the calculations, putting the
original calcs in a history table and some flag per 6 X 18 fields on
whether that field was overridden. One of the problems I might be
running into (which is why I mention the number of fields and months)
is Access table and query limits. It's that I'm either exceeding the
number of characters a query can have or the number of times I can use
functions or something like that. I am also working with other record
fields that don't need to be tracked.
I already have the report written with calculations NOT overridden.
I hope this makes some kind of sense to someone. I would appreciate
any ideas on the subject, as i have been researching and contemplating
on this long enough....smile...
TIA
Suzan
solution to allowing a user to change calculation results. They want
to be able to override a calculation to a value of their choice. I'm
coming up with a solution similar to tracking changes or doing some
kind of audit trail. The problem is I want to store new manual
overrides of calculations, AND if I have to, store the original
calculation...yuck, who wants to store a calculation. They want to be
able to override calculations up to 18 months in the future. I would
delete overrides in the past. There are basically 6 types of
calculations times 18 months of possible monthly calculations. I
would also like to be able to store comments on the overrides.
Basically, this reminds me of Excel ease of change but with tracking.
In the end, I produce a report that replaces original calculations
with manual overrides by the user. This sounds like some violations
of theory, but hey, that's what they want. I figure I could get
something to work if no one decides to help, but I really want to look
at more options than what I could think of.
My main idea is to store every record's calculations in a table and
then do a type of audit trail on the calculations, putting the
original calcs in a history table and some flag per 6 X 18 fields on
whether that field was overridden. One of the problems I might be
running into (which is why I mention the number of fields and months)
is Access table and query limits. It's that I'm either exceeding the
number of characters a query can have or the number of times I can use
functions or something like that. I am also working with other record
fields that don't need to be tracked.
I already have the report written with calculations NOT overridden.
I hope this makes some kind of sense to someone. I would appreciate
any ideas on the subject, as i have been researching and contemplating
on this long enough....smile...
TIA
Suzan