> Unfortunately I oversimplified my explanation, and the processing > that is required is somewhat more complex.
Perhaps you could give more detail about your data. It seems to me that you should restructure your data so it is "atomic", ie so that each bit of data appears in its own row in a related table, rather than having multiple values in one row. As you're probably aware, this is a fundamental of database design. Otherwise you're unscrambling the egg, which is very error prone and inefficient. Tom BareFeet -- Comparison of SQLite GUI tools: http://www.tandb.com.au/sqlite/compare/?ml _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
