I’ll look into that…
I will not need keys to match up, however…
The problem is that there are slots on different casinos with the same name. Since the database was originally set up with the slotname as the primary key – this poses a problem (unless, of course, I prefix the slotname or something similar.)
So, I want the Casino ID AND slotname tied together as one key so that I do not have a problem. Know what I mean.
I may just re-structure the whole stupid database 
Might be the best way out of this.
Thanks.
*Edit* I think it is about time for kwblueDB V2.1 