Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Distributed Processing Design Question
Message
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Network:
Windows XP
Miscellaneous
Thread ID:
01137136
Message ID:
01137445
Views:
17
Ok, I take the "not as difficult as I thought it would be" statement back! Setting up a standard remote COM+ component is easy enough. Implementing it with MSMQ is not so simple.

I missed the Export process from the server side and having to run the installer on the client. I also missed the fact that I had to have message queuing installed on the client. After doing that, I got it running.

Now, I can run this from the client app:
oTest2=GetObject("queue:/new:testcomserver.myclass")
It creates the queued object fine (I think).

But, there's a problem when I call the method that counts to half a billion.

=oTest.MaxCPU()

Now, this runs apparently in a loop forever and eventually takes over the CPU at 100%.

Any idea why this would happen?
Previous
Reply
Map
View

Click here to load this message in the networking platform