Results 1 to 11 of 11
  1. #1
    JustCallMeAl
    Guest

    System Design (Word97 SR2)

    Haven't said much to say lately because I haven't had much to say. However, something has come up that I would appreciate input on.

    I have the unique opportunity to institute a major change in the manner in which we create our documents.

    We have several standard documents which currently come from six individual files. These files supply the boilerplate text, which include some fillin fields for the user to fill-in. About 98% of the content in all six forms (which is what we call our documents) is the same. So why have six different forms? My question exactly.

    I had mentioned this to my supervisor about two years ago. At that time I was not in a position to institute the change--I didn't have the position to do that. However, now I do.

    Initially, I plan on using one userform (with multipage) to gather all the information necessary to create the document. After gathering the information, the correct version of the six documents will be created. What I would appreciate is ideas of how to proceed between the time of gathering the information (userform) to completed document.

    One thought that has been bounced around in the past is to use an Access database. However, the counterpoint of that is the time factor involved in accessing (no pun) an Access database.

    Therefore, I would appreciate some brainstorming on this.

    Thanks

  2. #2
    Gold Lounger
    Join Date
    Dec 2000
    Location
    Hollywood (sorta), California, USA
    Posts
    2,759
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: System Design (Word97 SR2)

    How much data are you gathering?

    I use mostly global variables with a few on the fly autotext for
    storing formatted text that cannot be stored in variables.

    But I also use one global app to manage the entire document
    assemby process. Of course I recommend that technique because user productivity goes way UP when they learn and use a single UI for all they do.

    If you need to store the data entered for later use, then the database is a good idea.

    My app will soon not only utilize SQL table data (entered via other processes), but will be the front end to enter the data as well.
    Kevin <IMG SRC=http://www.wopr.com/w3tuserpics/Kevin_sig.gif alt="Keep the change, ya filthy animal...">
    <img src=/w3timages/blackline.gif width=33% height=2><img src=/w3timages/redline.gif width=33% height=2><img src=/w3timages/blackline.gif width=33% height=2>

  3. #3
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: System Design (Word97 SR2)

    .ini style files are fast and cheap if the data is easily represented as text.

    Write:
    System.PrivateProfileString(strMyINIfile, _
    "MySection", "MyKey") = "Some text value"

    Read:
    strSomeValue = System.PrivateProfileString(strMyINIfile, _
    "MySection", "MyKey")

  4. #4
    JustCallMeAl
    Guest

    Re: System Design (Word97 SR2)

    Thanks, Kevin

  5. #5
    JustCallMeAl
    Guest

    Re: System Design (Word97 SR2)

    Thanks jscher.

  6. #6
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: System Design (Word97 SR2)

    I wrote Customizer and Files Processor can be roped in to run Codetext against a slew of documents, that is, in tandem these two utilities give you the ability to grab every bit of common text across a hard drive or sub-directory.


    Seeing as how its you, BigAl, I'll grudingly (grin!) offer to customize to a limited extent.

  7. #7
    JustCallMeAl
    Guest

    Re: System Design (Word97 SR2)

    You link to CodeText leads to http://www.vif.com/users/cgreaves/CodeText.htm, which in turn has this link: file:///D:/GREAVES/ADMIN/Web2001/50megs/codet.zip, a file on your computer! I would be interested in looking at CodeText, but for that little fact. <img src=/S/smile.gif border=0 alt=smile width=15 height=15>

  8. #8
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: System Design (Word97 SR2)

    JustCallMeStupid!

    I apologise, especially to those who sent me an email 9to which I have replied with attachments).

    I believe the links are now correct.


    OTOH maybe life would be a lot simpler if i just left the links pointing to D: and let you guys help yourselves to whataver I've got here .......

  9. #9
    JustCallMeAl
    Guest

    Re: System Design (Word97 SR2)

    The link at for CodeText at "http://cgreaves.50megs.com/index.html" still points to your d: drive. And yes, I did refresh my browser.

  10. #10
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: System Design (Word97 SR2)

    > still points to your d: drive.

    That's because I am more stupid than even I can imagine, and I forgot to rename the u/l index.htm to be index.html.

    What the 'l!

  11. #11
    JustCallMeAl
    Guest

    Re: System Design (Word97 SR2)

    Thanks all for your comments.

    With the current method of document creation, which I inherited, what I would like to do, I can't. I would have to rewrite the entire system--take about a year--and these revisions need to be done now.

    Kevin mentioned global variables and autotext. Both are good, but both, in this case, would be unworkable. Variables, as you mentioned, cannnot contain formatting, which I need. Autotext can; but they must be saved in a .dot file. I dislike doing that because it makes them so hard to update. We have about 20 "major" templates (.dot files) which control the many different types of documents we create (again, this was inherited). With the shear volume we create, the possibility that the template would be in use when it needed updating is very high. We have a couple like that, and it becomes a real challenge to update them.

    Jscher2000 mentioned ini files. That is a good idea, but like document variables, it cannot contain formatting. (The primary formatting that I need are bookmarks).

    Chris mentioned his Codetext program he wrote. But after it failed twice (once a known bug which you list in the *faq.dot and the other was when I tried to reverse, if I remember correctly, three paragraphs, it kept on running and running, like the Eveready Bunny), and since the code is password protected, meaning I couldn't learn from it, I decided to move another direction.

    Also, there are some other factors which I didn't mention because I forgot about them. These must be accounted for in the document creation process.

    Therefore, I have decided to go the following, which will make it a little more modularized, but allow for current conditions.

    I'm going to build a library of document chunks. These will be Word documents that I can insert at a given bookmark. They themselves will contain bookmarks for the user interface to drop the information into (I try to bind the bookmarks to the control names, therefore, I only have to cycle through the controls, matching them with the bookmark name, and drop in the information).

    To meet the unique situation that I forgot to mention, I am going to use the ini file concept to save a boolean. Since (and I hope I get the terminology correct) Word 97 cannot pass a value to a macro (i.e., Application.Run "Peanut Butter", filler:="Jam"), I can use a temporary ini file to accomplish the same thing.

    So, even though there didn't seem to be much discussion, the ideas you gave sparked a workable "solution" to fit in the current circumstances.

    Thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •