Note: To post to a thread, you must be logged in.
Hi Scot,
Great site... I'm a relative newcomer to ORM, and I'm really enjoying the info you've collected here. Thanks.
I'm having a problem running Orthogonal Toolbox... I have VEA SP-2 on a Windows XP machine, with .NET runtimes v1.0 and v1.1 installed. I can install the Toolbox just fine, can see the toolbar button just fine, but when I open an ORM source model and click the 'Orthogonal Toolbox' button, nothing happens.
I haven't run across any documentation that expressly forbids my current setup (though I haven't seen any specific reference to VEA SP-2). I'm wondering if you might be able to point me in the direction of a possible resolution? Have you heard of this sort of problem before?
Incidentally... I had the exact same issue a few months back, on an entirely different XP machine. Toolbox installed just fine, but no functionality.
Any advice? I'm dying to dig into your tool... :-)
Thanks,
Josh Lane
Hi Josh,
Haven't seen this one before....
By any chance, do you have the Visual Studio 2005 beta installed?
Scot.
Thanks for the quick reply, Scot...
Nope, no beta software... this is fairly standard production dev machine... VS.NET 2003 EA, VEA SP-2, Office 2k3 with all patches, SQL Server 2000, various dev utils, etc.
One more thing... it's working now. All I did was go eat my dinner. :-)
Honestly, I can't explain what happened. It didn't work... I closed Visio, ate my dinner, came back and opened up the same ORM source file that didn't work before, and bingo... OT works like a charm. One other difference I'm noticing between then and now is that I didn't see the toolbar icon before (when it wasn't functioning); I see it now. Odd.
I've done a little Office automation and integration work in my time, and it's definitely a strange beast... but I can't offhand explain this behavior. But if you're interested in reproducing the problem and want more details of my setup and configuration, let me know... I'll be happy to help.
Josh
Hi, Josh,I have heard about such and all kind of problems from myself.I just reported similar case - the need of VEA restart [1]. I shifted to using VMWare (virtual machines) and have bare minimum what I need in each machine and do not mix things and installations.It is possible to mount a network inside one PC with thisIf u still spoil your machine by Office Automation, I advice u to look over MS opinion on it [2]VGV
[1]G. Vanine. "restart system" confuses. This forumhttp://www.objectrolemodeling.com/Discussions/tabid/27/forumid/5/threadid/235/scope/posts/Default.aspx [2]"Considerations for Server-Side Automation of Office"http://support.microsoft.com/kb/257757/EN-US/
Must have been the dinner. Did you have chicken? ; )
Very strange. I am using an MS office toolbar which is a bit of a pain in the butt. I would not be surprised if that was the culprit somehow.
Glad it's working now.
Scot Becker in [1] also mentioned that OT uses registry and registry can't be read without "system restart" (added later: well, in those COMs, i.e. MS Office components... Huh, I pity that i mentioned it).Just keep reading