how to transfer access aplication to the multi user environment!-URGENT

[ljubo lecic via AccessMonster.com]

I have developed a pretty complex ACCESS aplication
which is working fine in a single user environment.
Today, I was asked if I could install the aplication
on the server to be simultaniously used by 5 users.
Being new in access I postponed my answer.
My question is:
What is the best way (or the easiest) to do such a thing.
(If I decided to use Oracle as a back end what steps
should I do )

 

[Steve Schapel]

ljubo

The basic concept here is to put a separate copy of the application file
(frontend) on each local machine, with the backend data file located on
the server, and link from the frontend to the backend tables. I have no
personal experience with using an Oracle backend, but this general
principle applies regardless of the backend type, whether the connection
to the backend is via linked tables functionality, or ODBC.

 

[Arvin Meyer]

The most important consideration is to make sure that each user is working
from his/her own copy of the front-end, running from each workstation, or
from separate folders on a Terminal Server. Whether you use Jet, Oracle, or
SQL-Server as the engine doesn't change the way the front-end is deployed.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Norman Yuan]

Theoretically, there is nothing to transfer.

The simplest way:
a. Choose a computer on the network and create a shared folder. Make sure
all you Access app used has read/write permission to this folder.
b. Drop the *.mdb file in this folder.

You are done! User simply go to that folder and double-click it to start.
Note: all users need to have Access installed on their computers. However,
it is alway strongly recommended to split Access app into back end
containing tables only and front end containing forms, reports, queries,
code modules, if searal users working on the same database. This way, you
may be able to connect your Access front end to different back end (as you
described the possibility to use Oracle as back end) with minimum changes
(however, a back end of true database server, such as Oracle or SQL Server,
is so different from a JET database, that the transition from JET database
back end to a database server could render your front end useless or need to
re-write in order to use the database server's power more efficiently).

 

[ljubo lecic via AccessMonster.com]

Thanks a lot to all of you who answered my post!