Jason, could I ask why you thought to add the floor and ceiling approach to adding the data to the database? in your table structure of: weightfloor, weightceiling, amount. wouldnt I need another field to represent the delivery type?
also in the shipping rules am I right in thinging I will need to create a heavy long list of shipping rules to compare for every single combination of costs (as listed in the beginning of this thread) - so in other words roughtly I would need to create 36 individual shipping rules!! how would i represent the price amount from the database in the shipping rules box in ecart? (obviously I done simular in a previous project with using data from a database in the ecart shipping rules..but this one is a little different since each combination is stored as a record in the database.