By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,327 Members | 2,627 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,327 IT Pros & Developers. It's quick & easy.

converting database from stand-alone to networked?

P: n/a
RC
I am starting a project to track inventory for a medium size business.
The business would like to start off running the Access database on a
single laptop and move the laptop from one area of the warehouse to
another area of the warehouse as the database is needed. They want to
start this way to get the inventory tracking system in use as quickly
as possible. After the inventory tracking system gets refined and
updated so the process is working efficiently, then they will probably
want to put the database on the company network so that information
can be entered into the database from one part of the warehouse and a
different part of the warehouse without carting the laptop back and
forth.

My question is: Is it difficult to move/convert/transfer a standalone
database from a single laptop to a Network? If it is difficult,
should I just start with the network option from the beginning? Are
there any particular things I should take into consideration when
creating the stand-along version that will help make the transfer to a
network go smoothly? What about Data Access Pages and using a browser
for the data entry forms?
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
RC wrote:
I am starting a project to track inventory for a medium size business.
The business would like to start off running the Access database on a
single laptop and move the laptop from one area of the warehouse to
another area of the warehouse as the database is needed. They want to
start this way to get the inventory tracking system in use as quickly
as possible. After the inventory tracking system gets refined and
updated so the process is working efficiently, then they will probably
want to put the database on the company network so that information
can be entered into the database from one part of the warehouse and a
different part of the warehouse without carting the laptop back and
forth.

My question is: Is it difficult to move/convert/transfer a standalone
database from a single laptop to a Network? If it is difficult,
should I just start with the network option from the beginning? Are
there any particular things I should take into consideration when
creating the stand-along version that will help make the transfer to a
network go smoothly? What about Data Access Pages and using a browser
for the data entry forms?


There is no problem.

An MDB can contain tables, queries, forms, reports, modules, and macros.
Lets say your MDB contains them all. All you need to do is copy to
the MDB to the network when ready and it is accessible to all. Or you
can split the tables that contain the data to a backend database and
store that on the network and have the rest of the objects in the front
end and keep the front end on the laptop and you link the backend tables
to the front end...real easy to do. When ready, you distribute the
front end to all other users.

One reason I like the network to have the files is that networks are
often backed up daily. If you forget to backup your database and you
accidentily delete it or the laptop computer crashes...you've lost a lot
of work.

The folks may want it done the way you describe for security. Just
remember to make backups. But you could set up a network folder that
only you have rights to...it'd still get backed up.

Sometimes it's not worth the hassle to make a stink over a small thing
like this and go with the flow and do it the way they want. I guess
it's up to you as to how important you think this is.
Nov 13 '05 #2

P: n/a
RC
Thanks, you put my mind at ease. I won't worry about networking right
now and I'll cross that bridge when I come to it.

Salad <oi*@vinegar.com> wrote in message news:<xt***************@newsread3.news.pas.earthli nk.net>...
RC wrote:
I am starting a project to track inventory for a medium size business.
The business would like to start off running the Access database on a
single laptop and move the laptop from one area of the warehouse to
another area of the warehouse as the database is needed. They want to
start this way to get the inventory tracking system in use as quickly
as possible. After the inventory tracking system gets refined and
updated so the process is working efficiently, then they will probably
want to put the database on the company network so that information
can be entered into the database from one part of the warehouse and a
different part of the warehouse without carting the laptop back and
forth.

My question is: Is it difficult to move/convert/transfer a standalone
database from a single laptop to a Network? If it is difficult,
should I just start with the network option from the beginning? Are
there any particular things I should take into consideration when
creating the stand-along version that will help make the transfer to a
network go smoothly? What about Data Access Pages and using a browser
for the data entry forms?


There is no problem.

An MDB can contain tables, queries, forms, reports, modules, and macros.
Lets say your MDB contains them all. All you need to do is copy to
the MDB to the network when ready and it is accessible to all. Or you
can split the tables that contain the data to a backend database and
store that on the network and have the rest of the objects in the front
end and keep the front end on the laptop and you link the backend tables
to the front end...real easy to do. When ready, you distribute the
front end to all other users.

One reason I like the network to have the files is that networks are
often backed up daily. If you forget to backup your database and you
accidentily delete it or the laptop computer crashes...you've lost a lot
of work.

The folks may want it done the way you describe for security. Just
remember to make backups. But you could set up a network folder that
only you have rights to...it'd still get backed up.

Sometimes it's not worth the hassle to make a stink over a small thing
like this and go with the flow and do it the way they want. I guess
it's up to you as to how important you think this is.

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.