Updating Office 2003 with SP2...can lead to error if don't?

[Guest]

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]

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.

 

[Guest]

Thanks John.
The code that gives the error its very simple. Is the one behind an unbound
combobox that will list all the visits patients had. Once you choose from the
combo box one value in its list (click event), it will use values in
clomun(0) and column(1) to retrieve data from one of the table and repopulate
the form so that user can see or modify data. What is happening is that you
get the error for let say patient 2 and 5 and not for any other patients.
Plus I don't get the error ever on my pc. Others dont' get the error if
working with the Runtime version of Access. Just who doesn't use the runtime
version get the error (and not for the same patients!!). Really tricky, isn't
it?