On Thu, Jun 30, 2011 at 9:27 AM, Alexandros Nipirakis wrote: > I would also say if you are doing something intensive, you may want to > offload it to a separate thread. I have found that data processing > that locks the GUI (IE, on the app thread) causes users to basically > go nuts and start clicking things incessently. Create a thread for > data processing and use a delegate to communicate to the GUI. If you > use Web Services, then do asynchronous rather than synchronous calls. > > Another thing I would suggest (this is coming from being burnt a > couple thousand times on this) make sure you separate your Data Access > Layer from your GUI. It is even a good idea (again, IMHO) to create a > separate DLL for all your data access. This is particularly good if > you believe that there is ever a chance that you will switch database > engines. Of course, if you use a webservice, it basically forces you > into doing this anyways. Be careful about how much business logic you > embed in your GUI. This is also an area where you might want to put > the code in a separate DLL. > Very good advice. Thanks. I've been trying to do that. The threads and the separate database access layer. --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .