<div class="gmail_quote">On Sat, Dec 11, 2010 at 12:07 PM, Bill Allen <span dir="ltr"><<a href="mailto:wallenpb@gmail.com">wallenpb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
David,<br><br>Thanks for the feedback. I should have been more specific on the usage of the data. The data will be some email addresses, names, department, and an indicator if the email address is internal to the business or an external contact. So, one table with these being the fields in each record should suffice. The users will be presented an interface that allows them to select one or more recipients to which a standardized email with a PDF attachment will be sent. All of this is no problem. I was concerned that with more than one user at a time potentially accessing the SQLite db at a time would be a problem, but I see from the SQLite site and from some discussions here on Tutor that this is perfectly fine. The users may add information to the db also, but since such writes will be infrequent this too should be OK. At least, that is the impression that I have gotten from what I have read here and other places. Just wanting to confirm that I have understood this correctly. Also, any other suggestions are welcome.<br>
<br>Thanks,<br><font color="#888888">Bill Allen</font></blockquote><div><br></div><div> I think the larger concern is how the users are accessing the DB. Multiple clients on multiple computers accessing the same db file on an accessible network location? Or something else?</div>
<div><br></div><div>There are plenty of pitfalls to be aware of depending on your use.</div><div><br></div><div>-Wayne</div></div>