Russell, please don't take this as unfriendly or agressive, and being quite good at peevish myself, I can understand your point of view. But if you don't currently need to deal with thousands of records, then your current level of expertise with using cards will serve you well, and since the card metaphor is inherent in Revoluton, it has more uses than just wrangling data, obviously. When and if you need to deal with bigger data sets, then you'll have the opportunity to develop your expertise for that (whether it be files, custom props, databases, or whatever), and you can be sure that people here will be happy to help and advise. Personally, I find devising schemes for handling data is one of the more enjoyable and interesting aspects of programming, though of course YMMV.

Best,

Mark

On 15 Jan 2008, at 17:56, Russell Martin wrote:

I don't currently have a project where I'm trying to store thousands of
records. To some, maybe that will invalidate my views on the subject.

I just read what Sarah had written below and I was frankly a bit
peeved. I've spent a considerable amount of time learning how to use
stacks as documents and then to find out that even at a paltry 4000
cards, Revolution is in her words 'unworkably slow'.

That just doesn't sit well with me. Most of us have yesterday's
supercomputers sitting on our desks or in our laps. Revolution
shouldn't take a performance hit until you're dealing with millions of
cards. Maybe it's doing something stupid in all of that searching, like
thousands of saves to disk when it should be suspending them until the
search operation is over.

--- Sarah Reichelt <[EMAIL PROTECTED]> wrote:

I would recommend the list field-single card method for Rev. With
Hypercard, marking cards by finding was super fast. With Rev this is
not the case. I wrote a small database (about 4000 records) in
Hypercard for some friends, using the one card per record method.
When
they changed to OS X, I tried just importing it into Rev but
searching
for multiple matches was unworkably slow. I converted it all to a
single card plus data field and it was all good again. Plus the data
is easier to back up and restore if I send them a program update.

Cheers,
Sarah
_______________________________________________
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




______________________________________________________________________ ______________
Never miss a thing.  Make Yahoo your home page.
http://www.yahoo.com/r/hs
_______________________________________________
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

Reply via email to