Hi all,

Ran across this bug in some 3rd party VFP code. When users were logging into their RDC server and are running a report that first opens an "options" form, they were getting error messages upon every instantiation of a text box. It was hard to get at the error as the code is a 3rd party report writer that takes control of error handling.

But I finally tracked it down to error in this code:

IF NOT '\XXFw.vcx' $ SET('ClassLib')
   SET CLASSLIB TO XXfw.VCX ADDITIVE
ENDIF

Since the left side of the IF statement is in mixed case and the right returns uppercase, the SET CLASSLIB TO was firing on every textbox.

This raises an error when the form is run on the RDC server but not from users within their office. The error was #24 "Alias is already in use".

I also could not reproduce it from my dev machine.

It seems that if you reissue a SET CLASSLIB that there generally is no error - but somehow on RDC there is.

I fixed the code but just was wondering if anyone knew why the behaviour. Is there some setting that affects what happens if SET CLASSLIB is set to an already open class?

More curious than anything.

Albert