Blair,
We are sometimes have good control over the code and can check it, but
not all the time, especially during the (near) real time processing that
the program does. At that point we just do a fileIn and hope for the
best. It would be quite a duplication of effort to pre-compile all the
code (hoping to match the exact syntax of Dolphin and the lookup rules
for variables) to check for undefined variables beginning with capital
letters so as to prevent Dolphin from complaining later. I have read
several times about the compiler being due for an update, so will
probably cross my fingers and hope none of our users run into the
problem in the interim.
Thanks,
Keith
Blair McGlashan wrote:
>
> Keith
>
> You wrote in message news:
[hidden email]...
> > The message box with the text in the subject line seems to originate
> > from the compiler (DolphinCR004.dll, but also earlier versions) when an
> > unknown variable with a capital letter is found while code is compiled.
> > Is there a way to suppress this message? It appears not only with the
> > development session manager, but also the runtime session manager. We
> > don't want end users to see it and need to automatically answer no. Is
> > that possible?
>
> It does come from the compiler, and I don't think you can suppress it in 4.0
> (except of course by ensuring that the globals are predefined - are you not
> in control of the code that is being evaluated?). This is not very flexible,
> so I will see if we can do something about it for the next release as an
> enhancement.
>
> Regards
>
> Blair
Locked
