Doing something like S CIPHER=##class(%SYSTEM.Encryption).AESEncode(text,key) in COS compiles fine, but doesn't appear to actually do anything. CIPHER is returned as null. One of the support technicians that I talked to suggested using the object factory to expose $system.Encryption in the VB app. I'll be sure to mention this to them. Thanks.
"Bill McCormick" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > A lot of the $SYSTEM functions are wrappers to c functions in Cache. > They are not true cache class projections but merely wrappers and won't > project to COM. If you can't say ##class(%SYSTEM.Encryption).Method() in > COS it won't work in COM as a rule of thumb. Don't be afraid to bring > these to the attention of support though. It just means that the system > guys did not complete the job and write the class wrapper. > > Mike Hershberger wrote: > > > I'm trying to use the Cache Object Factory to expose the %SYSTEM.Encryption > > class to a VB6 project. I keep getting the message 'Failure to create > > %SYSTEM.Encryption. <METHOD DOES NOT EXIST>OpenObjectEx+8^%apiOLE' when > > trying to use Factory.OpenId or Factory.New with %SYSTEM.Encryption as the > > class name. The connection to Cache was established successfully using > > Factory.Connect. Does anyone have any thoughts on why this might be > > happening? I can provide the code if needed. Thanks. > > > > Mike > > > >
