donphillipe
10-08-2009, 02:39 PM
Let's suppose I create a project and someone deletes the reference or there ends up being no file that the reference points to on the system where the project is trying to run and I want to say "Hey dummy, you need this XYZ file to run this". Otherwise all this cryptic (to the user) errors come up; it would be nice to actually have the program state what is wrong.
Short story:
How can I tell what REFERENCES have been added or not, i.e.
Programatically, how can I find out if this line exists.
Reference=*\G{420B2830-E718-11CF-893D-00A0C9054228}#1.0#0#..\..\WINDOWS\SYSTEM32\scrrun.dll#Microsoft Scripting Runtime
Now that I think about it, I guess I could read back to my own VBP file but that seems a little primitive.
Short story:
How can I tell what REFERENCES have been added or not, i.e.
Programatically, how can I find out if this line exists.
Reference=*\G{420B2830-E718-11CF-893D-00A0C9054228}#1.0#0#..\..\WINDOWS\SYSTEM32\scrrun.dll#Microsoft Scripting Runtime
Now that I think about it, I guess I could read back to my own VBP file but that seems a little primitive.