Thanks for your suggestion. I take it that your suggestion is related to the database restructuring.

i'd create an abstraction layer using an ORM like Rose::DB::Object ( i usally hate them, but in this case, i think it makes sense ) to map new objects onto the extisting database (and vice versa).

I have a good enough database abstraction layer. Do you mean I need to create another abstraction layer? Or I only need to make the layer to deal with two database models? I am more inclined to database refactoring when thinking about database restructuring.

I don't know about the scariest f'ing thing stuff. This is my first professional experience so I don't know any better. I just learn as I go, and perlmonks has been the one that helps me to get to this point. So this rewrite/refactoring is exciting, challenging, and scary at the same time.

Thanks