Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Visual Basic > VB 6 Visual Basic 6 > Pro VB 6
Password Reminder
| FAQ | Members List | Search | Today's Posts | Mark Forums Read
Pro VB 6 For advanced Visual Basic coders working in version 6 (not .NET). Beginning-level questions will be redirected to other forums, including Beginning VB 6.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Pro VB 6 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old May 30th, 2006, 07:37 AM
Registered User
Join Date: Feb 2006
Location: YORK, Yorkshire, United Kingdom.
Posts: 9
Thanks: 0
Thanked 0 Times in 0 Posts
Default COM Question...

I have an important technical query about COM....

I have a small project which requires some work to finish it off.

The scenario is as follows:

I have a VB6 application on server A (it has to be a VB6 app because it has to respond to a DDE request) which needs to launch an application on server B.

The application on server B is also a VB6 application and uses COM to communicate with a third application on server B. The third application on Server B has a GUI which is required to be displayed to the user on server A. so far I have embedded a MSRDPCLIENT object in the application on server A, which successfully launches the application on server B.

The problem comes when a new request is received by server A. The embedded MSRDPCLIENT object only seems to have a disconnect function which doesn’t end the session on sever B – meaning that a new connection request creates a new session – this eats up server resources and will bring server B to a halt very quickly. What I need is a way of communicating to the already established session, telling it of a revised parameter and allowing the existing session to do it’s stuff.

My research has led me to believe that there is something called VirtualChannels which would allow this communication to take place, though I am unsure if this is the case or not.

Hope you can help.



Darren Brook
email: darrenbrook@btconnect.com

Reply With Quote
  #2 (permalink)  
Old June 5th, 2006, 03:26 PM
Friend of Wrox
Join Date: Nov 2004
Location: Port Orchard, WA, USA.
Posts: 1,621
Thanks: 1
Thanked 3 Times in 3 Posts

Well, of course you could pass a "Commit suicide" instruction to the process on B.
Or, you could just keep your communication with the original instance (which apparently is the persistent instance), and just change the subject, so to speak. In otherwords, don't disconnect.

I don't really know anything about the actual question youasked regarding VirtualChannels.
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
question maheshraju ASP.NET 2.0 Basics 3 March 13th, 2008 08:54 AM
Question Ashwini Classic ASP Databases 3 January 10th, 2006 07:20 AM
Question? Calibus Classic ASP Databases 8 August 6th, 2004 08:25 AM
a question gorji C++ Programming 2 August 11th, 2003 07:41 AM

All times are GMT -4. The time now is 08:10 PM.

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.