Charlotte Foust
cfoust at infostatsystems.com
Fri Dec 7 09:51:53 CST 2007
Why not just link the project that contains the error class? We work very differently in .Net than we did in Access. Out apps are solutions that contain multiple projects, some shared with other apps. Otherwise, I think you'd need the full path reference in the Imports statement in your data class. Charlotte Foust -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Friday, December 07, 2007 6:39 AM To: dba-vb at databaseadvisors.com Subject: [dba-VB] Lib object references lib obj I have modules out in a library. These objects use other objects out in the lib. For example a data reader uses an error class to log and record errors. Under normal circumstances (a large project) I link those other classes directly into the current project. In the latest case (a very small project) I did not do so, but I did link my data class (which uses the log and error classes out in the lib). When I go into that data class it is informing me that it can't find the error and log classes that it normally uses. The reason is that I did not link those error and log classes in to the current project. Is there a syntax to tell the parent object that the used object exists in the same library and to just go there to find it? John W. Colby Colby Consulting www.ColbyConsulting.com _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com