E
Eric
Hi all, I have read almost all posts in these Discussion Groups and still
can't get a handle on what I'm doing. I now have a great library of
favorites to use in the future but still need some advice.
I am developing a template for our agency. The goal is to standardize our
formal reports and also capture specific elements of the reports for use in
an access database. These reports can be as large as 100 pages sometimes.
The Template will actually be the final report and needs to be formal.
I have protected sections and non protected sections, form fields and tables
etc. But exporting the data to .txt seems to be an issue and I am
questioning my approach.
1. Exporting the fields are not a problem. Except if the user has to add
an additional field. The new field does not have a name, or takes on a
generic (Text1) name. This creates an export and database issue.
2. If I use tables then the "convert tables to text" can be a huge task
doing them individually. Plus tables want the first row as labels and that
really doesn’t' work with the formatting I'm trying to maintain.
3. Form fields seem to be the best way to go, except in a protected
document the user looses all the formatting flexibility; underlining, bullets
etc.
Capturing the data in these reports is just as important as the report
itself. The protection of the document is vital because of the possibility
of fields being deleted etc.
Does anyone have a better approach then any of the ones I have mentioned?
Maybe a combination of methods? I really don't know.
I appreciate any and all comments, best wishes and prayers.
LOL
Thanks
can't get a handle on what I'm doing. I now have a great library of
favorites to use in the future but still need some advice.
I am developing a template for our agency. The goal is to standardize our
formal reports and also capture specific elements of the reports for use in
an access database. These reports can be as large as 100 pages sometimes.
The Template will actually be the final report and needs to be formal.
I have protected sections and non protected sections, form fields and tables
etc. But exporting the data to .txt seems to be an issue and I am
questioning my approach.
1. Exporting the fields are not a problem. Except if the user has to add
an additional field. The new field does not have a name, or takes on a
generic (Text1) name. This creates an export and database issue.
2. If I use tables then the "convert tables to text" can be a huge task
doing them individually. Plus tables want the first row as labels and that
really doesn’t' work with the formatting I'm trying to maintain.
3. Form fields seem to be the best way to go, except in a protected
document the user looses all the formatting flexibility; underlining, bullets
etc.
Capturing the data in these reports is just as important as the report
itself. The protection of the document is vital because of the possibility
of fields being deleted etc.
Does anyone have a better approach then any of the ones I have mentioned?
Maybe a combination of methods? I really don't know.
I appreciate any and all comments, best wishes and prayers.
LOL
Thanks