[Bort]

I have an application which takes input on a local machine and sends it to a database stored on a server. I'd like to be able to deploy my application over a number of computers (all on the same network), all of them updating the same database (on the network server).

First of all, will this be possible without putting together a completely new application to handle all connections to the database and sorting the entries?

If not, how would I go about doing this?

I have a sneaky suspicion that the concurrency errors from this one are not going to be friendly...

I'm not after all the code or anything, just a point in the right direction

Thanks,
Bort

[modi123_1]

Yes it is entirely possible. If you have the db server set up then your program needs the right connection string to the server and bam-o.

Our apps usually deal with 2k-5k users a day.

[Bort]

I have a database file stored in shared folders on a server. My program has the correct connection string to connect to it and update it, but won't simply putting my application on multiple PCs will cause concurrency violations?

[baavgai]

Bort, on 19 Feb, 2009 - 10:50 AM, said:

I have a database file stored in shared folders on a server....

Sorry, this does not sound like a database...

If the "file" is Access it's time to reconsider your options. If the file is something like one of those MDE thingies Visual Studio embeds, you're probably fine a web app is a single point of entry. If it's just a file you open up on a share then you could be in trouble.

[modi123_1]

Also I am going to throw this out there - MS SQL express is free and supports a large database.

Baavgai is right.. if this "file" is Access you will have to punt it and get a real DB. MSSQL.. MYSQL... postgre.. something else.

Concurrency issues in what way? as in having twenty people accessing the same piece of data? If that's the case just build a "locking" system that locks that chunk of data from any other user access.

[Bort]

It is an Access database, although I have no problems with changing that to a SQL database instead. Only reason I used Access is because I know how to use Access and have never created a SQL database before.

Concurrency errors as in having 20 people trying to update the same database at the same time, not accessing data.

[Bort]

Can anyone provide me with a download link for SQL Server 2008 Express please?

The one from the Microsoft VS 2008 website is corrupt.

Edit:

Never mind. I found a different Microsoft site where the download seems to be working.

This post has been edited by Bort: 24 February 2009 - 07:27 AM

[DeCompile]

Now this is entirely person opinion and determined by the users of your database.

Personally, we use web apps. Only because there has never been a standard hardware configuration across the multitude of departments that use these applications.

With web apps, there is no installation, no dependancy issues. It's just open a web browser and away you go. Works the same for Apple, Linux, FreeBSD (some users never let go) and even Windoze.

That's my 2c.