Client/Server Architecture

a_20120

tan
Local time
Today, 23:55
Joined
Nov 21, 2006
Messages
175
Hello EveryOne,
I have a mdb File, which includes around 50 users with different Access Level, and want to make it Client/Server architecture. What I mean want to put the Db in the Server and the Clients can access that maybe simultanously

How can I do that? What Tools (Like ODBC, MSDE) is needed? Please help me with this
 
Help !!!

Hello EveryOne,
I have same as above Problem..................
If any one done Client/Server architecture with M.S Access mdb file, please guide and help me through that. because I did not do client/server upto now
Really appreciated your help...
 
Last edited:
Hello All Guys...
Why no one helping and guiding today? what happaning? Plz any one who had the same problem and issue help me....
 
Search the forum for Split Database and FrontEnd and BackEnd. These should explain how to setup a multiuser db. Are your users most entering data or using the db to research data?
 
WARNING:

As described, putting the database on a server and letting users access it from their workstations is TECHNICALLY NOT client/server architecture.

This is client/server as in FILE SERVER client/server. BUT NOT database client/server.

In the sense of ODBC, Access is more often the CLIENT than the SERVER. In fact, I've never personally seen Access set up as the server side of the equation. You use SQL Server or ORACLE or some other product for that. Then Access can be the client side of an ODBC connection.

When you put a .MDB file on a server and let users connect to it, they must first have a local copy of Access. After that point, you can grant users permission to work with the (now shared) files on the file server.

You do NOT need anything but the file on the file server and local copies of Access to make this work correctly. HOWEVER, to optimize performance and assure data security, you need to search this forum to see topics such as

Split Database
Front End/Back End (and variants such as Front-End/Back-End, FE/BE)
Workgroup Security
Securing a Database
Windows Security

One more issue, and this is a minor tweak - your first post was at a very early time and you "bumped" the thread only 80 minutes later. Please allow for time zone differences. Patience is a virtue here. You got a response 4 hours later, which for this forum is not really that bad. Many posts go without a response for two or three days.
 
I prefer to use Access as a front end and link all the table through ODBC connections to a SQL server back-end. (SQL server 2000) is the easiest in my book. The link process is just like linking a text file to access just a few more parameters required to get through the Server security. As for power and storage potential, SQL server rocks!!!
 
IMHO - the best solution is MySQL on the be

good luck
 
Thanks every body,
I made the the Project in Access(mdb), then I converted it to 2003, then I created the BE and FE, and converted the FE into (mde)...
Now Could u plz give me more detail how to use SQL2000 or MSDE and ODBC?
 

Users who are viewing this thread

Back
Top Bottom