Wow, I didn't know I was still subscribed to this thread. This is going to be extremely complicated how I got to this solution so hold on.
I found a workaround that was barely acceptable to me. I figured out that all the tags in RSView are kept in a file called tags.db in one of the folders under documents and settings - all users - rsview SE. (I am not so sure about that either as I haven't worked on this in a very long time.) I tried opening this file in every conceivable database program but nothing could recognize it. After hex editing it and looking for anything recognizable or that I could cross reference with another known database, I determined it is a Watcom SQL 4.0 database, circa 1992 or something like that. It turns out that this was a very useful and well regarded SQL server for that time period in certain circumstances. Unfortunately, this company ceased to exist in 1996. I tried buying about 10 books off ebay about using watcom databases, hoping that the software included with one of them would have an odbc driver, but none of them did. After researching this a lot further, I found that watcom's IP was sold to sybase I believe and they have a program called SQL Anywhere. It did come with an ODBC driver, so I did try this to connect to the DB but it requires authentication. I should also mention that when you install RSView it does install an ancient Watcom ODBC driver that was obviously written for windows 3.1 but it didn't work at all and would crash on 3 different computers we tried it on. Installing SQL Anywhere made this driver work again for some reason. Later because it was discovered that NERO 6.0 CD burning software was causing problems with a very advanced in-house application we uninstalled it, and I think that this magically made this driver work again. (It's been almost a year since I've touched this so I may be wrong). Back to the authentication, we were able to intercept the calls to the ODBC driver and determined that the username was "MMIUser" so one of the first passwords I tried was "MMIPass" and amazingly, it works. We can now pull this Database into any ODBC aware software such as Access and get all the low level stuff. I believe that this driver and login info works for all of the RSView SE databases such as the alarm log. We were then able to see how any tag was created, what all of its parameters were, and therefore import the tag database into our software program and recreate anything that RSView does on our own by emulating the processes that RSView has going on. This along with figuring out how to hack interprocess communication to work within an ActiveX control embedded inside RSView allows an amazing level of two way communication and interaction between RSView and external programs.
Since it's been almost a year since doing this I may have gotten a lot of details wrong, so post if you try to do something here, or if something needs more description and I'll fill you in some more.
I'm pretty glad that RSView32 is dead...
