yes, but you are using two locking techiques at the same time;

the synclock is threadsafe for any threads created during the request,
but not between two requests happening at the same time. this is becuas
the synclock is taken the instance of the request. at diffent request is
 locking a different object.

if lockkey is a privte shared, then monitor lock is threadsafe. not sure
why you assign a value to the lockkey inline as opposed to its constructor.

this assumes that this is the only code that calls the routine.

but you could just as easily use (if i know my vb syntax):

    private shared lockkey as string = ""

    synclock lockkey
        dosomething
    end synclock

-- bruce (sqlwork.com)