Database design for a network

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

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 Datasheet
Your Resource For Help With Access, Excel And Word Applications

www.pcdatasheet.com




"AMY Z." wrote in message
...
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

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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications

www.pcdatasheet.com




"AMY Z." wrote in
message
news:F9C7E6DE-37DF-44F0-BE33-
...
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


.

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 Datasheet
Your Resource For Help With Access, Excel And Word Applications

www.pcdatasheet.com


"RSC" wrote in message
...
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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications

www.pcdatasheet.com




"AMY Z." wrote in
message
news:F9C7E6DE-37DF-44F0-BE33-
...
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


.

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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications

www.pcdatasheet.com


"RSC" wrote in
message
...
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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications

www.pcdatasheet.com




"AMY Z." wrote in
message
news:F9C7E6DE-37DF-44F0-BE33-
...
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


.



.

Sooner or later your frontend MDE is going to become corrupted and unusable
with all users accessing the same file!!!

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

www.pcdatasheet.com


"RSC" wrote in message
...
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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications

www.pcdatasheet.com


"RSC" wrote in
message
...
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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications

www.pcdatasheet.com




"AMY Z." wrote in
message
news:F9C7E6DE-37DF-44F0-BE33-
...
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


.



.

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 Datasheet" wrote in message
ink.net...
Sooner or later your frontend MDE is going to become corrupted and
unusable
with all users accessing the same file!!!

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

www.pcdatasheet.com


"RSC" wrote in message
...
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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications

www.pcdatasheet.com


"RSC" wrote in
message
...
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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications

www.pcdatasheet.com




"AMY Z." wrote in
message
news:F9C7E6DE-37DF-44F0-BE33-
...
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


.



.

Well, if thats a possibility, its a slim one, since its
been running 365 days a year for over 2 years now. And
even if that were to ever happen... its simply re-posted
using the backup, and no data is stored in the front end,
hence, no data to corrupt.
Im sure if it was possible that would happen, with 32
users constantly using the front end MDE over 2 years, it
would have happened by now.

-----Original Message-----
Sooner or later your frontend MDE is going to become
corrupted and unusable
with all users accessing the same file!!!

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

www.pcdatasheet.com


"RSC" wrote in
message
...
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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications

www.pcdatasheet.com


"RSC" wrote in
message
...
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
Datasheet
Your Resource For Help With Access, Excel And Word
Applications



www.pcdatasheet.com




"AMY Z." wrote in
message
news:F9C7E6DE-37DF-44F0-BE33-
...
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


.



.



.

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 Datasheet" wrote in message
news:PugHd.1490
...
Sooner or later your frontend MDE is going to become
corrupted and
unusable
with all users accessing the same file!!!

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

www.pcdatasheet.com


"RSC" wrote in
message
...
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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications


www.pcdatasheet.com


"RSC" wrote in
message
...
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
Datasheet
Your Resource For Help With Access, Excel And Word
Applications



www.pcdatasheet.com




"AMY Z." wrote in
message
news:F9C7E6DE-37DF-44F0-BE33-
...
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


.



.





.

So tell us how a frontend that exists on a server is used without opening
Access on the server.

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

www.pcdatasheet.com


"RSC" wrote in message
...
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 Datasheet" wrote in message
news:PugHd.1490
...
Sooner or later your frontend MDE is going to become
corrupted and
unusable
with all users accessing the same file!!!

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

www.pcdatasheet.com


"RSC" wrote in
message
...
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 Datasheet
Your Resource For Help With Access, Excel And Word
Applications


www.pcdatasheet.com


"RSC" wrote in
message
...
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
Datasheet
Your Resource For Help With Access, Excel And Word
Applications



www.pcdatasheet.com




"AMY Z." wrote in
message
news:F9C7E6DE-37DF-44F0-BE33-
...
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


.



.





.