Multi user Application

[shers]

Hi,

I have finished coding a VB.Net application that has connection to SQL Express 2008 database. My question is, what steps do I have to take to make this a multi user application.

FYI:
There are 3 tables in the database of which two tables contain data to be viewed by the user and one table is to insert records by the user. The former two tables will be edited by the administrator only. So there is no issue of concurrency. But the one table that is used to insert records by all users has to be dealt with. Please give me suggessions as to how I should go about it.

Thanks

 

[picoflop]

idea:
http://www.vbdotnetforums.com/datab...423-problem-data-synchronicity.html#post95761

Though usually there shouldn't be a problem if records are only inserted. If you need a unique key on creation, you either use a database feature (most dbs should have a kind of autoincrementing value) or (if that is not possible/wanted) you create a key that depends on the current users id.

 

[cjard]

Hi,

I have finished coding a VB.Net application that has connection to SQL Express 2008 database. My question is, what steps do I have to take to make this a multi user application.

Make your SQLSX remote connectable and modify the connection strings on the the other machines to point to the SQLSx instance. If no user is updating or deleting data then the only insert concurrency issue you may encounter is a PK clash if you are calculating a primary key in a daft way (like select max(id)+1)

 

[shers]

idea:
If you need a unique key on creation, you either use a database feature (most dbs should have a kind of autoincrementing value) or (if that is not possible/wanted) you create a key that depends on the current users id.

Is there any advantage in using a unique key on creation? Anyways, I've already added a unique autoincrementing unique key.

Make your SQLSX remote connectable and modify the connection strings on the the other machines to point to the SQLSx instance. If no user is updating or deleting data then the only insert concurrency issue you may encounter is a PK clash if you are calculating a primary key in a daft way (like select max(id)+1)

What is SQLSX? If modifying the connection string on each client machine is what you meant, it would be tedious as there are around 150 users. All users are only inserting data, so there is no question of updating or deleting data except the administrator. Also there is no calculation of primary keys too.

Thanks

 

[picoflop]

Is there any advantage in using a unique key on creation?

It depends
I usually work with mobile devices that are most times offline. To make synching easier, I usually need to create a unique key without knowing what keys are generated on other devices. So I usually integrate device id, user id or something like that in record ids.

 

[cjard]

What is SQLSX?
If modifying the connection string on each client machine is what you meant, it would be tedious as there are around 150 users.

SQLServer Express.

Get someone else to do it then