>>>>>>Project a and project b include class A, class A calls form A. Don't need form A in project a but do in project b. recompiling wants to suck it in or produce an resolved reference error. Any way to:
>>>>>>
>>>>>>1) exclude Form A from project a without coding the exclusion in every call -- do we have to add it to the project and exclude it?
>>>>>>2) suppress errors for unresolved references?
>>>>>
>>>>>Do you mean there is a code in class A that invokes this form? I don't think there is a way around it, but take a look at EXTERNAL command in Help.
>>>>
>>>>EXTERNAL doesn't work that way....(tried it)
>>>
>>>Then one option is to exclude the form and another is to create a light weight version of the same form with this name.
>>
>>Thanks everyone. All of these options we have considered, but trying to go with one that involves the least amount of code mods or project file mods - we've tested every one already including the pre-processor and compile time constants which work as well.
>>
>>Not sure which route we'll go yet, still hoping for a cleaner solution....
>
>
>The least amount of code mods is to add a form - called A - to the project that is complaining. You can exclude the form from the project if you wish
So far that is what we are doing -- adding some dummy forms.... :o)
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"