![]() The correct way in this case is to make the user login as administrator to install. For example when the IT guy installed for the user but into the IT guy's own Window user login, then the actual user will face problem. ![]() But in a corporate environment where the IT Dept has very strict setup, then installation can be a hassle. If they are not, maybe maybe not have problem. And if Reg-Free COM can free me from the problem, then I will embrace it straight away.įor users who are home users and they are administration of their own computers, there is no problem. If this Excel8 Active DLL prove to be a problem for me, then I will consider the Reg-Free COM route and try exploring until I succeed. Reading bits and pieces here and there can be confusing. There seems many ways:ī) Different manifest for program and individual controlsĬ) With and without. Actually this software had been much neglected and is the more work to convert.įew years ago I have searched and read about Reg-Free COM using manifest. Now, after much delay, I am trying to do the same with the 2nd and last software. So the 339 and 429 errors were gone forever for that 1st software. They did not even have to call the IT guy of course so long they have the clearance to install. Since then, I have never had any installation problem feedback, not even from those in very strict corporate IT environment. So when I found Krool's non-OCX common control replacement, I jumped into it and changed my 1st software. There are other situations and can be too long winded so I cut short here. I never had problem installing it at home. I had to tell tell IT to do it this way as above despite resistance from my boss and IT for fear of proceedure and to cover their backside. When I was working in a bank 9 years ago and I previously bot a software (which was an industry standard and very well known and famous trading software) for US$2,999 and I needed it for my work. After that, make the user non Adminstrator again.Īs an example of the problem faced in corporate: So either I am still missing some steps or this is totally beyond me (for Vista, Win8 and Win10).įor users who are home users and they are administration of their own computers, there is no problem. I do understand about packaging and deployment and I am using Installshield (upgraded to cover Win10) to create the installer for my own VB6 written software and have done and change and change the settings but I still had people coming back with 339 and 429 errors. Thank you all for your kind replies and suggestions. Then the question becomes "If you jam all of this into a client program to compile that as a monolith will the client program be too big to compile?" We can't answer that since we know nothing about the client program.īut factoring out the stub classes into a separate DLL or creating an alternative IDL/ODL source and compiling that into a TLB shouldn't be that big of a deal. The Excel8 Project Group itself doesn't look like all that much code altogether though. So that leaves the possibility of "too big to compile as a monolith." Those interface classes could be isolated into a single separate DLL that is only required at compile-time since only their typelib resource is being used - they have no code in them. ![]() We have had reg-free COM for a long time now, and a VB6 monolith can only be so large before the compiler will fail anyway.īut I don't seen anything in the Project Group he's talking about that requires compilation as separate DLLs aside from a few stub classes that are used to provide interface definitions. ![]() I think what he's saying is he wants to create a monolithic VB6 program, one that uses no DLLs (including OCXs, which are merely renamed DLLs) aside from those which are part of a standard Windows install. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |