I have two sites in sharepoint 2003 and I need to do a regular (monthly) one way sync of the custom lists , (maybe 6) I am an administrator of both sites,- but do not have any special sharepoint priviledges beyond this I nned a client tool as I have no access to the servers. I have sharepoint designer 2007. Can this be used to do this task - or can anyone recommend something? A tool would be good thanks

Hi Wedny, I'm wondering if you could describe what you mean by 'sync' for the two lists on the two different sites. Are you looking to blend their contents somehow, to do a content deployment-like circumstance, or something else entirely? Do you have access to FrontPage 2003, a better tool overall for working with SharePoint 2003 sites? Thanks!

Hi Tracey When I mean sync I mean just copy over the lists from once site to another,The main lists will change from day to day - but I want to sync over these changes - say every month or so so that the 'subsect 'copy on my site has up to date data for me to manipulate and report on. The lists to main site - are always 'pending' - so I don't want to automatically sync all the time, Just take a snapshot and every so often copy the data over. It would be a one way sync only. Basically the initial dataset on the source site is about 20 lists joined by lookups to form a relational type database. I only need about 4 of the lists - but they have about a thousand rows each - I thought of using excel (2003) as a centre point - but it seems a bit messy. I downloaded Data Sychronisation Studio - and it seems to do exactly what I want in theory - but just doesn't seem to connect to our sharepoint site in practice I have front page 2003 and designer 2007

Hi Wedny! I’ve done some digging into this, and I’m afraid 2003 functionality is not quite as far along as the SharePoint 2007 functionality, which includes options like content deployment. For 2003, with a 1-way trip for the data, we can consider the following (this is based on the scenario that only List 1 is getting updated dynamically): 1) We can do the Excel export-import option you’d mentioned in your response. Depending on the list, this may go smoothly or involve a little manual tweaking along the way. 2) We could make a template backup of the original list with content (up to 10 megs for V2). Move this template over and create a new list based on the template in the new site. Warning: Issues list will not be able to do this! Additionally, you would have to delete/recreate the list every month, there would be no ‘overwrite’ option for this. 3) There doesn’t seem to be a ready way to ‘sync’ content with FP 2003, we have the ability to move some of the pages and such behind the scenes, but nothing quite as granular as you’re looking for. 4) A third-party tool or custom element may be able to do this, but it may not be supported depending on its method (example: direct SQL modification is not supported). In that light, I can’t advise you on how to get Data Sychronisation Studio to work, as I don’t know what its underlying functionality might be. If it’s utilizing 2007’s content deployment behind the scenes, we wouldn’t have that as an option in 2003. You may want to check with their company to see if that’s the case! Thanks!

Tracey - that's for your comprehensive reply, I really appreciate it. Can a template include data? We are moving onto 2007 eventually - so unfortunately it may have to be the spreadsheet approach until then!

A template in V2 can hold up to 10 megs of data, which may or may not help you depending on list size, of course. You can check that information out in Central Administration, under Site Collection Administration -> View Storage space Allocation. I've also found this link that contains a good overview of gotchas for both spreadsheet and list template methods! http://office.microsoft.com/en-us/windows-sharepoint-services-help/copying-or-moving-sharepoint-lists-HA001154562.aspx I hope this has been helpful; thank-you! Tracy

thank you very much - excellent support.