[dba-VB] Projects vs Solutions

OK, this immediately causes issues referencing objects in another project.  For example I have a 
"main" project, and a "CSVRepair" project.  The Main project form opens when I run the project but I 
then need to be able to open a form in the other project where I gather information about the file 
to fix.

The objects in that other project aren't visible in intellisense.

"Normal" opening of a form is done with something like

MyFormName Somename = new MyFormNname();
SomeName.Show();

Well... MyFormName is not valid in project main.

While we are on the subject, what happens if I just need to dimension a class used in project CSVRepair?

John W. Colby
www.ColbyConsulting.com


Charlotte Foust wrote:
> Think of the solution as the application.  The projects within the solution can be shared with other applications.  We use the projects primarily to group parts of our apps, like UI, Reports, Data, Configuration, Security, etc., but it really is up to the architect of the app.
> 
> Charlotte Foust 
> 
> -----Original Message-----
> From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Wednesday, November 18, 2009 5:07 AM
> To: VBA
> Subject: [dba-VB] Projects vs Solutions