>Hi
>I have a .Net application which calls a VFP DLL, it all works as when I run it as an application, but the DLL refuses to even instantiate , no error messages and it does not get to the init of the dll, when I run it as a windows service.
>Any ideas?
>Thanks
>Stuart

There are a bunch of reasons why your VFP COM component may not be working. Usually it's permission related or related to mapped network drives. Your COM component runs with the same permissions as the account that the service is configured for. So if that account doesn't have permission to do something, your COM component won't either. Mapped drives also don't work - you have to use the UNC pathing, ex. \\Server\Share\Dir\File instead. Again, if the account the service is running doesn't have access to the share, your COM component won't either.

Take a look in the event log for any errors.