mreed
Member
- Joined
- Dec 1, 2009
- Messages
- 5
- Programming Experience
- Beginner
First off, let me say Hi. I'm new to this forum and I would like to thank you in advance for any suggestions or comments.
Here is what I'm looking for:
I have created a Payroll Management application in vbexpress2008. It is my very first vb project and I've spent a lot of time and effort on it. It's not perfect, but it works. It connects to an access (2003).mdb database. The problem I had in designing this database was that multiple users needed to access the data.
So what I did was place the database on a server and the local users hard drive. did work and make changes to the local copy, have the program check the attributes of both files and display them to the user and have the user select whether they want to update the local or remote copies.
This works great when their were only 2 users...
Now I have another issue, I need to have this program distributed to 9 other people, so now I've got 11 users and the possibility of 2 or more of them trying to update the database at the same time just compounded on me.
sharepoint server was suggested (but I'm not familiar with programming with sharepoint, plus it's out of our cost range)
I'm looking for ideas/suggestions on how I can overcome this problem.
All of the users have access to the server and my first thought was to create a separate database for each user and then somehow, merge that into 1 database that is accessed by the first 2 people (the big shots)
Here is what I'm looking for:
I have created a Payroll Management application in vbexpress2008. It is my very first vb project and I've spent a lot of time and effort on it. It's not perfect, but it works. It connects to an access (2003).mdb database. The problem I had in designing this database was that multiple users needed to access the data.
So what I did was place the database on a server and the local users hard drive. did work and make changes to the local copy, have the program check the attributes of both files and display them to the user and have the user select whether they want to update the local or remote copies.
This works great when their were only 2 users...
Now I have another issue, I need to have this program distributed to 9 other people, so now I've got 11 users and the possibility of 2 or more of them trying to update the database at the same time just compounded on me.
sharepoint server was suggested (but I'm not familiar with programming with sharepoint, plus it's out of our cost range)
I'm looking for ideas/suggestions on how I can overcome this problem.
All of the users have access to the server and my first thought was to create a separate database for each user and then somehow, merge that into 1 database that is accessed by the first 2 people (the big shots)