I think, you cannot access public variablis in standard .EXE as you did it with classes or ActiveX controls. One solution is to create out-of-process server (ActiveX EXE), which public variables you can access (more reliable solution in this situation is to create public properties instead of public variables). If you cannot create ActiveX .EXE, other possible solution is to export variables (for instance, in some file) and import them in other application. In this situation, you must know when to export variables. Best solution is to use database and to update immediately variables in it (you can store them into table). Other application will get variables from database on demand. One more solution: you can organize communication between two solutions with WinSock controls: First application listening on some port for requests. Second application makes request and first application returns values of variables in some format (for instance, =;=;...;).

Plamen Ivanov
MCSD .NET Early Achiever and MCAD .NET Charter Member (VB .NET/SQL Server 2000)
MCSD (VB 6.0/SQL Server 2000)
VB (.NET) - what other language do you need in the whole Universe?...