1) I make 1 DB having data for so many users. 2) I make seperate DB for each user
Second approach implies that you'd have to do your own database files (users) management when adding/removing users. It also means you have'd have several database files to keep, so the simplicity of handling just one single file is lost. One advantage what I can see is that when one databse file gets corrupted, other user's data is left intact. I'd opt for the first approach and when it seems that things are getting slower over the time, browse this mailing list for some hints, tips and tricks - that usually helps a lot. :-) In any case you can break the database into multiple files later - it needs some work and changing the schema perhaps, but it's not an overkill. Current limitation is 10 attached database files but AFAIK this can be changed easily in the sources and recompiled if needed. Peter
