I am designing a somewhat complex Module/Application for a client. Many tables are required to hold all the information needed. As such, I started my application development with a single table and built my first ControlPages. Now I am moving on to another table, which is a child table to the first one I designed. I figured I'd create a new DataProvider class for it, along with the Abstraction Class and Implementation Class, etc. All seemed to work fine, until my new class ran the line of code in my new DatProvider Class's CreateProvider() method that stated:

CType(Framework.Reflection.CreateObject("data", "ESB.Modules.EAP_Provider.Data", ""), DataProviderLocation)

It claims that the object created is of datatype DataProvider (my original one) and cannot be cast into DataProviderLocation (my second one). I am assuming that Framework.Reflection.CreateObject() is hard coded to instantiate a "SqlDataProvider" class object within the Namespace provided. "SqlDataProvider" is coded to inherit from DataProvider...which makes sense why I get the error I am getting.

My question is, is there a way to override the default and have it in this instance, instantiate a different class, the correct class needed.  I was thinking of just hard coding the class needed, but since the original code is using reflection, I was afraid that hardcoding the correct class, would break something else down the line.  I would have assumed that multiple DataProvider classes wouldn't have been a problem.  Figured it was a normal enough thing to do...

Any advice?

---

Ben Santiago, MCP Certified & A+ Certified
Programmer Analyst
(SQL, FoxPro, VB, VB.Net, Java, HTML, ASP, JSP, VBS, Cognos ReportNet)