>Yes, I understood that ... and I assume the code you posted is in the oProcess object. But, I must apologize for my stupid question; I had been thinking that the LoadDataDictionary() method was in oApp & it's not. So, forget that question ... unless that method is loading up a DataDictionary that's part of oApp? You haven't really said where this DataDictionary is.
>
>Maybe what you really should be checking is the DataDictionary itself? I typically use code like this (similar to what Viv posted). I've seen it referred to as the "double-check locking pattern":
>
>

>If MyDataDictionary Is Nothing Then
>    SyncLock LockDictionaryObject
>        If MyDataDictionary Is Nothing Then
>            If Not LoadDataDictionary() Then
>                Return False
>            End If
>            ' Do other stuff
>        End If
>    End SyncLock
>End If	
>

The LoadDataDictionary() is initiated from a hit to the Web site. But, that method, makes some calls to the oApp.Tables collection object to load the data dictionary into. So, that's why I figured out that I should apply a lock at the Web site level (the hit in progress, for the first one that gets into the app). Then, even if LoadDataDictonary() is executed some calls to oApp.Tables collection related loading issues, this shouldn't be a factor as the lock should be already in place.

But, I will check it out more tomorrow.

Thanks