Learning some interesting depth about continuous forms, since I use those frequently and am always looking for good layout ideas. This is always a pain, but thanks to John below - I see more clearly why.
Here's something that may (MAY) be worth a try. If you are storing the color choice in the record, why not have a related table with 2 fields. One for the color choice code number, and the other field storing an image of a simple line, bar, or rectangle in the color you want with that code (whatever shape, size works for your specific form). Then match that color image table to your record source for the form and just display the linked image behind whatever part of each record you want. Those types of images as a GIF are very small, and shouldn't add much to the load time of the form for even a large set of records.
Anyone see why that couldn't work? I don't have anything right now that I would need to try it out on, but would love to know if that's a good work around.
Tim Ritter
Fort Wayne, IN
--- In MS_Access_Professionals@yahoogroups.com, "John Viescas" <john@...> wrote:
>
> Walter-
>
> It works in the report because the report formats each record one at a time. It
> would also work in Single Form view, but it doesn't work in Continuous form view
> because there is really only one copy of each control. You see multiple rows
> because Access "paints" all but the current row, and it honors Conditional
> Formatting as it's doing the "painting." There is no event associated with
> "painting" each row in a form like there is in a report (On Format).
>
> John Viescas, author
> Microsoft Office Access 2010 Inside Out
> Microsoft Office Access 2007 Inside Out
> Building Microsoft Access Applications
> Microsoft Office Access 2003 Inside Out
> SQL Queries for Mere Mortals
> http://www.viescas.com/
> (Paris, France)
>
>
Tidak ada komentar:
Posting Komentar