backend version control?

[CarlRostron]

Help needed please on a split database (front and back end). I have completed the split and have deployed the backend to SharePoint. The front end is sat on my (and others) machines with linked tables to the SharePoint lists. This is all fine and works well.

However this is where I need help. Although this database is deployed, I am constantly working on a local copy of the database in design I.e. Tables being updated with fields and relationships and new tables being added. The reason for this is that work wanted something workable putting out there now and that I just continue its development in the background.

What is the best way to update the tables on SharePoint bearing in mind that users are putting new data on there? I don't want to lose what they are updating and then I need to redploy the 'new' backend to SharePoint again (no doubt in the same location) as that's where the front end is looking for it.

I hope this makes sense and I look forward to some guidance on how I can manage this version control of the backend without losing data.

 

[DJkarl]

Well you can append all the data from the production copy to your local copy then push your copy and overwrite the one on sharepoint. Aside from that there really isn't a great way to do version control and preserve data. Ideally a back end shouldn't be changed once it goes to production, I understand it wasn't your call in this case.

 

[CarlRostron]

Yes far from ideal but I appreciate your words.