Database development for SQL Server Compact and interoperability between several PC:s

I have done some database programing and am somewhat familiar with VB and creating Windows Forms applications...


What I now want to do is create a common library for several computers to use. This library (database) should be updated only by one user and other users could use the info that is stored in it. Also other uses should be able to inform the "updater" on which positions to update...

Was my explanation incoherent enough? :bigyello: :bigyello:



I'm thinking of using Windows Forms Applications with SQL Server Compact for easy installation for every user. At the moment I just don't know how to start working with the internet access between two different computers.


BASICS:
- One user is in charge of the information stored in the database library. He has his own user interface created in Windows Forms Application.
- Other users have the same library which they can update when needed. They have a different interface which is also a Windows Forms Application. (The library on other users' computers remains the same until they deside to update it...)
- Other users can inform the updater if some updates need to be made for certain positions. (Example: By selecting certain positions from the library and just clicking "Needs to be updated".)
- The connection between the computers and databases should work flawlesly, since some users

Below is a picture to try to try and clarify my jibber jabber...
:rolleyes:

Since SQL Server compact is for single use only I don't see how you can use this, unless of course you intend to update 1 db and then send to all other users.

Quote:

---

Originally Posted by GaryMazzone

Since SQL Server compact is for single use only I don't see how you can use this, unless of course you intend to update 1 db and then send to all other users.

---

Ok... I have no experience with server based or multiple user databases... Could you guide me through the first basics and give some good tips?
I'm trying to read some tutorials at the same time...

:afrog:

I would go with SQL Server Express 2008 R2 for the backend database.

Ok I guess you are going to send the db to each client so that is not a problem.. What will be is that the database will be out of sync between each other at different points in time. Is this supposed to be avaliable to all uses 24/7?

Quote:

---

Originally Posted by GaryMazzone

I would go with SQL Server Express 2008 R2 for the backend database.

Ok I guess you are going to send the db to each client so that is not a problem.. What will be is that the database will be out of sync between each other at different points in time. Is this supposed to be avaliable to all uses 24/7?

---

Thanks for the response.
In a way yes. I will be sending the db to each client. The out of sync -thing is not a problem. That is the way it should be. (Example. The DB manager ie. "host" computer is turned off for the week-end. The clients are still working on some projects and need to pick stuff out of the library. The have the last update available as 'offline' on their own computers..

But is the Express the way to go?


The idea is, that I will create a common library that is managed from a single seerver. This librarys updates are transfered to clients computers when needed. At other times the clients work with the "old"/previous version of the library...


How is this DB sending done? I've tried to figure it out and always navigated to wrong info sites... Any links or advices?



Thanks for your interest! :thumb: