This is the way we always do it. For associations, you might be better off creating a separate set of subroutines that add and delete to rows of associated values. Its just more controlled and you dont end of with uneven columns of data. The system Im working was not designed this way and I was finding tables of data within records that were uneven. We still have a little of that left and I plan to knock that out when we can. Anthony
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Johnson Sent: Thursday, January 05, 2006 12:22 AM To: u2-users@listserver.u2ug.org Subject: [U2] DCOUNT I'm finding that I'm doing a lot of programming for the processing through multi-valued attributes. I'm wondering if the method I'm using is the best way to determine the last element. LAST=DCOUNT(REC<15>,@VM) FOR I=1 TO LAST (process something) NEXT I There was a REMOVE thread a few months ago and I use that when I expect that the number of elements could test the patience of the EXTRACTs. REMOVE doesn't give you the MV counter for the associated fields by itself. You have to manage separately and hope to keep in sync. That's more code. I know that in VB certain object array variables (a list box for example) has a property for the number of elements. Is there anything in MV that I'm not aware of for determining the last multi-value that's easier to type than the DCOUNT expression. I'm looking at reducing my keystrokes. Thanks in advance. Mark Johnson ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.14/222 - Release Date: 1/5/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.14/222 - Release Date: 1/5/2006 ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
