I'm evaluating the trial version of Reflection Desktop 16 and I'm running into an error on a VBA procedure. The procedure uses the Legacy.Printing.PrintToFile method and appears to properly declare and set the dll at the top of the procedure:

Dim Legacy as Object

Set Legacy = CreateObject("Attachmate.Reflection.Objects.Emulat ion.OpenSystems.dll")
Legacy.Connect = ""

The dll is present in the file path shown in the references. When I attempt to run the macro, I get a "run-time error 429, ActiveX component can't create object". Some sites I'm searching regarding this error mention that sometimes the application must be registered before the class will function properly. Would I be getting this error because I'm using a trial version of Reflection?