Messages
Reply
Edit
Delete09:40 pm
3T31AGQFL
| From: | Alex Sosa |
| To: | Rick Strahl |
I logged in as Administrator and ran command window also as administrator. I changed directory, ran VFP9, opened project, and asked to compile to exe. The screen froze for about 5 minutes at the end before ending with the exe created. Very slow, but it worked. Is it always that slow?
This was an important tip Rick. Thanks.
Alex
Alex,
You have to run as a 'true' administrator. If User Account Control is enabled you are NOT a real administrator.
To properly register any COM component you have to start a command prompt and use the Windows Run As Administrator option from the shortcut.
+++ Rick ---
Sorry for this very long explanation. I've been compiling a project into exe for a long time and recently started to have trouble. Here is sequence of possibly relevant events:
1) I installed VFP9 SP2 for the first time and made a new copy of Payday, our main project, to continue development with SP2. Old versions continue to be maintained with sp1.
2) Since both old and new versions of Payday share class libraries, old copies of the project along with a copy of shared classlibs were moved to a new disk to continue development with VFP 9 SP1 installed in a virtual machine
3) By mistake, a support person continued to use SP1 for a seldom used older version of Payday in same disk as the new (SP2) version resides
4) Apparently shared libraries (vcxs) were gradually recompiled alternatively by sp1 and sp2, with growth of vct files.
5) When finally I compiled the SP2 version of Payday into an exe for the first time, I found that it ended with a very small (12 kb) exe file and very large (70 mb) app file.
6) Investigating, the info of point 3 above came up. Thinking that size was the cause that exe and app files don't properly combine, the large vcx/vct files were packed and the seldom used version was moved to the new disk
7) --> This week we installed a new server and Active Directory for the first time
8) Now I started to get "Access to the Registry Key Denied" at the end of the compilation into exe, when COM component was being registered
9) A web search brought an MS article "FIX: "Access to the Registry Key Denied" Error Message When You Register .NET Assembly for COM Interop"
10) I followed instructions on how to unlock registry keys, but the problem persists.
I come to this site because expertise in VFP/.NET interop is abundant here, especially with Rick.
Does anyone have suggestions?
TIA,
Alex
