How can I load packages dynamically which may have duplicate classnames?
I have two packages
Package 1 contains, say 500 forms
Package 2 contains another 1000 forms
Most of the forms in each package depend or relate to each other in some degree.
Also a number of forms in each package (say 50) refer to a form(s ) in the other package.
For example, we have a contact management package. One of the forms in this allows the user to perform a sales order inquiry - but this is in the Sales Package. The Sales order inquiry pulls in say, Stock Inquiry. This is in the Stock Module.
What we now have in the Contact Manager module, when it is built, the Sales Order inquiry screen is compiled (together with all it's dependencies) and also the Stock Inquiry screen (together with all it's requirements).
Loading the Stock Module is fine.
Loading the Contact Manager results in EFilerError " A Class named xxxx already exists..".
Now, these classes are going to be the same.
Is there anyway of suppressing/ignoring this error and loading the complete Contact Manager module.
If not, can you suggest a way to overcome the above situation.