I was having trouble getting my components working with SQL Server and

ASP:



I'm running VB6 and Windows2000 with IIS5 and SQL Server 7:



1. VB registers the ActiveX dll when it is compiled.



2. Running regsvr32 to register the same component again (without prior

unregistering) has no effect.(as expected)



3. Running regsvr32 to unregister this component results in "invalid

ProgID" error in the browser.(as expected)



4. Running regsvr32 to re-register this component has no effect.



5. Re-compiling the dll has no affect at this point unless the web server

is stopped and restarted either from the command line or by restarting

windows. Then it works as expected.



Bottom line: When creating custom components which handle data access

between SQL Server and ASP it is necessary to compile the dll before

loading the asp page in the browser. After unregistering the component it

is necessary to stop and restart the web server before loading the page in

the browser after re-compiling.



If you know why please fill me in.



I'm using "binary compatibility" when the component is compiled. 



This implies that components must be compiled on the web server which I

know isn't the case.



Thanks,



John Hopper