Hello All I am currently investigating changing a shared multi user Excel spreadsheet to a centralised Sharepoint document. I have, what I am sure is, a very simple and basic question however I am struggling to find the answer. At present the spreadsheet we use is to log rows of new data requests, one row per data request. Simple so far. However with multiple people working with the sheet there are issues of concurrent working/sharing, not to mention the lack of medium to long term scalability. Sharepoint will solve most of the issues. At present when creating new rows the team have to verbally check where everyone else is and if they have row X free on their current working copy to ensure that there is no conflict with two totally different data requests being logged in the same row. If there are two members of a team editing a simple row for the same data request this is fine as they can just resolve any conflicts as and when they arrive between data input for a single request. The concern that I am trying to avoid is when the row is being used for two separate data requests. I am presuming that the team can just hit refresh before and after they start to create a new row, therefore minimising the risk of using the same space, however the risk is still there if they start at the same time, or indeed forget to refresh. Does Sharepoint have the inbuilt functionality to counter this problem, maybe a simple automatic refresh as soon as a new row is populated? Many Thanks Mark

When you create a new item in SharePoint it is assigned an ID and no two items can have the same ID. If two users select the "new item" option and then "save" at the same exact time then SharePoint is simply going to create two new list items based on the order they were saved and give each row a unique ID. So if I am understanding your question correctly, yes SharePoint can handle this situation. If I misunderstood what you are asking, let us know. ~Jennifer Mason ~My Blog~ ~SharePoint Support~ ~SharePoint Training~ ~Follow me on Twitter!~