Re: Database design for a network

Have been following this thread with interest as I am trying to get a
multi-user app working properly. I'm not a professional developer but more
of a power user writing an app for my own small company. I have four client
PCs connected to a server. As I understand the approach it should be:-

- When happy with the table design make a back-end version and keep this on
the server in a folder with shared access
- Design forms, queries, reports etc - does it matter whether you use the
mdb or the back-end version ?
- Make a front-end version to contain the forms etc - Is this the same as
creating an mde version - I think the implication of some of the postings is
not necessarily
- Decide whether to keep the front end(s) on client PCs or as a single copy
on a shared server folder. There seem to be pros and cons.

Have I got this right ? And is this topic written up well for my level of
capability anywhere. I can't seem to find it in the help system or in the
Que book. I think the key point is nothing seems to explain clearly what a
front end is and how to make one which is why this thread is helpful.
--
Gooner D
(May the Great One on High smile upon Arsenal for ever)


"Lynn Trapp" wrote:

What's the difference between "the application" and "the frontend"? I'm
afraid I'm lost.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


"RSC" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:05d901c4fe3e$8950fc30$a401280a@xxxxxxxxxx
The application does not reside on a server, simply the
front and back ends, so NO sessions of access are open on
the server, just one session of access on each individual
PC where ACCESS IS INSTALLED. And one LDB file per
backend is created per MDE backend module regardless of
the number of users. Im quite suprised no one here knew
that already...
ALL 32 users have been on at the same time with no
noticeable decrease because of the reason Ive outlined
above. Someone would have to be insane to actually run
off of a server based access app. ...thats what the PC is
for, to install the application there; and to store the
front end forms and reports, and backend data on the
server.

Im quite suprised no one here knew that already...


An excellently working access environment for almost 3
years now.

-----Original Message-----
Not only that, but every time a user opens the frontend
that resides on the
server, the server will actually open a new session of
Access. This will use
up server resources, thus, slowing the application down
considerably. The
more users you have the worse the problem will get.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


"PC Data***" <nospam@xxxxxxxxxxx> wrote in message
news:PugHd.1490
$Ju1.1431@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sooner or later your frontend MDE is going to become
corrupted and
unusable
with all users accessing the same file!!!

--
PC Data***
Your Resource For Help With Access, Excel And Word
Applications
resource@xxxxxxxxxxxxxxx
www.pcdata***.com


"RSC" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:06c801c4fd9e$32c751c0$a601280a@xxxxxxxxxx
For my application I have 32 users and I have the
front
and back ends as MDE's, posted on the network and not
on
the users PC, since when i want to upgrade the front
end
or simply make changes to it, id rather not have to
worry
about whats on someones PC (especially 32 of them).
Its
set up so that all 32 users can simultaneously share
the
front end MDE which is tied to multiple back end MDEs.
Note that users must have read/write network access to
the folder which hosts the MDE so that the temporary
LDB
files can be created when the databse is accessed.


-----Original Message-----
To clarify --- post the backend file on the network
and
a copy of the
frontend on each user's computer.

In regards to a .mde file, it's a good idea but be
aware
that a .mde file
can not be modified. You need to save the
original .mdb
file so you can make
changes to it and then create a new .mde file from
the
revised .mdb file.

--
PC Data***
Your Resource For Help With Access, Excel And Word
Applications

resource@xxxxxxxxxxxxxxx
www.pcdata***.com


"RSC" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:06a401c4fd9b$52d2ee50$a601280a@xxxxxxxxxx
I would also not post the mdb on the network. I
would
make the front end an MDE file rather than an
MDB... Go
to Tools selection in the Access menu bar, and
select
Make MDE. This will load much faster, and also
prevent
anyone regardless of their security rights from
modifying
or viewing your code. Its a good way to CYA.


-----Original Message-----
Start with two .mdb files. For development, save
both
files on your
harddrive - it does not matter which folder they
are
saved to. The backend
file is only for your tables. Create all your
tables
in
the backend file.
After you have created all the tables, save the
backend
file on the server
in a folder which all users for whom the database
is
intended share. Delete
the backend file from your harddrive. Open the
front
end
file, go to File -
Get External Data and link to all the tables in
the
backend file. The list
of all tables will appear in the frontend file
with a
right arrow on the
left of all the table names. You are now ready to
create
all the queries,
forms and reports you need for the database in the
frontend file.

--
PC
Data***
Your Resource For Help With Access, Excel And Word
Applications

resource@xxxxxxxxxxxxxxx

www.pcdata***.com




"AMY Z." <AMYZ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:F9C7E6DE-37DF-44F0-BE33-
FF0C8C443C8F@xxxxxxxxxxxxxxxx
Hi
I need to design a new Database to be used on my
company's network. It is
a
small network with one main server and approx.
12
frontend computer
stations.

This is my first time trying this. All my
databases
so
far have been used
on
single computers. Is there anything I should be
aware
of when starting
this
in the beginning design stage? Or should I
build
the
whole program
normally
and then use the database splitter wizard?

Thanks for your time,
Amy


.



.





.




.