dance studio db

We have recently had a Access DB updated for us ,but did not end up with the product we were hoping for , We are a dance studio with over six hundred students and we require to have the capability to schedule our recitals by several unique parameters. We need to create five unique performances ( blocks) encompassing (on average) about one hundred and thirty dances in total, each performance block being approximately 60 dances and each dance needs to be performed two times within the five performance blocks, a few three times. In the creation of these dance blocks, several conflicts need to be identified: 1 -Three dances in between performances 2 - Siblings to dance in same show 3 - Young kids to be scheduled early 4 - Variety in sequencing My vision: to start with a complete list of dances, from there a dance would be selected and slid into one of the five dance blocks (each dance block represents a unique performance), as other dances are slid over to the various dance blocks that is where the conflicts would be identified and either the dance would be removed from the dance block or a change in sequencing within that dance block would need to occur. The system needs to track if a dance has been selected, and if so how many times, as the dance blocks are being created. There is a lot of selecting and deselecting during the process of moving the various dances around so its very important to have as much of the data visible, and since the dance blocks are being created simultaneously, moving between dance blocks is also imperative, must contain “user friendly interface “ The way the DB is designed now, you have to select a blank dance, move it to a dance block, and then populate that dance with the dancers….. absolute shit , there are no checks and balances, there is no way of knowing if you have captured all the dancers from a particular dance, and if you want to move a dance from one block to another , you have to repopulate the dance one dancer at a time.... there is no way to achieve our objective with the design that is outlined in the attachment. There might be some debugging necessary as the db has not really been put through its paces, communication wasn't what it should be and we were not presented with updates, only the finished product and then every issue we had was being treated as a add on to the scope of the project, so after much frustration we decided to cut our loses and try a different avenue to get to what we need. I am looking forward to working with someone who can bring this project to the next level, thanks for looking