Keeping in mind, multivalue works for UV/PICK because the OS/database structure was designed around that concept.
Now, trying to get a single field application that has been designed around a single field of data to now try to "deal" with multivalue would be quite harmful, to the application. It's kinda of like trying to implement GUI into UV code without using 3rd party methods, it would, not doubt, be very difficult and cause many a program to stop working correctly I'm sure if the Access/Oracle/MySQL were redesigned with multi-value in mind, the opinoin would be a little higher of it's usefulness (to Access/SQL world) George > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Ray Wurlod > Sent: Wednesday, July 19, 2006 9:20 PM > To: u2-users@listserver.u2ug.org > Subject: Re: [U2] RE: Multivalued datatypes > considered > harmful | The Register Register > > > I responded in a positive tone to the author with examples of > how his assertions are undermined by simple understanding of > the processes involved - primarily separating selection from > display in one's mindset. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
