Tom's solution has not worked. But he has offered me more help tomorrow to find a solution.
Why not create a single product that can instantiate itself (or subobjects) more than one way?
The product I am creating is more like an application. It has container objects at the top, and several subfolders that contain hundreds of objects that make up a 'record'. I guess you can say I have tons of data models to go in this application. My whole problem is trying to get things to instantiate more than one way. Once a user has created a record of type #1, he must have the ability to go back and add an extension of type A. In doing this, It alters the way type #1 initially existed. I can't force the user to create a record of tye #1 with the type A extension up front. If only it were that easy, I wouldn't be having such a pain. ----- Original Message ----- From: Dylan Reinhardt <zope@dylanreinhardt.com> Date: Wednesday, May 28, 2003 3:43 pm Subject: Re: RE: [Zope] Another import doesn't find the module
On Wed, 2003-05-28 at 12:33, Stacy Roberts Ladnier wrote:
The line I had that read from Products.Resources.FGDC import profile failed.
Before class1 of DISTINFO.py, I tried the above statement and recieve a 'can't import name profile'.
However, this line works like a charm: from Products.Resources.FGDC import DISTRIB
and is located directly under the above line. Totally baffling me.
Is the solution Tom gave you not working?
Distinfo #1 is in the FGDC directory. Distinfo #2 will
live in
the extensions directory. I want to set of a script in the scripts directory that will cause the #2 to be added. By the way, both of these objects(#1 and #2) should have the same metatype.
This sounds like a pretty brittle system. Why not create a single product that can instantiate itself (or subobjects) more than one way?
Dylan