"is there a better suggestion out there for what I'm trying to do, besides
making 3 tables, one to hold mob_index_data with a primary key of vnum, one
for mprog_data with a primary key of vnum, and one to hold
mob_mprog_associations with foreign keys for both vnums, for this scenario?
Do I even have that straight in my head?  Any help would be appreciated :D"


This solution is the "proper" way to do it.  With your proposed 3 table
system you will end up with properly normalized tables.  I'd say it's the
best bet...

Cameron 

Reply via email to