Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
File access denied error
Message
General information
Forum:
Visual FoxPro
Category:
Installation, Setup and Configuration
Miscellaneous
Thread ID:
00547444
Message ID:
00547779
Views:
8
>Thanx for everyones suggestions. I found th eproblem because of all of the thought provoking that your clues triggered.
>
>I had a dll with the same name as the exe that was instantiated via IIS. All I had to do was rename the exe. All all is well.
>
>I have one more question: What is everyones thoughts on checking the Regenerate Component IDs each time I build my dll or exe. I don't really understand this aspect of components and executables.
>

You don't need to Regenerate Component ID each time you build the new version if you just changing some code in COM without changing its interface. I would suggest to regenerate it only if you are building the new version of your COM with changed interface - with different exposed methods or properties. I myself, when I experimenting a lot with different COM versions, periodically clean out the registry from my COM entries, otherwise it eventually creates a mess in registry and you can see many strange things happening. You might try COM Explorer utility for this, http://www.4developers.com
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro

"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform