Remote Automation : Windows 3.1 client/ Windows NT Server 
Author Message
 Remote Automation : Windows 3.1 client/ Windows NT Server

        Has anybody had any successes in implementing enterprise systems that use
Remote Automation between a Windows 3.1 client and a Windows NT server? I
know that this works, and I've seen simplistic examples of it. My questions

        1) Generally, how SLOW is it? How about relative to DCOM?
        2) Is it good for anything but LOW volume transaction processing?
        3) Are there any other "gotchas" I should be aware of?

        Our servers are all NT, but.....we've got a whole bunch of  3.1 clients
and are looking for a suitable migration path to the 32 bit world. This is
especially true for new development. We want to position the new apps so
that when all our clients are 32 bit, we can take advantage of 32 bit's
inherent benefits.

Sun, 23 Apr 2000 03:00:00 GMT  
 [ 2 post ] 

 Relevant Pages 

1. How To: Windows Service w/ remote clients, i.e SQL Server

2. Newbie: VB4, Windows 95 platform, Windows 3.1 target

3. Compile under Windows 3.1 different from compile under Windows 95

4. writing vbscript to know the OS of a remote PC ( is WIndows NT or WIndows 2000)

5. Windows NT Password Change From Windows 95 Client

6. Windows NT Users form a Windows 95 / 98 Client

7. MDB and rpts in OS/2 server while programs in Windows 3.1 workstation

8. Netware 3.1 , Windows 3.1 and VB

9. Using WINAPI 3.1 call FindExecutable on Windows 3.1

10. Windows NT (Excel VB) to Unix inetd Client-Server Link

11. Client side ActiveX control accessing SQL Server with Windows NT Security

12. Enumerating NT Server Connections from a Windows 95 Client and VB4.0


Powered by phpBB® Forum Software