Peter, did you look into using arrays and customPropertySets?
In (somewhat) similar circumstances, I've found that these can deal
with largish data sets and provide pretty good performance.
I have 18000+ records in one of my data sets, each record with
between 3 and 30 fields. I save the data as a customPropertySet in a
stack file, and archive it regularly as a text file in a simple text
format. Searching and comparing within the data seems quite quick on
the whole, and though I don't have to produce nicely formatted
reports I do have to assemble sub-sets of the data (by searching) in
regular use.
Best,
Mark
On 15 Jan 2008, at 08:11, Peter Alcibiades wrote:
This is my own case: 15-20k records of sales during the fiscal
year. I
accumulate them (with some trepidation) into an external tab
delimited text
file. Then we need to go through and extract sales by product by
month for
some 200+ items. After a prolonged meditation on switch, if and
repeat, and
the prospect of creating a 200 x 12 matrix of fields with each one
individually named and scripted, I broke out "Effective Awk
Programming".
Its like reaching for a plane, after trying to get a smooth finish
with a
chisel. But chisels have their uses too, and are often the right
tool for
the job. Don't try doing a mortise with a plane!
Well, please correct if this is not right.
Peter
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
