certainly such things can occur. But as use in 0 without a select afterwards is used, for me Occam shaves your perfectly valid point until correct alias is proved SOMEWHERE in the code ;-))

>try
>

>USE bookings IN (SELECT("Bookings")) ALIAS muh
>USE bookings IN (SELECT("Bookings")) EXCLUSIVE
>*boom
>

>
>even better
>

>USE bookings IN (SELECT("Bookings")) 
>USE bookings IN (SELECT("Bookings")) AGAIN ALIAS muh
>USE bookings IN (SELECT("Bookings")) EXCLUSIVE
>*boom
>

>
>we do not talk datasessions and concurent use
>
>and, for your example
>

>SELECT SELECT("Bookings")
>USE bookings EXCLUSIVE
>

>
>will work with SELECT before USE. Even five char smaller code
>
>[gdr]
>
>>I am sure this must have been pointed out already. But, try placing a SELECT Bookings after the USE statement. If there is a table already in the current work area, then the Booking table will be opened in the next unused work area.
>>
>>Also, as a standard practice, I generally use the statement
>>

>>USE bookings IN (SELECT("Bookings")) EXCLUSIVE
>>SELECT Bookings
>>

>>So if the table is already open in another work area, then it will be reopened in the same work area.
>>
>>
>>
>>>

>>>SET SAFETY OFF
>>>SET EXCLUSIVE on
>>>USE bookings IN 0 EXCLUSIVE &&I have tried it with and without the exclusive clause. Makes no difference.
>>>DELETE ALL
>>>PACK
>>>IF ISEXCLUSIVE( ) &&Just to check if there is exclusivity. returns .f. each time - no matter what I change around in the code.
>>> MESSAGEBOX('Table opened exclusive')
>>>ELSE
>>>  MESSAGEBOX('Not opened exclusively')
>>>ENDIF
>>>SET EXCLUSIVE OFF
>>>SET SAFETY ON
>>>