Re: Last question for awhile...

Not elegant doesn't necessarily mean bad:)

It just seems like a sort of loophole way of solving the problem rather
than some sort of option for a field that says "In form view, use
values from column a, in table view, use the equivalent values in
column b". So the two values would not actually be present in the list
at any given time.

Just semantics I know, but I'm more than a little OCD about anything
that touches data so I always strive for the cleanest way to do
something, even if there's an equally effective shortcut.

Rick Wannall wrote:
You got it. The only really viable alternative is to have a little table
that stores those values and then use a different row source type of
Table/Query. Same thing, more or less.

Curious to know why in your estimate it is "not an elegant solution".

You want to show one value, store another, and you don't want to show the
one you're storing. By definition you're describing two values presented in
a list, one column invisible. How much closer could you get to that
description than a combobox or listbox with one column width set to 0?

.

Relevant Pages

  • Re: Last question for awhile...
    ... define a "lookup field" in a table. ... On first glance, it might appear to be "more elegant," but you are very ... It just seems like a sort of loophole way of solving the problem rather ... that stores those values and then use a different row source type of ...
    (comp.databases.ms-access)
  • Re: Returning Median Value
    ... this is a common misconception about quick sort. ... I did a quick test using the tester app with the pure quicksort (no stack depth limiting) on several distributions. ... Swaps are item swaps, stores are stores to the pivot element. ...
    (microsoft.public.vb.general.discussion)
  • Re: sorter script [was: Frustrated newbie question]
    ... was from the "perldoc -q sort" as a way of ... most 'elegant' of looking algorithms. ... that bogged the database engine down. ... was due to bad implementation on the db engine. ...
    (perl.beginners)
  • Re: ECC logging implementation
    ... of loads and stores, within the aliasing rules, would not be ... This is why I would never rely on an ordinary inline load or store having any sort of implied global visibility: Any operation which does require some sort of synchronization must be encapsulated in an explicit call to a function with the required functionality. ... If an architecture supply sufficiently strong ordering guarantees that those function calls can become inline macros without any special lock/sync operation, that would be nice, but I won't depend on it. ...
    (comp.arch)
  • Re: IBasicAudio::put_volume() not working?
    ... >>> Isn't this a little more elegant? ... >> I was told about some sort of special com pointer the other day but ... >> bah:P i don't normally use hungarian... ... >>> Have you looked at your graph in GraphEdit using the ROT code? ...
    (microsoft.public.win32.programmer.directx.audio)