I have been running a number of tests for everything that uses MasterBaseQuery(). Not all 100 plus of them, but 4 or 5 of them. The only erroneous return is from the same function discussed here. At this point I just don't see what/why it is going calling for colSet1 instead of colFilePath, as called in the function.

Here is the call line again.

Code:
MasterBase.MasterBaseQuery("SELECT colFilePath FROM defMasterBase WHERE colName = '" & MyApp & "'")
When it executes it goes directly to MasterBaseQuery(), as expected. However, here is what the ListCommand looks like when it is called.

Name: ScreenShot.jpg Views: 1326 Size: 9.4 KB

As can be seen, instead of colFilePath being called, colSet1 is called. I cannot see any reason why this would occur.

This is just about the extent of my understanding of the debugging process. There is no other database to check, and while there is a table that is similar to the one used for this, it has neither of the columns that show up in the MasterBaseQuery(). I heard mention of, "Stepping into the Library method." . Do I even want to know what the hell that is? It sounds like an opportunity for me to dig a deeper hole than I am already in.

I am willing to learn but can this be resolved if I just replace the staffRecord.vb form (design/code) with a new staffRecord.vb with a new design/code? Of all the calls to MasterBaseQuery() that I have checked, this is the only one that calls out the wrong column.