Creating a complex form solution in access and Publishing it to th

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The form I would like to put in a database is 25 pages printed. It features
approximately 11 entities(locations, people, specialties, etc.). This means
that I want capability for an unlimited number of line items per entity for
each form. I would then like to publish this to the internet (using Access)
and have it so that, once completed, a user may print a hard copy that looks
EXACTLY like it does in the desktop version.
1. Is this possible?
2. If possible, how complex would you say it is? (Say on a scale of 1-10.)
3. How much time would it take to build such a form?

Since I know very little about Access, I would like some general feasibilty
oriented responses.
Thanks!
 
Hi,
to be able to access an access backend over the internet you need some
frontend technology which allows you to do that. Access forms do not, so you
either need to use DAP, ASP, PHP...which then connects to the backend and
pulls the required data.
Within access itself forms are not meant for printing. They are only to
view/edit/add data. Reports are for printing.
I hope this gets you started a little.
HTH
Good luck
 
Thanks for your quick response!
What I meant by a form is that right now it is a traditional printed form. I
don't even know what you would really call this in Access but I assume you
would have some data entry screens that would allow a user to complete the
"form", and then print it.
 
Two things:

(1) Putting your Access database on the web will require additional
knowledge & skills, over & abive the skills required to write an Access
database for use on one PC. Google the Access groups for "access and
the web" (without the quotes), or simiar terms, you should find lots of
hits.

(2) The first step in designing an Access database, is to design the
tables (your "entities") - not the forms or reports. You need to design
the tables before you even *think* of writing the forms and reports.
You design the tables by using a non-trivial, non-intuitive process
called "database normalization". Google the Access groups for that
term, you should find lots of rererences. If you have any questions
about designing your tables, post again in
microsoft.public.access.tablesdbdesign.

HTH,
TC (MVP Access)
http://tc2.atspace.com
 
Thanks for your response!
Though I am sure you are correct about creating tables and such, I am more
concerned about feasibility at this time. I need to know how much work will
be involved in creating such a complex form in Access. Perhaps you could gear
your response to those issues...
 
If you are already throughly familiar with the concept of "database
normalization", and designing table structures in "third normal form",
then, the table design will be quite simple (from what you have
described so far), and the majority of the work could possibly be in
the form(s). In which case, it would be reasonable to focus on the
forms, to get a grip on how long it would take.

*BUT* - if you are *not* throughly familiar with database
normalization and designing table structures in third normal form -
then, the *design of the tables* could be the most complex task. You
will have to learn the relevant concepts, from scratch. This could
easily be significantly more difficult, than designing the form(s) that
are based on those tables.

HTH,
TC (MVP Access)
http://tc2.atspace.com
 
PS. I'm not talking about *creating* the tables - the term that you've
used.

I'm talking about *designing* the tables - an entirely different thing.

TC
 
creating such a complex form in Access
Click to expand...

As others have said,

(a) It's not a matter just of "creating a form" but of first nutting out
a data structure suitable for the information on the 25-page printed
form and then designing the forms ("data entry screens") to allow the
data to be entered and report(s) that allow it to be printed.

(b) If you need to share the database over the internet, you can't use
an Access database for data entry. You need a technology such as ASP
that can display a form in the user's web browser and send data to and
from the database. This needn't be an Access database, but it must be
one that's available on the web server you're using.

Going back to your original questions:
1. Is this possible? Yes

2. If possible, how complex would you say it is? (Say on a scale of 1-10.)
Click to expand...
To someone who's familar with relational database design, SQL, ASP and
web applications, about 4. To me (not familiar with ASP and web
applications), about 6. To someone new to all of it, about 9.
3. How much time would it take to build such a form?
Click to expand...
It's not just a form you're asking for, but a web application. Any
answer to this would be guesswork: it depends on a huge number of
factors, including the skill and experience of the builder, the number
of users expected (a handful? tens of thousands?), whether the database
needs to be available 24/7/365, whether any outputs are required besides
the one 25-page form.... Could be weeks, could be months.

It's not just a form but a web application with a database back end. I'm
guessing
 
A good analogy would be to ask someone how much and how long would it
take to build a house with 4 bedrooms, 3 baths and a two car garage.
There is much, much more information that is neccessary to answer that
question.
 
Though we could (obviously) go on with this thread, I have obtained enough
information to at least have a glimmer of the task at hand.
Thanks to all who have posted!
 
Back
Top