It has been a long time since I worked with Oracle Forms, but the chances
are that you have encountered one of the following problems:
a. Word is failing to connect because there is a new security feature which
pops up a dialog box whenever Word does something that would result in SQL
execution. If Word has been invoked via OLE Automation, the pop-up is not
displayed and Word behaves as if the user chose not to connect. There is
more info. at
http://support.microsoft.com/default.aspx?scid=kb;en-us;825765
b. Word is failing because Word 2000 used ODBC to connect to Oracle
databases and for some reason Word 2003 has been unable to connect using
that method and the same connection info. You should be able to check
whether Word 2003 can connect successfully by opening the document manually
in Word 2003 and seeing what happens. If Word does not connect, you will
probably have to go through the connection process again, but be warned that
by default, Word 2002/3 uses OLEDB, not ODBC, to make these connections. If
you now have a mixed Word 2000/2003 environment, I would not attempt to
maintain one version of these Word files - create and maintain one for use
with Word 2000 and another for use with Word 2003 and maintain them
separately.
There could also be some problem with the specific mechanism Oracle Forms
uses to initiate Word (are you using ole.invoke ?) or problems if your old
documents were using macros written in WordBasic. I don't have anything
specific in mind on those fronts though.
Peter Jamieson
