Layers in client documents

  • Thread starter Thread starter WestWingFan
  • Start date Start date
W

WestWingFan

I have a client who wishes to place several hundred documents into a
database. Then attach values to specific statements in the document. So far
so good.

But, the documents are inconsistent in their presentation the statements for
example:

Document 1:
Section
Statement
Document 2:
Section
Subsection
Statement
Document 3:
Section
Subsection
Subsubsection
Statement
Document 4: Is a mix of documents 1-3 like.....
Section
Statement
Subsection
Statement
Statement

I would like to preserve the layering as presented in the client's
documents. But I'm not sure how to do it. Is it possible to have all of the
statements in one table with different fields for the subsections and
subsubsections? If those fields are null, then don't report them and if they
are anything besides null to report them.....

Thanks in advance!
 
I have a client who wishes to place several hundred documents into a
database. Then attach values to specific statements in the document.
Click to expand...

Sounds like you are trying to build a DMS (http://en.wikipedia.org/
wiki/Document_Management) in Access. You admit you are "not sure how
to do it" so can you please spare a few moments to explain why you
aren't using a dedicated COTS (http://en.wikipedia.org/wiki/
Commercial_off-the-shelf) system? Not NIH (http://en.wikipedia.org/
wiki/Not_Invented_Here) I hope ;-)

Jamie.

--
 
I'm not trying to build a DMS. I am interested in the statements, because
that is what I am connecting other information to in the database. Anyone
else have a suggestion?
 
To get meaningful suggestions you need to characterize your proposed
application somewhat further:

Will the target documents be "live"? If so you have to assure that
your stored data reflects the current state of the pertinent document.
Date stored vs. document's date modified.

Will the documents be fully accessible by Word or another VBA
compliant application that can be automated with Access? If so then,
in very broad strokes the general algorithm would be something like:

Open the document and scan forward.
Find differentiator between types of text such as Word's
Outline markers / styles
In tblDocSecChar
Capture a unique value such as "Nth character in doc"
Store the text (or object) type and Char#
Find next separator of same type
Store the text type and Char#
Loop to Find next separator of same type
Find Next type differentiator

HTH
 
Thanks for the response Larry.

Here is my characterization. I am using Access as a tool for statement
display so I can analyze the statements and make connections to them (for
example a statement about brakes would be connected to another statement
about the role of friction in making a car stop and one about reading
technical manuals). My deliverable is not an application, merely the tables
of information which are going to be imported into a separate application. I
am in contact with the application company about how to do that. As our
mutual client is moving to an online application, I really don't know if the
documents are going to be live.....

Does this help?
 
My earlier response really covers the territory of your original post
and your last one....

It's up to you to implement the pseudo code in the Access environment
to produce the results you want to make available to the external
world.

HTH
 
Sorry, my last sounded like "And the rest is up to you". While your
application is indeed yours to do, please post back as new issues
arise.

HTH
 
Thanks.

Larry Daugherty said:
Sorry, my last sounded like "And the rest is up to you". While your
application is indeed yours to do, please post back as new issues
arise.

HTH
Click to expand...
 
Back
Top