I created an application that had its own database access class
library loaded with objects. I've now created another application
that needs a DBA library that uses some of the same objects as the
other. I created the application, the second DBA and referenced the
original DBA in the second.
When I go to use inherited objects in my application I can only see
the properties that I created in the directly referenced class
library. Will I have to reference the original library in my
application or am I missing something simple here?
Sample Code:
<serializable()> _
public class AStudent
private _strName as string
public sub new()
'blah blah
end sub
public property Name as string
get
return _strName
end get
set(value as string)
_strName = value
end set
end property
end class
<serializable()> _
public class Student 'in the library directly referenced by the app
inherits AStudent 'In original class library
private _iID as integer
public sub new()
'blah blah
end sub
public property ID as integer
get
return _iID
end get
set(value as integer)
_iID = value
end set
end property
end class
The application cannot see the property "Name" in "AStudent".
Cor Ligthert[MVP] - 07 Mar 2008 04:14 GMT
Yes you should set a reference to the DLL where Name is in.
Cor
>I created an application that had its own database access class
> library loaded with objects. I've now created another application
[quoted text clipped - 49 lines]
>
> The application cannot see the property "Name" in "AStudent".
cfps.Christian - 07 Mar 2008 14:03 GMT
That worked, I was hoping that pure inheritance would traverse that
gap as well but I guess my hopes were crushed.