The times I've built COM servers, I haven't needed to keep unregister / register the servers. And when I did do the "regenerate component IDs", it always appeared to create all new GUIDs for the servers. Then, when looking into the registry you would have as many entries as you did "regenerate IDs".

If you are only changing existing functions in your server, you shouldn't need to regenerate, nor reregister... The IDs are basically labels/pointers to the main function to create your com server, where the file is located, etc (check you .VBR file corresponding to your .EXE).

So, any new methods/functions you have should make themselves visible on subsequent calls with no other changes (provided you don't make the metods as hidden or protected)

HTH


>I have a VFP app (call it main.exe), that calls/uses 2 other VFP apps (call them com1.exe and com2.exe). All are EXE's. The 2 called/used apps are COM.
>
>On the workstations I have another EXE (startmain.exe), that checks the local copies of main.exe, com1.exe and com2.exe against the server copies. If the server copy is newer (as in I did an upgrade), the server copy is copied over the workstation copy of the exe(s).
>
>My question: When I have made modifications to com1.exe and/or com2.exe, do I need to reregister these com's, on the workstation, after copying the new version to the workstation?
>
>I have always done the following everytime I rebuilt the exes, i.e.:
>com1.exe /unregserver
>com1.exe /regserver
>com2.exe /unregserver
>com2.exe /regserver
>BUT, I do not know if it is necessary. Is it?
>
>Just in case it has any effect, I should tell you that I always rebuild the exe's with the "regenerate component id's" option. Why? I do not know. I can't understand anything I have read about this subject. I just do it because I am afraid not to.
>
>Thanks,
>John