Chicken and Egg Models Dont Load -- Begack!

[eluser]jedd[/eluser]
I suspect the general workaround is to not do it

Can you rip the common / reliant code out and stick it in a library? I reckon that'd be your best bet, and that way both models can reference the functions from the library.

(I don't think two models should ever need to rely on each - if they do it probably means you've designed the scope of your models sub-optimally.)