>>I still think this is virtualization. Have you looked to see if the file also exists in the Users hierarchy?
>>
>
>I can't figure out if the computer is using virtualizaiton. And I don't understand how to check if the file exists in the User hierarchy.

Virtualizaton would limit the file access to the local PC. The remote PC should not be able to access the virtualized file at all. The store location for virtualization is under the path

C:\Users\{user id}\AppData\Local\VirtualStore\Program Files (x86)\{program directory name}

Access to this is controlled by the user id that is logged into the local PC. The virtualization occurs since programs are not allowed to write to the "real" program directory location. So on a network it does not seem that a remote PC should be able to access this.

I would go back to the USE ... EXCLUSIVE and do some more testing. If you un-use (USE IN alias) the table on the first PC, can the second PC then access exclusively? (If it still fails, then these are two separate tables.) If the second PC can use exclusively, then can the first PC also use exclusively at the same time? Possibly the second PC is not accessing the same table still?

If the second cannot USE EXCLUSIVE at all, then some other process is locking the table. But the fact that the first PC can USE EXCLUSIVE means that it is different. Now in this case the virtualization may be occurring; but this typically only occurs when you are trying to write to files under the "Program Files" directory or "Windows" directories. Verify that the path is actually the network share and not actually mapped somewhere else.