Single Access Database, Multiple users, in a Terminal Server Environment

[rjcmi]

I am attempting to design/implement a terminal server at a non-profit
center. They will be using a Terminal Server environment in Windows
2003. The center has an Access 2003 database which many users will
utilize and update. I am wondering if anyone can give me good
suggestions or direction on how to implement this one database. It's
designed to have one central database then a .Net exe file connects
the users to the database for entry/queries. It is designed for multi-
users and according to the developers has been used in a Terminal
Server environment.

I currently have a working test server up and operational to try out
various ideas.

Thanks for any help or insight you can provide

 

[Eric Blitzer]

Check out Tony's site - he has a section on Terminal Server and Access.

http://www.granite.ab.ca/access/terminalserver.htm

 

[Albert D. Kallal]

There is not much to add here.

The only thing to keep in mind:

For any multi-user access application, you split the database.

Even when using terminal server, then EACH user gets their OWN front end
when they log on.

If not clear that by you mentioned .net that you just using a mdb as a file
share, or you actually have a ms-access application.

If the front end part is written in .net, then the above split issue will
not apply...

 

[rjcmi]

There is not much to add here.

The only thing to keep in mind:

For any multi-user access application, you split the database.

Even when using terminal server, then EACH user gets their OWN front end
when they log on.

If not clear that by you mentioned .net that you just using a mdb as a file
share, or you actually have a ms-access application.

If the front end part is written in .net, then the above split issue will
not apply...

Thanks to everyone for the help !

I'll check out the link and keep the other things you spoke about in
mind.

 

[Norman Yuan]

If you are to make a .NET exe application to entre/query data in the
database file (*.mdb), then it has almost nothing to do with MS Access. You
may post in various .NET NGs.