Joel,
After you've included those files in your IS project, right click on the files that need to be registered (yourdll.dll,vfp7t.dll and the vc7++dll) and for the registration options, select "self register". The "Extract COM" option has not worked consistently for me for registering dlls.
>Claude, maybe my problem is with Install Shield Express. When I define the build parameters in InstallShield, specifically when I configure it to register my dll, should I do "self registration" or have install shield register my dll? And do I also need to configure it to register the vfp dll's and/or runtimes that you mention below?
>
>Again, thank you. Your help has been so generous and helpful in finding my way through com+ and dll development.
>
>Joel
>
>>Not that I know of - just make sure you include the tlb,vbr,vfp7t.dll,vfprenu.dll, and the vc++7 runtime and it should register fine...
>>>Claude, are there any issues regarding registering a VFP 7 dll on XP Professional? Any issues using regsvr32 on XP?
>>>
>>>Joel
>>>
>>>>There were some articles on COM+ on this site:
>>>>http://www.craigberntson.com
>>>>>Claude, is there a good book or article you can point me to that explains COM+ component installation and configuration?
>>>>>
>>>>>>Joel, I use COM+ and .vfp. mtdlls primarily for web apps, so, yes you can definitely set up once on a server and use from other computers without the runtimes. If you were to install this server application somewhere else, you might want to look at the Exporting feature although in earlier versions, I couldn't get this to work...
>>>>>>>Claude,
>>>>>>>
>>>>>>>Thank you so much. I implemented your suggestions below on a Win 2000 workstation and my COM+ component worked great. Now I have just one more question.
>>>>>>>
>>>>>>>If I want to implement my COM+ component on more than one workstation on the LAN, must I use your impersonation/identity configuration directions below on each work station, or is there a way to implement/configure the impersonation/identity of the component once, like on the server, so that any workstation can access and use the component? Also, must each workstation acessing the component have the VFP runtime installed?
>>>>>>>
>>>>>>>Joel
>>>>>>>
>>>>>>>
>>>>>>>>On Windows2000, go into Control Panel, Component Services:
>>>>>>>>1.)Right click COM+ applications and select New.
>>>>>>>>2.)Using the wizard, create an Empty Application,giving it a name/check server application, and selecting the appropriate account to run under.
>>>>>>>>3.)After the Empty Application is created, Right click on 'Components' under the newly created application.
>>>>>>>>4.) Select New/Component.
>>>>>>>>5.) The wizard starts - select 'Import components that are already registered.'
>>>>>>>>6.) Select the name of your vfp mtdll from the list and it will be added to this new COM+ app.
>>>>>>>>7.) Right click on the new COM+ application name and select 'Start'. The COM+ icon is now revolving in the Components pane.
>>>>>>>>It should now be running under COM+ now using the Impersonated User.
>>>>>>>>>Claude, how do you give an mtdll "the proper impersonation/identity." I don't know what this means. How do you implement the proper impersonation/identity? I want to use the mtdll to create a function in Excel using VBA that can access data from VFP tables on a network drive.
>>>>>>>>>
>>>>>>>>>Joel
>>>>>>>>>
>>>>>>>>>>For networked access to your vfp database, you've got to run your mtdll from COM+ (create a COM+ package) giving it the proper impersonation/identity. Same with using a mtdll with SQL/MSDE/Oracle/MySQL...
>>>>>>>>>>>I'm sure this question has been asked 1000 times but this is my first exposure.
>>>>>>>>>>>
>>>>>>>>>>>How do you access a mapped network drive from a VFP DLL? I seem to be able to access local data but not data on a mapped network drive. Will someone please point me to an article on this?
>>>>>>>>>>>
>>>>>>>>>>>Thank you.
>>>>>>>>>>>
>>>>>>>>>>>Joel