Looking for pointers with a multi user db

[Niels Jensen]

I'm developing an application which will sit on a Citrix server and users
will run it from there. Now as far as I can make out citrix starts a new
process every time an .EXE is run, however as I'll be connecting to an Access
DB do I need to watch for any issues regarding the possible conflict of
records in a multiple user environment?

One problem I can think of is that someone will add a new record to the DB,
however nobody else using the app will see the record as they'll be working
with their own datasets. I can fix this with a "Refresh Records" button, but
it would be nice to do this on the fly whenever the DB is changed. Is there
a way?

I should also point out that I'm still new to VB (Have been doing it around
9-5 for the last 2 months or so) having only developed 1 other application.
(Just in case I start getting #really# technical jargon being thrown my way
:) )

Cheers
Niels

[Chris Podmore]

Niels,

I wouldn't use access for a multi-user database. Have a look at MSDE or SQL
Server 2005 Express.

Chris.

http://www.microsoft.com/downloads/d...displaylang=en

http://lab.msdn.microsoft.com/express/sql/
"Niels Jensen" wrote:

I'm developing an application which will sit on a Citrix server and users
will run it from there. Now as far as I can make out citrix starts a new
process every time an .EXE is run, however as I'll be connecting to an Access
DB do I need to watch for any issues regarding the possible conflict of
records in a multiple user environment?

One problem I can think of is that someone will add a new record to the DB,
however nobody else using the app will see the record as they'll be working
with their own datasets. I can fix this with a "Refresh Records" button, but
it would be nice to do this on the fly whenever the DB is changed. Is there
a way?

I should also point out that I'm still new to VB (Have been doing it around
9-5 for the last 2 months or so) having only developed 1 other application.
(Just in case I start getting #really# technical jargon being thrown my way
:) )

Cheers
Niels

[Cor Ligthert]

Niels,

The dataset approach is a disconnected approach with normally optimistic
concurrency.

What means that is expected that the situation as you tells seldom occurs.

Some people say that you should arrange your data arround persons and with
that avoid concurrency problems, however I do not believe that that is
forever possible and think that it will bring unwanted dessign.

However it is (normally) optimistic concurrency so you have, when you
update, to check if there was no concurrency vialation when you have a
multiuser approach.

And than you have to choise which method fits you the best to solve that.

Here some of the pages about that.

http://msdn.microsoft.com/library/de...oncurrency.asp

I hope this helps?

Cor

"Niels Jensen" <Ni*********@discussions.microsoft.com>

I'm developing an application which will sit on a Citrix server and users
will run it from there. Now as far as I can make out citrix starts a new
process every time an .EXE is run, however as I'll be connecting to an
Access
DB do I need to watch for any issues regarding the possible conflict of
records in a multiple user environment?

One problem I can think of is that someone will add a new record to the
DB,
however nobody else using the app will see the record as they'll be
working
with their own datasets. I can fix this with a "Refresh Records" button,
but
it would be nice to do this on the fly whenever the DB is changed. Is
there
a way?

I should also point out that I'm still new to VB (Have been doing it
around
9-5 for the last 2 months or so) having only developed 1 other
application.
(Just in case I start getting #really# technical jargon being thrown my
way
:) )

Cheers
Niels

[Niels Jensen]

Thanks for the replies guys - this gives me something to chew over at least.

Niels

"Cor Ligthert" wrote:

Niels,

The dataset approach is a disconnected approach with normally optimistic
concurrency.

What means that is expected that the situation as you tells seldom occurs.

Some people say that you should arrange your data arround persons and with
that avoid concurrency problems, however I do not believe that that is
forever possible and think that it will bring unwanted dessign.

However it is (normally) optimistic concurrency so you have, when you
update, to check if there was no concurrency vialation when you have a
multiuser approach.

And than you have to choise which method fits you the best to solve that.

Here some of the pages about that.

http://msdn.microsoft.com/library/de...oncurrency.asp

I hope this helps?

Cor

"Niels Jensen" <Ni*********@discussions.microsoft.com>

I'm developing an application which will sit on a Citrix server and users
will run it from there. Now as far as I can make out citrix starts a new
process every time an .EXE is run, however as I'll be connecting to an
Access
DB do I need to watch for any issues regarding the possible conflict of
records in a multiple user environment?

One problem I can think of is that someone will add a new record to the
DB,
however nobody else using the app will see the record as they'll be
working
with their own datasets. I can fix this with a "Refresh Records" button,
but
it would be nice to do this on the fly whenever the DB is changed. Is
there
a way?

I should also point out that I'm still new to VB (Have been doing it
around
9-5 for the last 2 months or so) having only developed 1 other
application.
(Just in case I start getting #really# technical jargon being thrown my
way
:) )

Cheers
Niels