Good Morning SO!

We've been scratching our heads with with this interesting scenario at the office, and we're anxious to hear your ideas and approaches:

1. We have a database, whose schema is prone to changes -lets call it Prony-. (is used to store configuration parameters for embedded devices. so if the embedded devices guy need a new table, property or relationship for the model, he should be able to adapt the schema in a easy way -happens so often- ).

2. Prony needs a web interface to create/edit its data.

3. We have another database containing data that also need to be loaded to the devices, after making some transformations - lets call this one Oddy- (this data it's generated by an already existent administrative web application).

4. Finally we have Tracy, a server that communicates our DBs and our embedded devices. She should to auto-adapt herself, to our dbs schema changes and serialize the data to the devices.

Nice puzzle, don't think so? : )

Our current candidates:

• Rady: The fast

  Lets create some views in Prony that make the data transformation from Oddy. then use DynamicData (or some RAD tool) to create/update a simple web interface for Prony (so he can even consult the transformated data from coming from Prony : ). About Tracy, she will need to be recompiled to update her DB schema (Entity framework should work) and use Reflection to explore recursively the schema and serialize data.

  Cons: We would have to recompile Tracy and the Prony's web interface.

What do you think of the candidate(s)?

What would you do?