Actually turns out I got the OCX application to work on the workstation for only one Pivotal system. I've gone back to the test OCX program that Pivotal distributes rather than my code. This is a straight VB6 application and I'm getting very strange behavior. Wonder if the following rings a bell with anyone:
I'm experimenting with the test VB6 program that Pivotal distributes with the OCX itself. It runs great on my development LCS machine. It runs great on the production LCS machine. When it put it on a third machine that does not have Pivotal loaded, things get odd.
Development Pivotal systems are called "Demo" and "DemoOffline".
Production Pivotal system is called "Pulse".
On the third workstation I have copied over the Pivotal System Manager program and the needed DLL files. I have setup ODBC entries for all three Pivotal systems mentioned above. I have defined the three systems using Pivotal System Manager.
When I run the test OCX program, I can connect successfully to "DemoOffline" only. On the other two systems I get the message:
Pivotal eRelationship was unable to initialize the Active Notification Manager. Mobile systems cannot be kept synchronized without the Network Notificaition. Do you want to run Pivotal eRelationship in Read Only mode?
Its weird because "Demo" won't work but "DemoOffline" will. Both are on the same LCS box and of course "DemoOffline" is the offline version of "Demo". I've looked at all the obvious things and have even gone so far as to copy the registry keys from the development LCS to the third workstation but no luck.
There's nothing else of Pivotal installed on this third workstation, no Windows Access for example. I can hit all three systems successfully using Active Access.
