Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Dcom
Message
From
19/01/1999 10:19:30
 
 
To
15/01/1999 15:46:45
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Title:
Re: Dcom
Miscellaneous
Thread ID:
00176675
Message ID:
00177574
Views:
23
I don't think it's any different than on a 95 or NT client or server.
I haven't worked on 98 yet, but this is my understanding from those who have.
You must have a class created OLEPublic - if it's a visual class, in the Class Info dialog there's a check box for this; if it's a coded class, CREATE CLASS OLEPUBLIC (see the help for specifics).

We ran into some tricky situations, where we could only get it to work using NetBEUI protocol (not TCP/IP). From 95 client to NT client we could only get it to work using the 2nd method below.
My $.02 -- this is great stuff but not quite there yet. We have a rather extensive report submitted to MS on our findings. We got word back that they got the report and that we should expect to hear something in a couple of days. This was over a month ago, so either they found something that we totally missed but aren't letting us know or they can't figure it out either.

To use it, you can do one of two things:
1) Create a setup for the remote server app
2) Install from setup on the server machine
3) In the VBR text file created when you compiled the EXE, find the CLSID of the remote server. This will be a 13 character string enclosed in braces {}
4) On the client, issue
ox = CREATEOBJECTEX("", "")
Be sure to include the {} braces in the CLSID string. The server machine name can be the UNC name.

or

1) and 2) as above
3) copy the remote server's VBR and TLB files onto the client machine. If this is included as part of a client app setup, the location (for NT) is WinNT\OleSrv\.
4) Run CliReg32.exe on the app.vbr. This registers the app on the client with instructions to run on the server.
5) On the client, issue
ox = CREATEOBJECT("")
If the class name is myremoteclass and the server exe is myserver,
ox = CREATEOBJECT("myserver.myremoteclass")

Instead of steps 1) and 2), you can copy the the EXE, VBR, and TLB files to the server - an install would have put them (on NT) in the \WinNT\OleSrv\ directory so that's where I usually put them.
Run the EXE with the /REGSERVER switch to register the exe on the server machine.
e.g., myserver.exe /regserver

>What exactly do I do to run remote server (exe) on Win98 machine as a server and use it on win98 client?
>Thanks Mark
Insanity: Doing the same thing over and over and expecting different results.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform