that's what EV is for (unless you use another editor for data than AE) ;-)
On 10/12/2010 18:06, [email protected] wrote: > In a message dated 12/10/2010 6:56:38 AM Pacific Standard Time, > [email protected] writes: > > >> That is why I was thinking a real name-value store might be in order. As >> MV >> professionals, not every solution has to be a Pick solution. >> >> On Fri, Dec 10, 2010 at 4:10 AM, Symeon Breen <[email protected]> wrote: >> >>> Isnt this just a name value pair construct ? i do this a lot and just >> have >>> 2 mv attributes 1 = name, 2 = value >>> >>> >>> >>> If you want mv data in the values then you can always LOWER it. > Not sure why you would lower it. > > You could have all the tags in attribute one and all the values in > attribute 2, as multi-values. Of course if the user decides to create 800 > tags, > that can get pretty darn ugly to look at in the EDitor. > > And it's true that not every solution has to be a Pick solution, but if you > have to reference it many times, from within the Pick environment, why make > it external? > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
