VS.Net Networking with Access Database

[punt]

At Uni last year we created a VS.NET application which connected to access
database on a single machine, with a full install program.
My question is does this system work well for a networked application, so
for example I would install the program on a couple of machines(only about
2-6) then they try to connect to a single access database on a server. Are
there any problems in doing this? Does the server need any extra files? Any
comments appreciated.

Punter

[Cor Ligthert]

Punt,

You would have to be able to use the access database on a network (assuming
the users have access to it).

However with multiuser you get the aspect of concurrency. "Did one user
already in the current time changed something in the database while another
was still updating it."

That is an item you should check and of course place the rigth procedures to
resolve the problems when that had happened.

When you are only reading your database and not updating, than this should
be of course not be a problem.

I hope this gives an idea?

Cor

[Bernie Yaeger]

Hi Punter,

As Cor said, concurrency can be an issue, but, frankly, a small issue. ADO
..net is connecting you in a disconnected state, using dataset/datatables;
so, the last one in makes the change. From a practical point, of view, I
have several such programs using 5 - 15 pc's, and I have no difficulties.

One other thing to be aware of - when you place the .mdb on the server, all
of the workstations have to have .net security modified to allow full
access. Go into control panel, performance and maintenance, administrative
tools; use the .net security wizard and give local intranet full access.

HTH,

Bernie Yaeger

"punt" <no****@no.com> wrote in message
news:39*************@individual.net...

At Uni last year we created a VS.NET application which connected to access
database on a single machine, with a full install program.
My question is does this system work well for a networked application, so
for example I would install the program on a couple of machines(only about
2-6) then they try to connect to a single access database on a server. Are
there any problems in doing this? Does the server need any extra files?
Any
comments appreciated.

Punter

[punt]

"Bernie Yaeger" <be*****@cherwellinc.com> wrote in message
news:ON**************@TK2MSFTNGP09.phx.gbl...

Hi Punter,

As Cor said, concurrency can be an issue, but, frankly, a small issue. ADO .net is connecting you in a disconnected state, using dataset/datatables;
so, the last one in makes the change. From a practical point, of view, I
have several such programs using 5 - 15 pc's, and I have no difficulties.

One other thing to be aware of - when you place the .mdb on the server, all of the workstations have to have .net security modified to allow full
access. Go into control panel, performance and maintenance, administrative tools; use the .net security wizard and give local intranet full access.

HTH,

Bernie Yaeger
Thanks for the help...Just gotta test it now.

Matt

"punt" <no****@no.com> wrote in message
news:39*************@individual.net...

At Uni last year we created a VS.NET application which connected to access database on a single machine, with a full install program.
My question is does this system work well for a networked application, so for example I would install the program on a couple of machines(only about 2-6) then they try to connect to a single access database on a server. Are there any problems in doing this? Does the server need any extra files?
Any
comments appreciated.

Punter