Help with Complex VBA program

[rogerbowering]

Hi



At work I have to create Report templates using Word and pre-supplied Macro enabled Template (.dotm)

The template provides additional buttons and code to the Word documents I work on

The purpose of the code is to, essentially create a HTML version of the document ('documentname.tmp') in a subdirectory (compiled) of the original working document directory, i.e. //my directory/compiled/ and then it 'compiles' the HTML code into a further sub directory //my directory/compiled/mydocument_files/ and a jsp version of the document.

So I start with
//my directory/myworddoc.docx

and end with
//my directory/myworddoc.docx
//my directory/compiled/createdoc_myworddoc.jsp
//my directory/compiled/createdoc_myworddoc.tmp
//my directory/compiled/myworddoc_files/

For the last year, when I run the code, all the necessary folders and documents are created and I am left with the active docx file on screen.

But now when I run the code I left in the compiled folder with the tmp file as the active document (and the docx file closed).

Can anyone make sense of the VBA and advise if it can be changed to achieve what I need

PS the original coder has now disappeared

[macropod]

Your attached template contains over 1000 lines of code. That's a lot to ask anyone to analyse, looking for problems. Some of it seems unnecessarily convoluted, too. For example, you could probably replace the calls to getNameOnly, which invokes:

Function getCurName() As String
    getCurName = LCase(ActiveDocument.name)
End Function

Function getNameOnly() As String
    Dim testString As String
    Dim lastIndex As Integer
    lastIndex = InStrRev(getCurName(), ".") - 1
    testString = Mid(getCurName(), lastIndex, Len(getCurName()) - lastIndex)
    getNameOnly = Mid(getCurName(), 1, lastIndex)
End Function

with:

LCase(Split(ActiveDocument.Name, ".doc")(0))

You could most certainly replace statements like:

ActiveDocument.path + "\" + ActiveDocument.name

with:

ActiveDocument.FullName

Usually, if the execution behaviour changes, it's because someone has changed the code or done something to the data structures (e.g. file/folder names) that invalidates the assumptions upon which the code works. I suggest you review whatever changes might have been made in those respects.