Walter,
My sample db named Form_ContSimulated_ColorsRowWise.zip, uploaded to 4Shared.com demonstrates the approach outlined in my earlier post. It is in Access 2000 file format (Ref: DAO 3.6). Link for downloading the file is given below:
http://www.4shared.com/file/ngHp16DH/Form_ContSimulated_ColorsRowWi.html
Simulated continuous form using unbound controls, displays 12 records at a time. Full coverage of data is provided via suitable navigation buttons. Apart from being able to edit the records, the user can add new records or delete any desired one by clicking appropriate command buttons. All these actions are feasible directly on the simulated form. Current record remains identified by special highlight in first column.
First two columns (locked) display the record number and TrainID. Next two columns, holding TrainCode and ColorValue, are editable. Last column serves as ColorStrip, each row displaying the color represented by ColorValue in the previous column.
There is two way synchronization between ColorValue and ColorStrip. Any value entered in the former gets reflected as corresponding color in the latter. On the other hand, double click on ColorStrip invokes the color dialog box, where the user has unlimited choice and the color finally selected gets displayed in the color strip. Simultaneously, appropriate value gets assigned in ColorValue column.
Note:
The modules for color dialog box have been taken from Access 2002 Desktop Developer's Handbook.
You might like to try it out and confirm whether it is in line with your objectives and whether anything needs further attention.
Best wishes,
A.D. Tejpal
------------
----- Original Message -----
From: nkpberk
To: MS_Access_Professionals@yahoogroups.com
Sent: Thursday, September 29, 2011 04:43
Subject: [MS_AccessPros] Re: Following the color change thread
John;
That may be the best(chickens)way out. I'll have to generate a "Pick a canned color" form with a warning if they choose the same color more than once.
Off to the multi-colored brick road :-)
Walter Griffin
--- In MS_Access_Professionals@yahoogroups.com, "John Viescas" <john@...> wrote:
>
> Walter-
>
> Maybe pick 64 nice unique colors. By using the color picker, you're being a bit
> too user-friendly! Note that the user *could* pick two colors only one color
> number apart in the color picker. The numbers would be unique in the table, but
> would appear virtually the same on the screen. Better to give the users a
> selection of enough different "canned" colors.
>
> 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)
>
>
>
> -----Original Message-----
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of nkpberk
> Sent: Wednesday, September 28, 2011 8:58 PM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: Re: [MS_AccessPros] Following the color change thread
>
> John;
>
> Actually no, I'm using a color picker control and the user can generate
> something like 16000000 colors.
> When I originally set up the "trains" table and form I made a dozen or so "color
> swatch" files and realized some users may need a LOT more than that (certainly
> not 16 million! but 50 or 60 would not be out of the question)
> After that I thought to "automate" the color choices with the color picker and
> now I can't format the form the way I would like, That's what I get for
> thinking!
> I may have to revert to the original plan (with a lot more choices than before)
> if I can't figure out how to generate them on the "fly".
>
> Walter Griffin
>
> --- In MS_Access_Professionals@yahoogroups.com, "John Viescas" <john@> wrote:
> >
> > Walter-
> >
> > I assume you have a set number of colors that can be assigned. If that's the
> > case, build separate GIF or JPG files that are a "blob" of each color, create
> a
> > table with the color code, and a text field that points to the picture file on
> > your hard drive. Join your base table with the color code table on the color
> > code, then use an Image control bound to the text field to display the correct
> > color.
> >
> > 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)
> >
> >
> >
> > -----Original Message-----
> > From: MS_Access_Professionals@yahoogroups.com
> > [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of nkpberk
> > Sent: Wednesday, September 28, 2011 5:21 PM
> > To: MS_Access_Professionals@yahoogroups.com
> > Subject: Re: [MS_AccessPros] Following the color change thread
> >
> > Tim;
> > You know, that might work, build a table with an ID and a image control (OLE
> > doesn't seem to want to work reliably on my system with 2010 on it so I'm
> stuck
> > with an attachment type :-P) Just have to figure out how to build the color
> > image file in code and associate it with the "train" record. Or add an
> > attachment directly to the "Train" record and forget the linked table? Might
> get
> > complicated to change the value tho. May be over my head, too, Ain't no pro at
> > this!
> >
> > Tim, your close, I'm in Pleasant Lake
> >
> > Walter Griffin
> >
> > --- In MS_Access_Professionals@yahoogroups.com, "juiceplustim" <tritter@>
> > wrote:
> > >
> > > 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)
[Non-text portions of this message have been removed]
Tidak ada komentar:
Posting Komentar