Hi Mark, many thanks for response in regards to my question. The way the system will work is that we send an update to the client, they are than able to upload this xml file using the application, the application then applies the updates contaied within the file. We really want to be able to move away from shipping files with multiple versions, as we want the updater to be completly version independent. The reason we have chosen XML initially is that we can compare old xml to new xml file to genreate the necessary insert, updates and deletes. Plus if there are new columns it just means tewaking the sql that outputs the xml. Where as to do it by an object model, any methods/fucntions have to be all updated to cope with new columns/tables and any calls to those methods/functions must be updated. This would be laborious, unless there was a method to do it dynamically. The reason we are looking at an object model is that all our programming in the system uses this and we would like to replicate that for ease of use, but I do understand that XML is the most appropriate method. Thanks again Paul