Stephen Chrzanowski <[email protected]> wrote: > Reading further on, I see that you're looking at end-user. This changes > things a bit. Now you're looking at trying to make things user-proof, > maintain data integrity (Who said 1<>one?), validate data, so on and so > on. You're probably looking at custom code now. > Yes, though the end-user is mostly me so I'm not so fussed about data integrity. It's very simple data, a date, a couple of columns with numbers in and a text column. If it gets confused because I've mis-formatted a date I can simply correct the entry, it doesn't need heavyweight validation.
> But, if you can trust the user(s), I'd STILL say don't reinvent, but just > use a something that is already written. > That's exactly where I'm coming from, I'm desperately trying not to re-invent the wheel but all I can find is complete bicycles! :-) I want a simple application with low overheads (i.e. fast to load *and* with no DBMS extras not needed for data entry) and there really don't seem to be any out there. -- Chris Green _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
