Hi all - the problem I'm having seems pretty straightforward, but I'm at
loss at this point.
The situation is that I've written a COM component which essentially
triggers an access front end, which runs its own code then shuts down.
accessed from the server that the .DLL is actually installed on via the
asp page which calls it, it runs beautifully then exits without any
problems. It refuses to run at all when accessed from any other computer.
Things I've checked so far:
Domain permissions: I am a domain admin, and the file exists in
directories where domains have full control. I've even made the Program
Files directory DA accessible in case that was it.
IWAM, IUSER permissions: even with admin rights, no go
Does this thing actually work in the first place: yes, both on the
production server and within the VB IDE
Did I register it: Yep.
Did I set IIS access permissions: anonymous access is disabled.
What happens when its accessed from another computer: The page it is
accessed from hangs until the browser is closed. On the server, msaccess
is loaded as a service and cannot be unloaded without a reboot.
Any clues?
<edit>
To head off some other questions, yes, the intent is to trigger the access
app on the server, not on the client machine.
</edit>
<edited again>
If you don't have an answer off the bat, any suggestions on
resources/search strings I might try?</edit>
View Cart
