This is probably an easy question, but I haven't found the answer, so
hopefully someone can point me in the right direction.
I have a database developed as Access 2002 developers (SP1).  I used the
packaging wizard to distribute the program.  I am now inconsistently
receiving errors that shut Access down on the runtime version and on the
developer's computer.  The errors always point to msjtes40.dll, so I figure
it must be corrupt of have some other problem.
I found that it is from the SP6 release of Jet.
I can install the Jet update on the developers computer to resolve the issue
with the .dll file, but how should I fix the problem on the end computer?
Do I need to create a new package after the update is installed on the
developer's computer and re-install the entire package on the end user
computer?  Will this override the files currently there, or will there be a
conflict?  Or, do I need to install the Jet SP8 to each end user computer
instead of a complete new package?

Thanks in advance for the advice.

Lori