Accessing an MS SQL database

[davidc2]

I have a database in SQL and I need clients to connect to it but they don't have Internet access.. I mean, they'll have Internet access from time to time, but not all the time.

They are going to be entering products into the system and they need to see if the product meets certain conditions specified on the database...

how can I create a version of it on the client's computer?

Would I need accesss or something like that?

[ess]

You can create a replicate of the remote database on user's local machines.

Personally, I would use XML files. Basically, when the user connects to the internet, a connection to the remote server is established, and sync in an XML format is saved locally on user's machines.

If a user updated records on whilst offline, these changes will be flagged and once connected to the internet, you can apply those changes.

It is not going to be an easy ride, but I think you are better off using XML files.

[Aradon]

I'm actually about to start a project with this same issue and had thought about several different ways in which I would want to make my system local as well as portable.

I had debated using light MySQL on both the local and remote machine, syncing up the two databases when an internet connection is present, however an XML idea may prove to be much less of a hassle.

I've already got what I want in mind, now I just have to write it all down and start implementing it.

[davidc2]

I'm actually about to start a project with this same issue and had thought about several different ways in which I would want to make my system local as well as portable.

I had debated using light MySQL on both the local and remote machine, syncing up the two databases when an internet connection is present, however an XML idea may prove to be much less of a hassle.

I've already got what I want in mind, now I just have to write it all down and start implementing it.

Can you point me in the right direction and give me some tips on where to start and what to use?

I like the XML idea. The thing is that the database is kind of big.

[Lallo]

Can you point me in the right direction and give me some tips on where to start and what to use?

I like the XML idea. The thing is that the database is kind of big.

You will use IP in the connection to the database and it will be available locally. If you want to be accessible over the internet again you will have the same connection but with different IP - the internet IP of the "server" machine. Remember that if you use a pc as server machine (machine with the database) you will need fixed IP in order to be accessible all the time.

Few words about XML.............
I WOULD PREFFER DATABASE!

[davidc2]

You will use IP in the connection to the database and it will be available locally. If you want to be accessible over the internet again you will have the same connection but with different IP - the internet IP of the "server" machine. Remember that if you use a pc as server machine (machine with the database) you will need fixed IP in order to be accessible all the time.

Few words about XML.............
I WOULD PREFFER DATABASE!

Provably using a database would be better but since the computers on which the system is going to be installed are spread out it would provably make the installation more complicated for users...

Besides I need to learn XML sometime, what better opportunity? :)

[davidc2]

On second thought, the database is already there and it is quite big, so provably making XML files would be too much work.. provably the best thing would in fact be to make a copy of the database to a mini-version of it...

I'll do some research on how to copy data from SQL Server to MySQL or SQL Server Express... that might work.