Solved Invalid Procedure Call Or Argument On Everything!

[MajP]

Then again (I don't mean this to sound argumentative) but listen to some of the justifications in #13 for data corruption.

I think we are agreeing and not arguing. My point is that it is hanging on compilation, because it is corrupted not because there were names in conflict. A simple naming conflict of existing object would be caught without corruption being a factor. A naming conflict due to something within the compiler is a different problem. That is my understanding how a form can be corrupted. There is basically some phantom garbage hanging around and it cannot recompile the code when it hits that. This is why I am suggesting building from new and exporting the objects.

On creating a fresh db & importing the objects on execution it then did what it should have in the old db & jumped to:

Below in a certain form; which I don't think there is anything wrong with & was not Publicly scoped. There was another combobox with the same name but that should not have affected it; hence my logic was it was a name-mapped issue. I do not think the below should have ever been the issue but it has been working fine so far. Cautious & hopt that my tyre is fixed CJ's analogy.

 

[dalski]

Well you were completely right on a very badly explained problem so many thanks.