I've missed something here - some part of the install process - maybe
someone can spot it;
My Install process is (new server);
1. IIS Up and running
2. .Net 2 (from windows update)
3. Foxpro installshield includes VFP runtimes
4. Test
I have a com object I use on a IIS Server
recently I purchased a new server W2003k - same as old one
the com object works on the old server
I've gone back to the installshield and recompiled all that
the com object runs from a vbs script on the server
also .aspx runs ok until it tries to communicate with the com object
i've got it down to this -- this works on the old server, not the new --
Foxpro Com Object compiled multithreaded com server
---------------------------------------------------
Define Class test As Session OlePublic
DATAPATH = ""
Enddefine
Put this on server and register with regsvr32
VBScript Test Ok
----------------
Set obj = CreateObject("t1.test" )
obj.DATAPATH = "Something"
msgBox obj.DATAPATH
ASP.Net test Fails
------------------
Dim y As New t1.test
y.DATAPATH = "something"
the error looks like this
-------------------------
The server threw an exception. (Exception from HRESULT: 0x80010105
(RPC_E_SERVERFAULT))
and shows the line ...
thanks in advance
David Bray
Regards
tom
"David Bray" <"david - at - brayworth dot com dot au"> schrieb im
Newsbeitrag news:e3dEpqsQ...@TK2MSFTNGP06.phx.gbl...
Thanks for your thoughts on this tom - my answer has been to go through
the code and late bind the foxpro com objects (i.e. use CreateObject ) -
which works .. but ..