I don't know much about this (I have only used Standard EXEs, ActiveX
dlls and ActiveX Controls), but I have heard that there are issues with
ActiveX EXEs.  You might want to look in MSDN or Microsofts web site to
see if there is anything on this.

Yehuda

-----Original Message-----
From: Vinay Poddar [mailto:vinay.poddar@s...]
Sent: Thursday, March 22, 2001 4:24 AM
To: professional vb
Subject: [pro_vb] Problem with Windows 2000/ VB 6.0 Activex EXE





We are facing a problem due to unidentified behaviour of Windows 2000
Server. We
are having same application running on Windows NT server and we don't
have any
issue with that. When the application is running in windows 2000
evironment, the
instance creation of ActiveX EXE (VB6.0) behaves abnormaly. The issue is
being
detailed as per below:

Functionality

For processing reports, we are using two programs - primaryreportexe and
secreportexe.

Primaryreportexe is a std exe and the other one an activex exe which has
a class
  with property single use instancing.

The reportrequests submitted by users go to a table.PrimaryReportexe
which runs
always has a timer with 10sec interval.
During each timer event, it looks for report request in the table, and
if it
finds one, creates an instance of secreportexe and
calls a method of secreportexe for running the report.

This method calls the Settimer API function with arguments as 1000 and
AddressOf
 gprProcessSP. gprProcessSP will be
run after 1sec. Timer is used to make the secreportexe processing
asynchronous.
After completion of the report, secreportexe fires an event which will
be
captured in primaryreportexe and will kill the
secreportexe instance.We have set a limit of maximum 5 secreportexe
programs
running at a time. Everytime the
timer event occurs, primaryreportexe checks for the number of
secreportexe
instances running and if it is less than 5 and there
is a request submitted by user, creates an instance of secreportexe.

Environment

These programs are done in VB6.0 SP3. This was running fine in Windows
NT. Now
we compiled these programs in Windows
2000 server environment as our servers are going to be Windows 2000
Server SP1
and we are running these programs in Windows 2000
server environment. In Windows 2000, we are facing  problem.

Problem

If already an instance of secreportexe is running (gprProcessSP is
getting
executed. gprProcessSP calls Stored  procedures
in Oracle.), createobject (secreportexe) method called from
primaryreportexe is
hanging till the running secreportexe
finishes the job. So basically at a time only one secreportexe instance
is
running. SecReportexe project properties are set as
unattended execution and Thread per object.
We tried without unattended execution setting, but no success.