Access application shared by multiple users

[VAer]

Correct me if I am wrong. I would like to know how it works. I would greatly appreciate if you can read the detailed post. I am trying to explain my questions as clearly as possible.


Access, by default, is a multi-user platform. Is it correct?


I have a login form which will ask user to provide username/password (when user opens the Access file).


I have only one table inside Access (three fields: Computer_name, Username, Password). All other tables are in the back end Sybase database, those tables are already linked to Access manually. Let us say, when I build the application, I manually link the Sybase tables but did not save my password in the Access file. That being said, the program needs to use user provided Username/Password to re-connect the linked table. Since it is multiple user platform, if Mike is the first person opening the file (log in), program use his Username/Password to re-connect all linked tables, how to write the code? I only know below code to link a new table, which is not exactly what I need. I think if I don't save my password there(I use my Username/Password to link the back end tables, then close the Access file), the linked table should lost connection. Whoever opens the file next time, the program will need his/her Username/Password to re-connect to back-end Sybase tables. I have verified that: when I use below code the link Sybase table to Access, then close and save the file, when I re-open the Access file, if I try to open the linked table, a window pop up for my Logon ID/Password. In this case, how to write the code to pass user's Username/Password to re-connect the linked table? The other way to go around it: I realize if I use acLink to link one un-needed table, then all the previously-linked tables are re-connected(as long as all other tables are from same Sybase database), then I go ahead and delete the un-needed table. It seems working, but the method is silly.

If Mike is the first person opening the file, the program uses his Username/Password to re-connect to Sybase back end tables. A moment later, Jennifer opens the same Access file, while Mike is still opening the file. Since the back-end tables are already connected via Mike's Username/Password. At the time point when Jennifer opens the file, does she open the file (saved by developer without password for linked table) or open the file already linked by Mike? Does the Access application needs to use Jennifer's Username/Password in order for her to run some programs(interacting with Sybase) in the Access application.

I am not sure if I make my questions clear. Let me know if you have any questions regarding my questions.



Thanks.

DoCmd.TransferDatabase acLink, "ODBC Database", _
"ODBC;DSN=DataSource1;UID=User2;PWD=www;LANGUAGE=us_english;" _
& "DATABASE=pubs", acTable, "Source Table Name", "HelloWorld", False, True

[ranman256]

You do not let people use the same access file.
for multi-user, EVERY person gets a copy of the access front end.
i have all user front ends in their network folders so I can distribute updates with the click of a button.
(a table of users and their folder paths)

thought: why not Just connect the external tables WITH password saved, and just password the access Frontend?
no code needed.

[VAer]

You do not let people use the same access file.
for multi-user, EVERY person gets a copy of the access front end.
i have all user front ends in their network folders so I can distribute updates with the click of a button.
(a table of users and their folder paths)

thought: why not Just connect the external tables WITH password saved, and just password the access Frontend?
no code needed.

Password will expire and need to a new password every a period of time.

How to distribute updates with the click of a button?

[CJ_London]

Access, by default, is a multi-user platform. Is it correct?

to expand on Ranmans response.

As explained in your other post, access provides a front end developer environment to create applications with forms/reports etc to run in an ms office environment. In that sense it creates what you want. If designing to be used by multiple users there will be things to consider to handle multiple users - such as logins, tracking user activity, granting of read/write rights etc. If you don't put those processes in, multiple users can use it, but you have no control. As with any application, each user must have their own copy (aka excel, word, IE, etc). With Excel, for example each user has their own copy of the excel app but the excel file contains the data - and in excel only one user can open, make changes and save at a time, so by that definition, it is single user - but multiple users can still use Excel, just not the same file at the same time.

The Excel equivalent of the excel file is the database - either the free database that comes with Access (ACE) or in your case Sybase, both of which are multi user by default.