DLL issues on locked down company laptop

[hamiltpj]

Hi there,

I have recently started a contract with a company who have their company PCs locked down harder than I've ever seen before. The hard drive is also encrypted,

Having failed to get one of my previous (xlsm) workbooks to work, I have saved it as an xlsx and re-added the scripts one by one, and found the key reason to be a couple of kernel32 procedure declare statements, which (even when commented out) cause a sharing violation followed by a corrupt file error when I try to save the file.

in addition, I am unable to add mscorlib.dll in references (no useful error message) and so I am unable to use dictionaries, queues etc.

has anyone come across this sort of thing before and if so how was it resolved?

Many thanks,

Pete

 

[ranman256]

yes, seen it.
they need to allow you (or someone) to add updated DLLs , and register them.
also, make sure all DECLARE statements have both versions, with & w/o PTRSAFE

 

[hamiltpj]

yes, seen it.
they need to allow you (or someone) to add updated DLLs , and register them.
also, make sure all DECLARE statements have both versions, with & w/o PTRSAFE

In what way do they need to be updated and registered? Yes, they are declared for both 32 & 64bit platforms.