Ok, the next thought that occurs to me (and one that probably makes a little
more sense now that I think about it...
The whole purpose of trying to keep things compartmentalised at this stage
is so I can deploy updates while people are still using the original module.
Is it possible to have a "Front End" module, contained in POL.dot, which
would just contain some code to call a routine from another template, say
backend.dot, which would only load backend.dot when it was actually called.
That being, backend.dot would not be loaded at Startup, like POL.dot
This would allow me to make changes to backend.dot, without having to wait
for everybody to go home. I guess it's sort of like an Access front-end /
back-end relationship.
-Bob
"Jonathan West" wrote:
>
> "Beeawwb"
> news:D4DD2D6C-EBAA-476B-A691-F873F8989A1E@microsoft.com...
> > Hi again,
> >
> > Is there any way to create error handling that doesn't live inside your
> > original module? What I'd like to do is be able to add error handling that
> > lives outside my module, and can be easily updated.
>
> You can pass the error number to an external routine, but that will still
> need to be within your project.
>
>
> --
> Regards
> Jonathan West - Word MVP
> www.intelligentdocuments.co.uk
> Please reply to the newsgroup
>
>