[dba-VB] threading

 > Why not have several (FE) applications if they are so independent? - all developed within one VS 
solution but as separate (WinForms) projects sharing the same (set of) class library(-ies)?

It seems like that may be what I am doing?  I have a single solution.  Inside of that solution's 
physical directory I have multiple projects, each in its own directory.  As I expand the solution I 
do an add / new project from the main solution / project.  Doing that takes care of creating a 
directory structure for each new project, but causes it to be created under the main solution directory.

Each project does not depend in any way on any other project, though I do have some shared 
libraries.  Each child project is referenced by the main project, but the child projects do not 
reference other child projects.

Now whether each of these independent projects ends up as individual applications I don't have a 
clue.  I was just tying them together with a single form / menu so that I have one central 
application to go to to find everything.

John W. Colby
www.ColbyConsulting.com


Shamil Salakhetdinov wrote:
> Hi John --
> 
> Why not have several (FE) applications if they are so independent? - all
> developed within one VS solution but as separate (WinForms) projects sharing
> the same (set of) class library(-ies)?
> 
> --
> Shamil
> 
> -----Original Message-----
> From: dba-vb-bounces at databaseadvisors.com
> [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Wednesday, December 09, 2009 10:14 PM
> To: VBA
> Subject: [dba-VB] threading
> 
> As mentioned in previous emails, I am developing an application to manage
> all of the tasks for the 
> DBFH.  This includes Backing up databases, creating orders, transferring
> data between an external 
> app etc.  I am trying to determine how to thread this app such that if I
> start a process exporting 
> data to Accuzip, I could have another process importing data from Accuzip,
> and also be working on an 
> order.
> 
> As things currently stand, each of these tasks is a project and each project
> has its own forms and 
> classes, and anything else necessary for that task.  I really do want to be
> able to do multiple 
> things like this at the same time.  Exporting data to Accuzip can take
> overnight, and actually 
> consists of an export and a matching import process.  It makes perfect sense
> (to me) to have threads 
> doing this kind of thing, and allow me to go back to the main application
> and do something else.
> 
> But at what level would I use a thread?  Would I use a thread to open the
> form that performs the AZ 
> process?  This would allow me to get that started and immediately go back to
> the main app and open 
> another form (using a new thread?) to start processing an order.
> 
> Or would the form open and the button on the form start a thread that
> executes the process?  If a 
> form starts a thread, that allows the user (me) to do other things in that
> form potentially changing 
> to a new directory or selecting a different database.  Do you disable all
> controls on a form when a 
> thread starts?  I never had to think about this in VBA and it is all rather
> confusing.
>