Brian Gubb
|
| Posted: 11/14/2002, 6:46 AM |
|
This is a multi-part message in MIME format.
------=_NextPart_000_0008_01C28C59.9F10EDE0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Is it possible to change the colours of any updated changes to existing =
data? So that people can see changes with a quick glance.
Brian Gubb
------=_NextPart_000_0008_01C28C59.9F10EDE0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Is it possible to change the colours of any updated =
changes to=20
existing data? So that people can see changes with a quick =
glance.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Brian Gubb</FONT></DIV></BODY></HTML>
------=_NextPart_000_0008_01C28C59.9F10EDE0--
|
|
|
 |
Sixto Luis Santos
|
| Posted: 11/14/2002, 11:26 PM |
|
Hello Brian,
That's a rather interesting proposition. Unfortunately I don't have a simple
solution right now. But maybe we can develop this thread further and find a
solution together.
The first though that crossed my mind was to include control values inside
the form, by means of hidden variables, containing the original data for
each field. Then, before the update, we could compare those control values
to detect changes and in some way alter the display to change the color for
the altered data. Then I realized that CCS generated code do not display
data immediately after processing, but rather refreshes (with redirect) the
page right after committing the update (or whatever) to the database. The
changes detected would be lost after refreshing unless we persisted that
information within a session var. The other way to transmit that information
could be by modifying the target of the redirection and adding some
querystring variables in there. Maybe a variable with the key of the changed
record, and another variable with a comma-delimited list of the changed
fields.
Another approach, and this may be overkill for some applications but ideal
for others, is to add a new DB table to maintain an audit trail. The table
could have the same schema as the original table, but with some new fields
like a new record id, a modification date field, an action field (to reflect
insert, delete or update operation) and a "modified by" field. First, one
must populate the table with the original data. Then, each time the data
changes in some way by inserting, deleting, or updating, a new record is
added to the audit trail. To highlight latest changes in the grid, first
select the latest entry in the audit trail and get the id of the record
(that is, the record id in the original table, not the id of the audit trail
record itself). Then do a new select in the audit trail, but this time
select the top 2 entries ordered by modification date (descending of course)
and restricted by the id. (something like SELECT TOP 2 * FROM original_table
WHERE original_id=x ORDER BY mod_date DESC).
There may not be a simple solution to this problem. Then again maybe I'm
overlooking something simpler and just complicating things unnecessarily.
Regards,
Sixto
"Brian Gubb" <b.gubb@clear.net.nz> wrote in message
news:ar0d0d$2f9$1@news.codecharge.com...
>Is it possible to change the colours of any updated changes to existing
data? So that people can see changes with a quick glance.
>
>Brian Gubb
>
|
|
|
|
Brian Gubb
|
| Posted: 11/15/2002, 12:05 AM |
|
I was hoping for any easy answer.  I'm still very new but CCS has been
and is an exciting learning curve.
Brian
"Sixto Luis Santos" <sixto@tecnoapoyo.com> wrote in message
news:ar27jf$bhs$1@news.codecharge.com...
> Hello Brian,
>
>
>
> That's a rather interesting proposition. Unfortunately I don't have a
simple
> solution right now. But maybe we can develop this thread further and find
a
> solution together.
>
>
>
> The first though that crossed my mind was to include control values inside
> the form, by means of hidden variables, containing the original data for
> each field. Then, before the update, we could compare those control values
> to detect changes and in some way alter the display to change the color
for
> the altered data. Then I realized that CCS generated code do not display
> data immediately after processing, but rather refreshes (with redirect)
the
> page right after committing the update (or whatever) to the database. The
> changes detected would be lost after refreshing unless we persisted that
> information within a session var. The other way to transmit that
information
> could be by modifying the target of the redirection and adding some
> querystring variables in there. Maybe a variable with the key of the
changed
> record, and another variable with a comma-delimited list of the changed
> fields.
>
>
>
> Another approach, and this may be overkill for some applications but ideal
> for others, is to add a new DB table to maintain an audit trail. The table
> could have the same schema as the original table, but with some new fields
> like a new record id, a modification date field, an action field (to
reflect
> insert, delete or update operation) and a "modified by" field. First, one
> must populate the table with the original data. Then, each time the data
> changes in some way by inserting, deleting, or updating, a new record is
> added to the audit trail. To highlight latest changes in the grid, first
> select the latest entry in the audit trail and get the id of the record
> (that is, the record id in the original table, not the id of the audit
trail
> record itself). Then do a new select in the audit trail, but this time
> select the top 2 entries ordered by modification date (descending of
course)
> and restricted by the id. (something like SELECT TOP 2 * FROM
original_table
> WHERE original_id=x ORDER BY mod_date DESC).
>
>
>
> There may not be a simple solution to this problem. Then again maybe I'm
> overlooking something simpler and just complicating things unnecessarily.
>
>
>
> Regards,
>
>
>
> Sixto
>
>
>
>
>
>
> "Brian Gubb" <b.gubb@clear.net.nz> wrote in message
>news:ar0d0d$2f9$1@news.codecharge.com...
> >Is it possible to change the colours of any updated changes to existing
> data? So that people can see changes with a quick glance.
> >
> >Brian Gubb
> >
>
>
|
|
|
|
|
