In my own projects, I'd probably go for using custom properties, but
if you're not considering more than a few hundred records, a card per
record approach shouldn't be problematical. I believe such an
approach can get rather slow, but not until you're dealing with
several thousand records.
Best,
Mark
On 20 May 2006, at 07:57, Ian McKnight wrote:
Hi
I'm developing an application for personal use that needs database
features and would appreciate some advice on the best storage method
to employ for scalability.
At present I have 60 records each with 18 text fields. The fields are
name, address, Date of Birth etc., class in school and attendance.
However I can envisage the number of records doubling quite quickly
and I would see an upper limit of perhaps 500 records as being a very
realistic maximum.
The records are used to produce printed lists (rolls) on a monthly
basis and summary sheets (attendance) annually. The attendance is
updated monthly as well.
I realise that I can put one record for each card or read the data
from a text file or custom property into 1 card or even use SQL at
some stage. My preference would be to have one record per card but is
this the best option for my application? At present I'm using Rev
Media 2.7.
Thanks for your help
Ian McKnight
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
