[AccessD] Continuous form question

Are you working with a version that allows conditional formatting?  If
so that's probably the most straightforward approach.  Everything else
depends on a lot of code.  I've done what you're doing and it isn't
pretty by any means, but you might be able to give it a facelift by
binding the controls to a class as JC has been teaching, give the
controls a DataChanged property, and use that to control the rest.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Steele
Sent: Thursday, February 19, 2009 2:10 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Continuous form question

I'll send you his phone number if you would like to talk to him on my
behalf
:)

The reason we would like to highlight changed cells is precisely so that
this large screen can easily be scanned for changes.  It's a shipping
scheduling screen - all the rows need to be showing because they depend
on each other.

What I've come up with is a second, change tracking, field in the table
which overlays the actual field in the form; when the actual field is
changed I put some characters in the overlay field which cause the cell
to appear with a red bar across the bottom.  It works, but as I said,
it's ugly to code.

Doug Steele

On Thu, Feb 19, 2009 at 1:47 PM, Charlotte Foust
<cfoust at infostatsystems.com
> wrote:

> This is why reports were invented.  I'm afraid if a client had to see 
> 600 rows of 20 columns and actually read it, I'd think seriously about

> finding a new client.
>
> Charlotte Foust
>
> -----Original Message-----
> Subject: [AccessD] Continuous form question
>
> Hello:
>
> I have a large continuous form which will normally be showing about 
> 600 rows of around 20 columns.  After editing it, my client would like

> some kind of visual clue as to which individual cells in the form have

> been updated, so that someone else can quickly look it over and see 
> where changes have been made. Does anyone have a good way of doing 
> this?  So far, any way I've thought about has been really ugly to
implement.
>
> <http://www.databaseadvisors.com>
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com