Access Database Limitations

[KFC]

Hi all,
Do you mind to advise if there are any concurrent sessions limitations on
one access database? Also, do you mind to advise how to call a form from
another access database? If yes, can updates/deletes be done successfully by
this kind of call? Would you please advise me how the codes can be written to
do the above mentioned functions? Thank you for your kindness.

 

[John Vinson]

Hi all,
Do you mind to advise if there are any concurrent sessions limitations on
one access database?

Nominally, 255. For read-only users you can probably get quite close
to that, certainly well over 100. For concurrently updating users, the
number will depend strongly on your network, the machines in use, and
especially on database design; I've seen problems with 20 and
perfectly satisfactory results with 60, just depending on the case.

Also, do you mind to advise how to call a form from
another access database? If yes, can updates/deletes be done successfully by
this kind of call? Would you please advise me how the codes can be written to
do the above mentioned functions? Thank you for your kindness.

Although it's possible to "call a form" from another database, you
ordinarily would not want or need to do so. Typically a multiuser
database would be "split" - the tables would be in one database shared
by all users, and each user would have their own "frontend", linked to
the tables and with its own Forms, Reports, Queries and other user
interface components. Some references might be handy:

http://www.granite.ab.ca/accsmstr.htm
http://www.mvps.org/access
http://home.bendbroadband.com/conradsystems/accessjunkie.html

and many additional links therein.

John W. Vinson[MVP]

 

[Arvin Meyer [MVP]]

Hi all,
Do you mind to advise if there are any concurrent sessions limitations on
one access database? Also, do you mind to advise how to call a form from
another access database? If yes, can updates/deletes be done successfully by
this kind of call? Would you please advise me how the codes can be written to
do the above mentioned functions? Thank you for your kindness.

I have 51 concurrent users without problems, but I have seen locking
problems with as few as 3 or 4. Much of the answer lies in the design and
use of the database.

To open a form in another database, you need to create a public function or
sub in a standard module in that database. Something like:

Public Sub OpenIt()
DoCmd.OpenForm "MyForm"
End Sub

In your second database, set a reference from any code window, to the first
database. Then call the code in the first sub:

Private Sub MyButton_Click()
OpenIt
End Sub

Doing this involves uses significantly more resources than copying the form
because 2 instances of Access will be open (1 in memory) so I only do this
when the form or report is complex and used by several different databases.
If it never will be updated, just import it, but if it is complex, and/or
updated frequently, you will save time and effort.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Pat Hartman\(MVP\)]

"Also, do you mind to advise how to call a form from
another access database?"

Forms don't store data. Tables store data. If you want data from another
database, link to the appropriate table. Do not open a form and attempt to
manipulate it via code. Linking to a table in a different database, allows
you to view/update the data from your database.