Load VBX/OCX/DLLs in the Windows System Directory

It’s best to load all shared (or public) VBXs, DLLs, and OCXs in theWindows system directory. Doing so prevents component conflicts betweenshared components that are loaded in the wrong places. By the way, Windowslooks in memory for loaded code modules from VBXs before it looks in theWindows system directory.

Share the Post:
Share on facebook
Share on twitter
Share on linkedin

Overview

Recent Articles: