Incorporate runtime updates to Dev packager? (Access 2k SP1)

Topic

New Reply

(Edited by Patricia W on 04-May-04 17:33. )

Amended Version Information: I have Access XP, not 2k, sorry. The reg. Access is SP2, and the Office Dev Tools are XP SP1, which is the highest patch they have for the XP Dev tools.

I see there is a new Office XP Service Pack 3 for Access 2002 Runtimes.
Is there a way — I hate like heck to go to applying patches to already installed runtimes — can I rebuild the .cab file with the updated versions of the file, then create the runtime, and would that be sufficient — or are there any problems you all can see with that? and, why doesn’t Microsoft put out an update to the .cab file itself — perhaps because the answer is not that simple?
I’m also assuming that a reinstall won’t copy over older runtime installs, that I’d have to uninstall and then reinstall, so it’s almost six of one, half-dozen of the other — but for newer installs, this would be helpful. thx, Pat W.

Reply | Quote

Replies

I’m not clear on what you’re asking. If you want to include the updates to the runtime in a cab file, you have to install the service pack to the runtime on the machine on which you build the setups, which may not be as easy as you might think. I’ve never managed to get it to install on my machine, but fortunately someone else in our office actually builds the installers. The patch is designed to be applied to installed runtimes, I believe.

Reply | Quote

> If you want to include the updates to the runtime in a cab file, you have to install the service pack to the runtime on the machine on which you build the setups,
…….. I assumed so, but there are no instructions from Microsoft on how to do that or if it is recommended, although I’ve found a lot of information on building a cab file, so, I think I can do it. I just wish there were either a patch to the Developer’s runtime files, or instructions on how to update it, or at least a blessing to developers to go ahead and _do_ that. Microsoft hasn’t been particularly XP Office Developer-friendly in this specific regard.

< The patch is designed to be applied to installed runtimes, I believe.
………..Right, it is supposed to be applied to installed runtimes, and I can do that. In fact, I _think_ I can trust the latest patch, "Art2002Sp3-kb834693-client-enu.exe" to include all the previous runtime updates — at least, it _seems_ to work. It would just be so nice if the KB article actually _said_ so, but it did leave out the precaution to install the two previous runtime updates, so, hopefully, this patch is cumulative.

thx
Pat

Reply | Quote

> If you want to include the updates to the runtime in a cab file, you have to install the service pack to the runtime on the machine on which you build the setups,
…….. I assumed so, but there are no instructions from Microsoft on how to do that or if it is recommended, although I’ve found a lot of information on building a cab file, so, I think I can do it. I just wish there were either a patch to the Developer’s runtime files, or instructions on how to update it, or at least a blessing to developers to go ahead and _do_ that. Microsoft hasn’t been particularly XP Office Developer-friendly in this specific regard.

< The patch is designed to be applied to installed runtimes, I believe.
………..Right, it is supposed to be applied to installed runtimes, and I can do that. In fact, I _think_ I can trust the latest patch, "Art2002Sp3-kb834693-client-enu.exe" to include all the previous runtime updates — at least, it _seems_ to work. It would just be so nice if the KB article actually _said_ so, but it did leave out the precaution to install the two previous runtime updates, so, hopefully, this patch is cumulative.

thx
Pat

Reply | Quote