Re: Updating Office 2003 with SP2...can lead to error if don't?
- From: John Nurick <j.mapSoN.nurick@xxxxxxxxxxxxxx>
- Date: Thu, 24 Aug 2006 07:09:17 +0100
Hi Rocco,
Yes, there are bugs in the original Office 2003 that were fixed in the
service packs. The package wizard will (as I understand it) use the
updated files from the service packs, so when you install the run-time
it will be up to date. So probably the first troubleshooting step would
be to update the other computer.
Apart from that, one would need to know what code was producing what
errors in order to make useful suggestions.
On Wed, 23 Aug 2006 14:10:02 -0700, rocco
<rocco@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hello,
is there any chance that a Database coded on a pc with Office 2003, Visual
Studio 2003 and all the latest updates installed can run fine and the same
database when run on a pc that has office 2003 installed, but not updated,
gets error?
We are facing a very strange behaviour...
If I deploy the db with the package wizard AND the runtime version of
Access, it works fine. But if I just give the .mde and run it on a pc which
has all the suite Office 2003 installed but not updated, the application
fires a runtime error when using some features.
References seems fine. I have used a code posted in this forum which I
re-post because I think it can be helpful:
Private Sub Form_Load()
DoCmd.ShowToolbar "web", acToolbarNo
Dim refCurr As Reference
Dim STRINGA As String
For Each refCurr In Application.References
If refCurr.IsBroken = False Then
STRINGA = STRINGA + vbCrLf + "Name: " & refCurr.Name & " is found at "
& refCurr.FullPath
Else
STRINGA = STRINGA + vbCrLf + "You have a broken reference to GUID " &
refCurr.Guid
End If
Next refCurr
Set refCurr = Nothing
MsgBox STRINGA
End Sub
The path for each reference is fine other than for minus differences due to
the fact that the user has Office 2003 (italian version) while I 'm working
with the US version, So part of the path will differ despite it leads to the
same place (i.e. instead of having C:\Program Files the user has
C:\Programmi), which I don't think can cause the error. Is it possible that
this differences depend from not having the user installed the SP2 for Office
2003?
Thanks,
Rocco
--
John Nurick [Microsoft Access MVP]
Please respond in the newgroup and not by email.
.
- Follow-Ups:
- Prev by Date: Re: Using Call Shell to open Excel Workbook within Access 2003, SP2 Ve
- Next by Date: Re: environment variables
- Previous by thread: Re: Using Call Shell to open Excel Workbook within Access 2003, SP2 Ve
- Next by thread: Re: Updating Office 2003 with SP2...can lead to error if don't?
- Index(es):
Relevant Pages
|
