jwcolby
jwcolby at colbyconsulting.com
Tue Feb 24 18:15:50 CST 2009
Not at all William, my argument is that if you are capable of using collections then tags quickly become a bad idea. Not a "not good" idea, a BAD idea, for all the reasons I have mentioned. YOU would not even consider using a single field in a table to store multiple unrelated things, and yet you don't bat an eye at doing it with a tag. You have to pack it, You gotta load it, you gotta unpack it, you gotta use it. You gotta see what is in there, you have to search for stuff. ICK!!! I have to do the same thing, but I don't use a tag to do so, it simply makes no sense. William, I used tags, more than anyone in AccessD, I would bet a paycheck on that. I wrote some ungodly code to do that packing, unpacking using etc. I wrote entire systems to make it easy to see the stuff I was packing in there. It worked. It was ugly. I would NEVER do it again. But I have the ability to use other more powerful tools. If you don't have that ability, I would HIGHLY suggest that you spend the time to learn more powerful tools rather than take the "easy way" because while it may be easy now, it will get ugly REALLY quick!!! Just an opinion from someone who has been there. And yes, it is just my opinion. John W. Colby www.ColbyConsulting.com William Hindman wrote: > ...sigh ...c'mon jc ...you're whole argument has become pros use classes, > nubees use tags ...which is not only insulting but simply not true ...I can > take you on a guided tour of access pro sites offering tag solutions/code. > > ...now as it happens, I've never used tags before ...just seemed like there > was always an easier way ...but then I've never written classes in access > either ...but my apps still work and the clients keep calling ...which, > insults aside, is the bottom line for all of us. > > William