[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::visual_basic

Title:Microsoft Visual Basic
Moderator:TAMARA::DFEDOR::fedor
Created:Thu May 02 1991
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2565
Total number of notes:10453

2501.0. "OLE automation Intel->Alpha" by ULYSSE::CATTOLICO () Thu Feb 20 1997 05:11

     Hi,
        
            I am running a small client/server application usin ole remote
            automation on WNT Intel and Alpha.
        
            The server implements a class "boh", the client creates an
            object of this class and send some data.
            I have developed it in Visual Basic (VB4 on Intel, VB5 on
            Alpha).
        
            The strange thing is that my application works fine if
            BOTH client and server are running on machines with the same hw
            (Intel->Intel or Alpha->Alpha); however, if I try the client on
            Intel and the server on Alpha, or viceversa then I get,
            on the client screen, when I issue the CreateObject
            instruction:
        
            Run-Time error '429' - OLE automation server can't create
            object
    
            Any hint?
        
        Thanks in advance
        
        Paolo
T.RTitleUserPersonal
Name		DateLines
2501.1ELIS::TOWERSThu Feb 20 1997 10:2123
    Paolo, on my last project I developed a shell client and four
    out-of-process OLE servers. The first time I built everything, put it
    into a kit and tried installing the kit everything worked wonderfully.
    Then I wanted to change something in one of the servers. I made my
    change, built the exe, put it in the kitbuild area, built the kit (we
    were using InstallShield3), installed it and tried to test it.
    
    Lo and behold! I got the same error you got. To get round this problem
    I had to rebuild the *client* even though it hadn't changed. What I
    deduced from this was that the client had built into it the guid for
    the servers. Chnage one of the servers, resulting in a change to its
    guid, and you have to rebuild the client.
    
    What I think this means for you is one of two things:
    
    1) You can't do what you want to do, or
    2) When you build the client you have to point your link for the server
       to the alpha version on the alpha machine. As I'm sure you know you
       do this via the Tools/References menu. I'd test this option
       interactively before I went to the trouble of building a kit etc.
    
    Cheers,
    Brian
2501.2not there yetULYSSE::CATTOLICOFri Feb 21 1997 04:4122
    Brian,
    
         thanks a lot for your answer.
    
     I tried everything.... unfortunately rebuilding the client did not
     help.
    
     What I did so far is: 
     - write an OLE server on ALPHA.
     - use it beautifully from ALPHA NT client applications
     - On WNT Intel, I succesfully register the TLB file for "serva" using 
        the Microsoft Component Manager (include in VB4).
  ---- Strangely, I do not see the name of my server in the
        "Remote Automation Connection Manager", as I expected.
       
    This last point, I guess, leads to the "429-OLE Auto can't create
    object" error, because my server is unknown.
    
    Still investigating......
    
    Paolo