> >>if it can see them, it will try to access them. don't know why, but > makes testing a royal pain... > >I dont understand. If it can see what?. Isnt my problem the fact that it > cant see or find the items? > > if the app or exe can see the forms, libraries in the path, it will try to > run them instead of the copies built into the exe. Hey, isn't this a bit different than it was under 2.x? There it ran from within .exe first. Besides, this behavior (is by design :) may have its good and bad effects: you can have the user SaveAs or SaveAsClass something the user is allowed to change, and it will run even if it's named the same as the original; on the other hand, if user does it bad, it will run bad and the original will not be accessed anymore. p.s. (this is a bit off the subject:) And it may be not the user, it may be someone else (an apprentice programmer or whoever). You probably don't have that kind of problem in the USA&Canada, but here, one of the most common source of damages done to the running software is the infamous "son of the user's boss, who knows much about those conflewctors". Bringing games on floppies (with viruses) was a real menace for a while - so maybe I have a reason to stop complaining about those things being such disk hogs: they simply can't be carried on floppies anymore :)