Barry, @Record is primarily designed for interfacing with the query processor. As each record is processed, the id is written to @ID and the record body to @RECORD. You can then use these directly in I Descriptors when accessing specific functionality: E.g.
MyPartKey 1> I Get the first two parts of the key 2> @ID["*",1,2] MyPartAddress 1> I Get last part of an address 2> @RECORD<4,DCOUNT(@RECORD<4>,@VM)> Etc. You can also use this in BASIC code if you want to run a ITYPE() function, along these lines: Read MyDictRec From MyDictFL, MyIDescriptor ... @ID = SomeId Read @Record From MyFL, @ID ... SomeValue = Itype(MyDictRec) Useful for dictionary driven routines e.g. export routines/screen runners etc. Brian > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Barry Brevik > Sent: 14 June 2005 02:17 > To: U2-users (E-mail) > Subject: [U2] [UV] Help with @RECORD > > UV 9.6.1.3 on W2K. > > What's the right way to use @RECORD? I can do- > > OPEN '','A-VALID-FILENAME' THEN NULL > > ...after which @STDFIL is populated with the file handle. > > Then, I can do- > > READ @RECORD FROM 'RECORD-ID' THEN NULL > > ...after which @RECORD is a dynamic array of whatever > corresponds to 'RECORD-ID' in 'A-VALID-FILENAME'. > > But having to directly reference @RECORD seems like it > defeats the purpose of a 'default record'. Is there a RIGHT > way to populate @RECORD? I've tried a number of ideas that > did not work. It would also be cool if you could get > TRANS() to populate @RECORD, but it does not seem to. > > Barry > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
