Thanks for the reply Keith, but is there a bigger issue than just vlide error warnings?
Actually that IS the issue ...
The VLIDE automatically prompts the user (using default settings) whenever any code attempts to set a value to a "protected" variable .. which ALL of the variable functions are when you load a type library ...
The VLIDE is doing EXACTLY what it should do... prompting you because your code is attempting to set a variable to a protected variable.
What I mean is that if you keep hitting no, it prompts with another message.
I have to shut down Autocad or bypass the portion of code that loads the type library before it will stop giving me error messages.
That is by design in the VLIDE ....
That's the reason I was wondering if I could test to see if the type library could already be accessed from Vlisp, kinda like vl-catch-all-error-p determines if an argument is an error.
This is not a lisp generated error, it is a VLIDE generated error. To intercept this error you would need to be able to control the VLIDE ... a much simpler solution is to set all of these errors to "transparent" in the VLIDE as I posted earlier, or to prevent them from ever happening, use the code I posted above ....
Essentially what happens is it checks to see if a single variable has already been set, if it has, then it is obvious that the type library has been loaded. If it is not, the it has not been loaded and you can load it without problem.