"Myrna Larson" wrote in message
...
Do you know about Tools/References in the VB Editor? You can set a
reference to Personal.xls or
the workbook that contains your code. Maybe that will solve your problems.

That would be too simple. I tried it and Excel gave me the finger and told
me that I couldn't use that file. Or any other .xls file of any name living
in any directory.

I expected no less. Thanks for trying.


On Fri, 25 Jul 2003 14:35:34 -0700, "Terry von Gease" wrote:

I need to know it there is any realistic way, the operative word here is
realistic, to have vast tracts of VB code exist and be usable independent
of
a set of worksheets.

The application is only 4 or so sheets but the volume of code supporting
the
application is quite large. Unfortunately in the MS world, elegance is
expensive. The problem being that the entire .xls file is unacceptably
large
and not only saves at glacial speeds, it seems to have grown to the point
where Excel's reach exceeds its grasp and is somewhat delicate. Saving
the
file while doing development is unpredictable and often entertaining.

Using a personal.xls file will keep the code separate and get it to load
but
actually using it is painful. The 'Application.Run' method is
unacceptable.
Not only is is exceedingly clumsy, you cannot use named parameters.

Is there any way to tell Excel where to look to resolve procedure
references? Or am I simply SOL?

--
Terry

"I said I never had much use for one,
I never said I didn't know how to use one."
M. Quigley