ACCESS USERS

[Dindulis Rimantas]

Hello, Dears Access intusiast ;]

I.m have one database, but i dont known how can conect 2 ussers same
time and update in same time...

Thanks wery lot,

Rgds.

Rimas

[Oko]

Typically splitting a database between a front-end and a back-end will
allow two or more users to connect to the same database without issue.
Should you move to a larger environment - or just have time to enjoy
such an exercise - you may find you have to transition to the use of
unbound forms.

The front-end will contain the forms, reports, macros, queries, etc...
while the back-end contains all of the tables. The front-end - so as
to have access to the tables - is linked to the back-end. The front-
end is then installed on the user's computers - each user having their
own copy of the front-end which is then linked to the data.

When the users then log in to use the DB they should both then be able
to work simultaneously without issue.

Dindulis Rimantas wrote:

Hello, Dears Access intusiast ;]

I.m have one database, but i dont known how can conect 2 ussers same
time and update in same time...

Thanks wery lot,

Rgds.

Rimas

[Dindulis Rimantas]

O many thanks OKO.

Mabye you can explane about ADO server?

Rimas.
On 18 Sau, 01:18, Oko <[e-mail]:

Typically splitting a database between a front-end and a back-end will
allow two or more users to connect to the same database without issue.
Should you move to a larger environment - or just have time to enjoy
such an exercise - you may find you have to transition to the use of
unbound forms.

The front-end will contain the forms, reports, macros, queries, etc...
while the back-end contains all of the tables. The front-end - so as
to have access to the tables - is linked to the back-end. The front-
end is then installed on the user's computers - each user having their
own copy of the front-end which is then linked to the data.

When the users then log in to use the DB they should both then be able
to work simultaneously without issue.

Dindulis Rimantas wrote:

Hello, Dears Access intusiast ;]

I.m have one database, but i dont known how can conect 2 ussers same
time and update in same time...

Thanks wery lot,

Rgds.

Rimas- Slëpti cituojamà tekstà -

- Rodyti cituojamà tekstà -

[Larry Linson]

I doubt Oko can explain about "ADO server" because there is no such thing.
ADO, ActiveX Data Objects, is an _access method_ based on the OLEDB
technology. The classically-used DAO is the native language of the Jet
database engine, is (most think) simpler, easier-to-learn, faster in
operation, and easier-to-use with Jet (which is what you are talking
about)... there may be, in some cases, minor advantages to using ADO with a
true server database engine. Jet is, however, a file-server.

I suggest you visit http://office.microsoft.com and follow the links to the
free online training, as not knowing that Access is multi-user enabled right
out of the box, even unsplit*, indicates you need rather basic
training/education before proceeding.

* however, splitting, as Oko suggested, is _preferrable_ for a number of
reasons.

MVP Tony Toews' site http://www.granite.ab.ca/accsmstr.htm has a wealth of
information on using Access in a multiuser environment, and there's a list
of a few other of the better-known resource sites at
http://mail.ntpcug.org/accesssig/default.aspx. Those, or searching the
archives of this newsgroup at http://groups.google.com will lead you to many
more.

Good luck with your project.

Larry Linson
Microsoft Access MVP

"Dindulis Rimantas" <r.********@gmail.comwrote in message
news:d1**********************************@x69g2000 hsx.googlegroups.com...
O many thanks OKO.

Mabye you can explane about ADO server?

Rimas.
On 18 Sau, 01:18, Oko <[e-mail]:

Typically splitting a database between a front-end and a back-end will
allow two or more users to connect to the same database without issue.
Should you move to a larger environment - or just have time to enjoy
such an exercise - you may find you have to transition to the use of
unbound forms.

The front-end will contain the forms, reports, macros, queries, etc...
while the back-end contains all of the tables. The front-end - so as
to have access to the tables - is linked to the back-end. The front-
end is then installed on the user's computers - each user having their
own copy of the front-end which is then linked to the data.

When the users then log in to use the DB they should both then be able
to work simultaneously without issue.

Dindulis Rimantas wrote:

Hello, Dears Access intusiast ;]

I.m have one database, but i dont known how can conect 2 ussers same
time and update in same time...

Thanks wery lot,

Rgds.

Rimas- Slëpti cituojamà tekstà -

- Rodyti cituojamà tekstà -