Access 2003 Runtime Issue

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I created an Access DB in Access 2002 and Upsized it to a SQL Server DB. I then published a runtime version of the application using the Access 2003 Developers extenions. When this is installed on some Windows 2000 based machines running Office 2002, the app runs fine. On other Win 2K boxes with Office 2002, we receive the message that the app is referencing a missing or broken link to OCW10.DLL and the app will not run. All machines were installed from the same media. Anyone have any ideas on what it is complaining about? This is our first venture in running Access Runtime across multiple users.
 
The OCW10 file is for web components of office. Likely, some pc's have the
web components installed,a nd others do not.

However, if you runtime is NOT using xml, then you need to go to the
tools->references and remove AS MUCH AS possible.

I am sure you are aware that broken references is one of the MOST common
questions here. If your code uses any part of office (like word, excel etc),
then you need to use late binding.

Note that the OCw10.msi is on the office 2002 cd, and I suppose you could
install it on those problem pc's that have office 2002. however, what you
really should do is check the references in your database BEFORE you build
the runtime...
 
Albert D. Kallal said:
The OCW10 file is for web components of office. Likely, some pc's have the
web components installed,a nd others do not.

However, if you runtime is NOT using xml, then you need to go to the
tools->references and remove AS MUCH AS possible.

I am sure you are aware that broken references is one of the MOST common
questions here. If your code uses any part of office (like word, excel etc),
then you need to use late binding.

Note that the OCw10.msi is on the office 2002 cd, and I suppose you could
install it on those problem pc's that have office 2002. however, what you
really should do is check the references in your database BEFORE you build
the runtime...


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.attcanada.net/~kallal.msn
Click to expand...
 
The problem was in fact a reference to XP Web Components that was included by default but not required. Thanks for pointing us to it.
 
IraKeener said:
The problem was in fact a reference to XP Web Components that was included
Click to expand...
by default but not required. Thanks for pointing us to it.

You are most welcome, and thank you for posting back..as now people can
goggle for this answer...
 
Back
Top