Arash

I use Add Field short cut regularly and I didn't have a problem so far. But I noticed when I try to use it like this example, it causes my RadStudio 10.4.2 to freeze! I put the cursor on "FMyField" and press the short cut(Ctrl+Alt+F by default). Is it just me or is there an issue? type TFoo = class protected procedure NewMethod; end; implementation procedure TFoo.NewMethod; const A = 1; B = 2; begin FMyField := A < B; end;

They were in System32 and SysWOW64! Thanks for the replies.

Tried that already. In fact it worked perfectly fine on my colleagues PC. I even got the BPL and the Konopka folder from his CatalogRepository and replaced it with mine without success. I also tried manual compilation, which works perfectly fine. It goes through and genrates the BPLs. But when I try to add the compiled BPLs to installed packages, I get the same error again.

At this point, I think there is a problem with my windows but any help would be great. I just upgraded to 10.4.2 and right after the installation tried to install Konopka Library. The compilation of the library works fine. (I also tried manual compilation and reinstalling Rad Studio). However, nothing helps as I keep getting the error "The procedure entry point [...] could not be located in the dynamic link library .../RaizeComponentsVcl_Design270.bpl" as you can see in the picture. Any ideas how to fix this?

Thanks for the last few answers. The company is using Azure Identification for basic access to intranet as well as different access levels. So I would either put the code on intranet and hook to it, or try to find a way to check Azure authentication from within the DLL.

Thanks for the answer. It's not an easy question to answer. It includes some sensitive information from the products. However, I'm not trying to hide info from professional hackers and it would be enough to prevent those who don't have access to our intranet.

Thanks for the reply. Two questions: 1- Do you have any suggestion that I can use without going through licensing hassles? 2-When I tried to set the domain of my personal PC to our company domain, I got the following error. Is this easy to bypass? "An Active Directory Domain Controller (AD DC) for the domain xxx could not be contacted. Ensure that the domain name is typed correctly"

Hi, The question might seem too obvious but I am not familiar with the topic. I am writing a DLL to be shared with internal users in my company as well as customers. I want to enable certain features in the DLL only for internal users. Since all company PCs are connected to our domain, an easy way to recognize them is to check for the DNS domain name, using "GetComputerNameEx". However, I was wondering how secure is this? Can someone else simply manipulate their PC to show the same domain name? Edit: In my case, it is enough to limit the access only to those who have access to our intranet. So any other suggestion that might be more secure and doesn't require special permissions or elevation is welcome. Regards, Arash