I use this method, when I create files during the night with sales data. I'll create a matrix with columns being years and rows being client data, then write it out to an "item".
Now during the day, there are no calculation, read in the item and display the numbers. This isn't really an issue, as the transfile that is created during the night, isn't really meant to be listed, but rather as a storage bin for the program to read from. Once it's in this format, it's easier to create reports as well. Usually, the matrix I create is 5-6 dimensional. I do some converting to work with the dimensions beyond char(252)...but again, they weren't meant for human eyes to view. George >-----Original Message----- >From: Ian McGowan [mailto:[EMAIL PROTECTED] >Sent: Thursday, August 19, 2004 11:38 AM >To: '[EMAIL PROTECTED]' >Subject: RE: [U2] [UV] How to return 'column' from dyn array? > > >> >Accounts -> files -> items -> attributes -> values -> subvalues >> >> in theory this works great! >> >> but...in reality (oh wait, poor choice of word). >> >> Say you have array of sales figures. <x> is the client >> and <,y> is the year, so it's setup like you stated and >> the dictionary will show all the years for each client. >> >> Now..You want to pull an array of all the sales for year<,3> >> That's where a function to grab a column would be nice. > >It's a bad idea to put the client info in an attribute - it >should go in its own item :-) > >The only reason to structure things this way, rather than the >way Barry originally had it, is so access or uniquery or >whatever can deal with the data naturally - in basic there >isn't much of a difference... > >Ian ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
