Thanks kindly.
The reason I had asked is the two 'offending' etnries in the OperatingSystemName column that caused my buffer overflow (Operating_System_Name_and0 should be 128 wide, but is instead 255 in my environment...the environment is older than dirt, so I don't have a good history as to what has or has not been installed) read as operating system 'darwin x86-64 "UNKNOWN" (Darwin version Darwin K...' (I don't have the complete text in front of me), and show a client under ClientVersion as QMX for ConfigMgr 2.2.0.440.
I reckon this is an older version of QMX than the currently supported one. But if it works the same way and doesn't touch the ConfigMgr schema, I will keep digging for whatever modified this column so I can document the incompatability with my stored procedure.
Thank you very much for your expertise and assistance.