p2p.wrox.com Forums

Need to download code?

View our list of code downloads.


  Return to Index  

access thread: Multiple Access on a network?


Message #1 by "Chip German" <lunartech@c...> on Thu, 20 Jun 2002 05:07:02
Hi, I am very new to database construction, so I am apologize if this is a 
stupid set of questions.
What I am trying to do is develop a database for our business that can be 
accessed almost entirely via a web browser such as IE 5.
The problem I have been running into with my first test database is that 
when I try to access the entry or view pages for the database (such as 
entering a new customer or viewing a list of customers) from any other 
computer than the server for the network, I get an error that indicates 
the file was not found on C:\inetpub\wwwroot\fpdb...etc.
Do I need to make a copy or replicate (or whatever) the actual Access GUI 
file onto the other computers in the same location on the C drive?
If I do this will the data actually get entered into the server and allow 
the other computers on the network to see data that was entered by a 
different computer?
What I have (basically) learned so far is that Access is not actually the 
database, that MSDE is the database, Access is just the face or front end 
to developing that MSDE database, sort of like a cardboard box with a grid 
inside full of numbers that can't normally be understood without some form 
of interpretation, Access provides that interpretation.
Simply put, would this be an accurate description?
I have 5 machines running Win 2K Pro SP2, all with MS Office Pro but only 
one has been set up to behave as a server. After reading a great deal and 
trolling extensively I have figured out that I probably need to install 
MSDE on all the other machines as well but I feel my idea should work.
I am getting close to the deadline I have set to have this up and running 
so its time for me to start asking questions and I appreciate any 
assistance I can get however slight.
By way of explaination, we are a commercial satellite distribution company 
and we have set up several control systems as well, basically we have 
almost no budget to work with yet since we are quite a young company and 
cannot afford to hire someone to do this for us so we have been forced to 
figure it out ourselves.
Message #2 by "Haslett, Andrew" <andrew.haslett@i...> on Thu, 20 Jun 2002 13:44:48 +0930
Hi Chip. You seem to getting a little mixed up here.  It seems you are
describing two different set-ups:

1. Create a front-end to an MS Access data store to be viewed through a web
browser
2. Creating an MS Access front-end to be run from a number of client
machines.

Going by your earlier statements I'm guessing it's option 1.  For this all
you need is ONE copy of the access database file (.MDB) and a Web Server
(such as IIS). You don't actually need a copy of MS Access itself on any of
the client machines, or the server.  It's not actually recommended to
install office on a web server anyway as it is a resource hog. (Of course,
to create the MDB file itself you're generally going to need use Access at
some stage anyway).

So we've got the MDB file and a web server. You need some server side
scripting (such as ASP) to interface with your database and output your
results into HTML so it can be viewed in a browser (which each client needs
to have on their machine).  You can also use Data Access Pages (available in
A2K and above), however I've not used them so shouldn't comment.

Finally, your clients browser needs to be able to see and access the web
server (via your network) so they can view the output.

That's pretty much it. Of course, each step in itself has a number of tasks
and implications that you'll come across as you go.  Going by your error
message, you seem to be using FrontPage to set up your pages, which is a
good start, although it does produce a lot of unnecessary and jumbled code.
It all depends on the level you wish to get into.

BTW, MSDE is a 'stand-alone' database engine - basically a drastically
scaled down version of MS SQL Server, used for larger, high traffic
applications. I doubt you would needs this in your situation with only 5
users.

Another note, Win 2K Pro CAN be run as a web server, however it is limited
to 10 connections and is not really designed to carry much traffic. You
would need to install IIS on Win 2k Server or better.

If you need any more help, feel free to ask.

Cheers,
Andrew

-----Original Message-----
From: Chip German [mailto:lunartech@c...]
Sent: Thursday, 20 June 2002 2:37 PM
To: Access
Subject: [access] Multiple Access on a network?


Hi, I am very new to database construction, so I am apologize if this is a 
stupid set of questions.
What I am trying to do is develop a database for our business that can be 
accessed almost entirely via a web browser such as IE 5.
The problem I have been running into with my first test database is that 
when I try to access the entry or view pages for the database (such as 
entering a new customer or viewing a list of customers) from any other 
computer than the server for the network, I get an error that indicates 
the file was not found on C:\inetpub\wwwroot\fpdb...etc.
Do I need to make a copy or replicate (or whatever) the actual Access GUI 
file onto the other computers in the same location on the C drive?
If I do this will the data actually get entered into the server and allow 
the other computers on the network to see data that was entered by a 
different computer?
What I have (basically) learned so far is that Access is not actually the 
database, that MSDE is the database, Access is just the face or front end 
to developing that MSDE database, sort of like a cardboard box with a grid 
inside full of numbers that can't normally be understood without some form 
of interpretation, Access provides that interpretation.
Simply put, would this be an accurate description?
I have 5 machines running Win 2K Pro SP2, all with MS Office Pro but only 
one has been set up to behave as a server. After reading a great deal and 
trolling extensively I have figured out that I probably need to install 
MSDE on all the other machines as well but I feel my idea should work.
I am getting close to the deadline I have set to have this up and running 
so its time for me to start asking questions and I appreciate any 
assistance I can get however slight.
By way of explaination, we are a commercial satellite distribution company 
and we have set up several control systems as well, basically we have 
almost no budget to work with yet since we are quite a young company and 
cannot afford to hire someone to do this for us so we have been forced to 
figure it out ourselves.
Message #3 by "Carnley, Dave" <dcarnley@a...> on Thu, 20 Jun 2002 09:54:13 -0500
a
Message #4 by "Carnley, Dave" <dcarnley@a...> on Fri, 21 Jun 2002 09:17:33 -0500
Buy a book on it.  Really!  if you already have one, buy a new (better) one.
not trying to be mean or anything but this is not the most basic thing you
are trying to do.  It becomes easier with every new tool release but it
still isn't the kind of thing somebody writing their first app usually can
do right the first time ;)  but with a good book, maybe one that uses at
least one example system that is similar to your architecture, you can do
it!  It's not rocket science but it ain't making an omelet either.   Look
into VB.Net it is designed to do exactly this, a co-worker of mine is using
it for some projects here and he is Loving it I compare my VBA / VB6 code
and .Net makes a lot of things automatic and easy.  But he was an
experienced programmer before he started with .net

10 suggestions for learning good programming:

(1) keep it simple
(2) get the basics working before you add bells and whistles
(3) study good code to see how it works
(4) write down your requirements
(5) design your database before you start coding
(6) design your screens before you start coding
(7) build the app in layers - login/connection to db, menus and navigation,
screens and form, manipulating db data, advanced GUI tricks (bells and
whistles)
(8) don't copy/paste code, use functions and objects
(9) test as you go, implement error handling code EARLY
(10) KEEP IT SIMPLE  you probably have lots of great ideas for what it could
do, but once it is in use you'll have more and better ideas for improvements
than you have now.

and number 11 (mine goes to 11 for when you need a little more)  HAVE FUN

David


-----Original Message-----
From: Haslett, Andrew [mailto:andrew.haslett@i...]
Sent: Wednesday, June 19, 2002 11:15 PM
To: Access
Subject: [access] RE: Multiple Access on a network?


Hi Chip. You seem to getting a little mixed up here.  It seems you are
describing two different set-ups:

1. Create a front-end to an MS Access data store to be viewed through a web
browser
2. Creating an MS Access front-end to be run from a number of client
machines.

Going by your earlier statements I'm guessing it's option 1.  For this all
you need is ONE copy of the access database file (.MDB) and a Web Server
(such as IIS). You don't actually need a copy of MS Access itself on any of
the client machines, or the server.  It's not actually recommended to
install office on a web server anyway as it is a resource hog. (Of course,
to create the MDB file itself you're generally going to need use Access at
some stage anyway).

So we've got the MDB file and a web server. You need some server side
scripting (such as ASP) to interface with your database and output your
results into HTML so it can be viewed in a browser (which each client needs
to have on their machine).  You can also use Data Access Pages (available in
A2K and above), however I've not used them so shouldn't comment.

Finally, your clients browser needs to be able to see and access the web
server (via your network) so they can view the output.

That's pretty much it. Of course, each step in itself has a number of tasks
and implications that you'll come across as you go.  Going by your error
message, you seem to be using FrontPage to set up your pages, which is a
good start, although it does produce a lot of unnecessary and jumbled code.
It all depends on the level you wish to get into.

BTW, MSDE is a 'stand-alone' database engine - basically a drastically
scaled down version of MS SQL Server, used for larger, high traffic
applications. I doubt you would needs this in your situation with only 5
users.

Another note, Win 2K Pro CAN be run as a web server, however it is limited
to 10 connections and is not really designed to carry much traffic. You
would need to install IIS on Win 2k Server or better.

If you need any more help, feel free to ask.

Cheers,
Andrew

-----Original Message-----
From: Chip German [mailto:lunartech@c...]
Sent: Thursday, 20 June 2002 2:37 PM
To: Access
Subject: [access] Multiple Access on a network?


Hi, I am very new to database construction, so I am apologize if this is a 
stupid set of questions.
What I am trying to do is develop a database for our business that can be 
accessed almost entirely via a web browser such as IE 5.
The problem I have been running into with my first test database is that 
when I try to access the entry or view pages for the database (such as 
entering a new customer or viewing a list of customers) from any other 
computer than the server for the network, I get an error that indicates 
the file was not found on C:\inetpub\wwwroot\fpdb...etc.
Do I need to make a copy or replicate (or whatever) the actual Access GUI 
file onto the other computers in the same location on the C drive?
If I do this will the data actually get entered into the server and allow 
the other computers on the network to see data that was entered by a 
different computer?
What I have (basically) learned so far is that Access is not actually the 
database, that MSDE is the database, Access is just the face or front end 
to developing that MSDE database, sort of like a cardboard box with a grid 
inside full of numbers that can't normally be understood without some form 
of interpretation, Access provides that interpretation.
Simply put, would this be an accurate description?
I have 5 machines running Win 2K Pro SP2, all with MS Office Pro but only 
one has been set up to behave as a server. After reading a great deal and 
trolling extensively I have figured out that I probably need to install 
MSDE on all the other machines as well but I feel my idea should work.
I am getting close to the deadline I have set to have this up and running 
so its time for me to start asking questions and I appreciate any 
assistance I can get however slight.
By way of explaination, we are a commercial satellite distribution company 
and we have set up several control systems as well, basically we have 
almost no budget to work with yet since we are quite a young company and 
cannot afford to hire someone to do this for us so we have been forced to 
figure it out ourselves.


  Return to Index