This is a name space collision. You need to remove one of the libraries and revise all code that referenced it to either reference the kept library or to reference a new differently named library (even if it was the removed library just renamed).
This is what happens if people write code without a good structure. Vexorian being slightly egocentric (in a good way) and the author of vJASS thought that only 1 table system, his, would be sufficient for everyone to use which is why it was named "Table" (the Table library). People like Bribe invented other alternative "Table" libraries for various reasons (maybe they thought they could do it better, or maybe they just designed one for their own purposes) which were also publically released. The reality is that doing this caused a massive name space collision since the interfaces used are different between the two tables.
If anything you should replace Vexorian's Table with Bribe's Tabe since as far as I know he wrote his long after Vexorian lost interest in WC3. Hopefully he would have the same methods as Vexorian with extra methods added (interface extension) otherwise there is no other way than to modify code. This is why interfaces are important and need to be standardized, if they share similar interfaces Bribe's should easily replace Vexorian without any code modification.
Depending on implementation, one could modify either Bribe's or Vexorian's to add the missing methods, possibly in the form of adapters. This may or may not be easy to do. The other way is to modify the code referencing methods from the removed system (either Vexorian or Bribe Table) to reference methods in the system you have.
This would never have happened if Vexorian or Bribe named their libraries less laconic. For example Vexorian could have named his VTable (Vexorian Table) and Bribe named his BTable (Bribe Table). In that case both could have co-existed in the same map and never interfered with each other's name space and map makers like you would not have to deal with a name space collision error. This however brings other problems which is why standard interfaces are recommended.