Are there rules/policy for creating a new ADO VS project to a solution? When
should I create a new ADO project for a VS solution? Is there anything like
a limit to the number of object files you can have to a VS project?
Background:
I have a top level local business getter application/project (lets call it
ProjectA). One of the things this project links to/gets is an Access ADO
application (DataSet, etc) for one particular database. The ADO files are
physically located in ProjectA and, use an Interface file I wrote.
Now, I need to use this same Interface file/template and write additional
ADO type applications for other/different databases which need to be
accessible from ProjectA.
Should I:
- Copy and save the existing solution ADO application files into a ProjectB
so I now have a VS ProjectA and an ProjectB (other ADO applications will be
placed into a ProjectC, ProjectD, etc)
- Keep everything in ProjectA? (very messy)
- Start all new ADO applications from this point forward into separate
projects?
AND (most important) where should I place that ADO Interface file so I can
get at it? How do I get at it?
I hope I haven’t lost you. Please/requestyou take the time to respond or
point me in a direction.
Steve