Word 2003 Stub to Word 2007 file

Graham...thanks for the reply...

The enterprise application is SAP. Inside of SAP, we have links to
DOC files (links meaning the file is not stored in SAP...it's a link
to the DOC file on the business network). The DOC file has been
converted to a DOCX file so the DOC file no longer exists.

Can we create a DOC file whose job is only to redirect the user to the
converted DOCX file.

Example: abc.doc is linked in SAP. We then convert abc.doc to
abc.docx. We'd like to create a new abc.doc file that would open
abc.docx. This way, we don't have to go into SAP and change thousands
of links...the link still works and it opens the proper file (DOCX).

Dan

Enterprise application? Stub file? If you don't explain what you mean you'll
never get a reply
Links? What sort of links?

--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>


drvice RemoveThis @nppd.com wrote:
> On Dec 17, 11:41 am, drv... RemoveThis @nppd.com wrote:
>> We are in the middle of a Word 2003 to Word 2007 conversion process.
>> We have an enterprise application where we have linked a number of
>> the old Word 2003 files and when the file is converted the link is
>> now broken, due to the change in file extension (DOC to DOCX).
>>
>> Is it possible to have a Word 2003 document act as a stub file which
>> forwards the user to the DOCX file? This way, we don't have to change
>> the links in the enterprise application and the user is still
>> presented with the DOCX file as they should be.
>>
>> Any help would be greatly appreciated.
>>
>> Dan Vice
>
> bump
>
> Still hoping someone has a solution...do I possibly need to post to
> another group???
>
> Dan

I'm afraid I lost the will to live after trying to get some sense out of
SAP's web site - I sincerely hope their products are better put together?

Frankly I can't see any way of doing what you require from a Word document.
I suspect it would have been better to have left the documents in DOC
format, at least until the software has been developed to accommodate the
change to DOCX. Word 2007 can work quite happily with DOC format.

The only posibility that immediately comes to mind, though I hesitate to
suggest it as it opens up a few worm cans, is to rename the files from docx
to doc. Word 2007 will recognize its own files even with the doc extension
and open them.

Immediate complications that spring to mind are those of identification of
which files are doc and which are docx, when the issue is properly sorted,
and if anyone is using an earlier Word version, they will not be able to
open the files unless they set tools > options > general > confirm
conversion on open and select Word 2007 document - even then there will be
an issue with docs created in 2007 from 2007 templates detailed at
http://www.gmayor.com/Problems_opening_2007_docs.htm

The real answer is to change the links so they point to the right files. If
the links were in documents that could probably be achieved with a batch
process in vba, but as they are in the SAP application, I guess you'll have
to ask SAP how to do that.

--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>


drvice.DeleteThis@nppd.com wrote:
> Graham...thanks for the reply...
>
> The enterprise application is SAP. Inside of SAP, we have links to
> DOC files (links meaning the file is not stored in SAP...it's a link
> to the DOC file on the business network). The DOC file has been
> converted to a DOCX file so the DOC file no longer exists.
>
> Can we create a DOC file whose job is only to redirect the user to the
> converted DOCX file.
>
> Example: abc.doc is linked in SAP. We then convert abc.doc to
> abc.docx. We'd like to create a new abc.doc file that would open
> abc.docx. This way, we don't have to go into SAP and change thousands
> of links...the link still works and it opens the proper file (DOCX).
>
> Dan

On further reflection, provided you overcome the security issues that will
attempt to prevent you from automatically running macros saved in Word
documents when opened in Word 2007, you could create a series of Word
97-2003 documents with names to match your docx versions albeit they won't
have the x each containing the macro

Sub AutoOpen()
Dim oDoc As Word.Document
Dim sName As String
Set oDoc = ActiveDocument
sName = oDoc.FullName & "x"
Documents.Open sName
oDoc.Close wdDoNotSaveChanges
End Sub

These will open from your link and in turn open the docx version of the
filename before closing the doc version.

I suppose it should be possible to save the document in a batch process
using each docx name from a given folder, though I would have to think about
that one a bit longer


--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>


Graham Mayor wrote:
> I'm afraid I lost the will to live after trying to get some sense out
> of SAP's web site - I sincerely hope their products are better put
> together?
> Frankly I can't see any way of doing what you require from a Word
> document. I suspect it would have been better to have left the
> documents in DOC format, at least until the software has been
> developed to accommodate the change to DOCX. Word 2007 can work quite
> happily with DOC format.
> The only posibility that immediately comes to mind, though I hesitate
> to suggest it as it opens up a few worm cans, is to rename the files
> from docx to doc. Word 2007 will recognize its own files even with
> the doc extension and open them.
>
> Immediate complications that spring to mind are those of
> identification of which files are doc and which are docx, when the
> issue is properly sorted, and if anyone is using an earlier Word
> version, they will not be able to open the files unless they set
> tools > options > general > confirm conversion on open and select
> Word 2007 document - even then there will be an issue with docs
> created in 2007 from 2007 templates detailed at
> http://www.gmayor.com/Problems_opening_2007_docs.htm
> The real answer is to change the links so they point to the right
> files. If the links were in documents that could probably be achieved
> with a batch process in vba, but as they are in the SAP application,
> I guess you'll have to ask SAP how to do that.
>
>
> drvice.DeleteThis@nppd.com wrote:
>> Graham...thanks for the reply...
>>
>> The enterprise application is SAP. Inside of SAP, we have links to
>> DOC files (links meaning the file is not stored in SAP...it's a link
>> to the DOC file on the business network). The DOC file has been
>> converted to a DOCX file so the DOC file no longer exists.
>>
>> Can we create a DOC file whose job is only to redirect the user to
>> the converted DOCX file.
>>
>> Example: abc.doc is linked in SAP. We then convert abc.doc to
>> abc.docx. We'd like to create a new abc.doc file that would open
>> abc.docx. This way, we don't have to go into SAP and change
>> thousands of links...the link still works and it opens the proper
>> file (DOCX). Dan

OK I've reflected

If you open the document containing the Autoopen macro in Word 2007 (don't
allow the macro to run) then run the following macro from normal.dotm, it
should save it for every docx file as doc in the selected folder, with the
same names as the docx files but containing only the autoopen macro. It
works here on my test documents, but as I don't know what your documents
contain, I would urge you to copy the files to a new folder and run it on
that. It saves the doc files in the same folder as the docx files.

Sub CreateDOC()
'run with the document containing the autoopen macro open
Dim strFile As String
Dim strPath As String
Dim fName As String
Dim strDoc As Word.Document
Dim newDoc As Word.Document
Dim fDialog As FileDialog
Set fDialog = Application.FileDialog(msoFileDialogFolderPicker)
With fDialog
.Title = "Select folder and click OK"
.AllowMultiSelect = False
.InitialView = msoFileDialogViewList
If .Show <> -1 Then
MsgBox "Cancelled By User", , "List Folder Contents"
Exit Sub
End If
strPath = fDialog.SelectedItems.Item(1)
If Right(strPath, 1) <> "\" Then strPath = strPath + "\"
End With

Set newDoc = ActiveDocument
strFile = Dir$(strPath & "*.docx")
While strFile <> ""
Set strDoc = Documents.Open(strPath & strFile)
fName = Left(strDoc.FullName, Len(strDoc.FullName) - 1)
newDoc.SaveAs fName
strDoc.Close SaveChanges:=wdDoNotSaveChanges
strFile = Dir$()
Wend
End Sub

http://www.gmayor.com/installing_macro.htm

--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>


Graham Mayor wrote:
> On further reflection, provided you overcome the security issues that
> will attempt to prevent you from automatically running macros saved
> in Word documents when opened in Word 2007, you could create a series
> of Word 97-2003 documents with names to match your docx versions
> albeit they won't have the x each containing the macro
>
> Sub AutoOpen()
> Dim oDoc As Word.Document
> Dim sName As String
> Set oDoc = ActiveDocument
> sName = oDoc.FullName & "x"
> Documents.Open sName
> oDoc.Close wdDoNotSaveChanges
> End Sub
>
> These will open from your link and in turn open the docx version of
> the filename before closing the doc version.
>
> I suppose it should be possible to save the document in a batch
> process using each docx name from a given folder, though I would have
> to think about that one a bit longer
>
>
>
> Graham Mayor wrote:
>> I'm afraid I lost the will to live after trying to get some sense out
>> of SAP's web site - I sincerely hope their products are better put
>> together?
>> Frankly I can't see any way of doing what you require from a Word
>> document. I suspect it would have been better to have left the
>> documents in DOC format, at least until the software has been
>> developed to accommodate the change to DOCX. Word 2007 can work quite
>> happily with DOC format.
>> The only posibility that immediately comes to mind, though I hesitate
>> to suggest it as it opens up a few worm cans, is to rename the files
>> from docx to doc. Word 2007 will recognize its own files even with
>> the doc extension and open them.
>>
>> Immediate complications that spring to mind are those of
>> identification of which files are doc and which are docx, when the
>> issue is properly sorted, and if anyone is using an earlier Word
>> version, they will not be able to open the files unless they set
>> tools > options > general > confirm conversion on open and select
>> Word 2007 document - even then there will be an issue with docs
>> created in 2007 from 2007 templates detailed at
>> http://www.gmayor.com/Problems_opening_2007_docs.htm
>> The real answer is to change the links so they point to the right
>> files. If the links were in documents that could probably be achieved
>> with a batch process in vba, but as they are in the SAP application,
>> I guess you'll have to ask SAP how to do that.
>>
>>
>> drvice DeleteThis @nppd.com wrote:
>>> Graham...thanks for the reply...
>>>
>>> The enterprise application is SAP. Inside of SAP, we have links to
>>> DOC files (links meaning the file is not stored in SAP...it's a link
>>> to the DOC file on the business network). The DOC file has been
>>> converted to a DOCX file so the DOC file no longer exists.
>>>
>>> Can we create a DOC file whose job is only to redirect the user to
>>> the converted DOCX file.
>>>
>>> Example: abc.doc is linked in SAP. We then convert abc.doc to
>>> abc.docx. We'd like to create a new abc.doc file that would open
>>> abc.docx. This way, we don't have to go into SAP and change
>>> thousands of links...the link still works and it opens the proper
>>> file (DOCX). Dan

Hi,

If you have an aspiration to work in USA and thought the only way to
do that was H1 then this is the mail will greatly help you where you
can fulfill your dream!!!
We file H1 visa for IT candidates having minimum two and half years of
live experience. Please let me know if you have suitable matching for
the below mentioned skills who are willing to apply for H1 B visa.
Skills set: Primarily SAP, PeopleSoft, Java developer/architect,
Oracle developers, ASP.Net, Siebel, Tibco, Mainframes, and Testing.
GEMS Inc. is a Software Consulting, Project Management & Global
Technology Services Company located in the Washington and offshore
development center in Visakhapatnam, India. We have been in business
for over 9 years and work with several government and commercial
clients.
We offer a full portfolio of services across many industries,
providing solutions in Business Analysis, SAP. We have grown to become
one of the fastest growing staffing companies on the East coast and
have a client base among the Fortune 500 companies. We also provide
training to our employees and our in-house training program runs for
4-5 weeks and here we train and prepare candidates in SAP, Business
Analysis or other technologies. Accommodation will be provided during
the training period and up until you are placed on your first project.
Our employees work in several skills including Web Technologies,
Database Administration, Systems Administration, ERP, Data
Warehousing, Business Analysis and Quality Assurance. Our Commercial
clients are usually in the Telecom, Banking, Health Care and Insurance
fields and are mostly Fortune 500 companies such as TCS, IBM, Wipro,
Patni Computers, etc.
When on project, our employees receive an annual salary plus benefits
such as Medical Insurance, Life insurance and Paid Vacation. We
sponsor H-1B visas and Green Cards for our employees and have a 100%
approval rate in such services. Please find attached a brochure about
our company and also the list of documents required to process the H1-
B. If you are really interested in taking a job with us, then we can
discuss in details the complete procedure. Please feel free to contact
us if you need any further information.
Regards,
Niharika