Hi there
I have a service running with RMS 1.3 that works as a Register. Now I updated RMS to 2.0 with Servicelevel 126. When the service tries to generate the QSRules.SessionClass object nothing happens. No error Message no further action - just nothing.
Has anyone a idea?
Martin
I haven't looked at RMS is a very long time, so this may no longer be accurate, but historically, MS has broken compatability on every build of RMS ( including every Hotfix). This means that if your service is tightly bound to QSRules ( the variable that uses it is declared as type QSRules.SessionClass instead of the generic "Object") that you will need to update your reference and recompile your code each time you install an update to RMS.
I haven't looked at RMS is a very long time, so this may no longer be accurate, but historically, MS has broken compatability on every build of RMS ( including every Hotfix). This means that if your service is tightly bound to QSRules ( the variable that uses it is declared as type QSRules.SessionClass instead of the generic "Object") that you will need to update your reference and recompile your code each time you install an update to RMS.
-- Glenn Adams Tiber Creek C > Hi there > > I have a service running with RMS 1.3 that works as a Register. > Now I updated RMS to 2.0 with Servicelevel 126. > When the service tries to generate the QSRules.SessionClass object nothing > happens. No error Message no further action - just nothing. > > Has anyone a idea? > > Martin
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.