Re: Error 2356 in AccessRT.msi

Tech-Archive recommends: Speed Up your PC by fixing your registry

Paul:
All of the following is with Access 2003 ONLY.  (NOT 2002)

I sort of solved the problem. When I moved the AccessRT.msi and the AccessRT.ca_ to another folder, it works. Now I do not understand why this is. So let me ask a couple of quick questions.

First, where am I suppose to get the original AccessRT.msi and the AccessRT.cab? I first use the Dev. Studio Tool Kit to make a simple setup package. (ie. it creates a file on my D: drive with the app name and the date (D:\fBlds\v346\WBS_2005-04-11) In this folder there is a sub folder called files and in there is the AccessRT.msi and the AccessRT.cab. I take these and move them to a new folder called A2003 and then perform the steps you describe. This is when I get the error message 2356 we have been discussing.
Now, if I move those exact same two files (AccessRT.msi and the AccessRT.ca_) to the C: drive (C:\Builds) then the error goes away and I am able to create a nested install exactly like your directions.

So here is my question. Where am I suppose to get the original AccessRT.msi and the AccessRT.cab files? Are they on the Access 2003 CD and/or the Dev. Studio CD? (I found the AccessRT.msi on the Access 2003 but not the AccessRT.cab)
Once I find them, is there a specific folder (directory) I should be placing them in?

This is almost the end. Now that I am closer to getting this resolved, I am almost done.


PS. I am a little scared of the Access 2003 security. I do not want that warning window popping up (it will scare the hell out my clients). I can not trust that changing the the registry values on installation will never change (what if down the road the user or another app changes the security level back to Medium). I can't help but think that this is just a headache waiting to happen. That is why I first thought about Access 2002. But I'm going with your advice that 2003 is better.


Thank you for your patience and help in this.

Dex

Paul Overway wrote: 
Dex:

If you haven't done so already, I'd suggest starting over with a new copy of ACCESSRT.MSI. Add the cab(s) again using msidb and be mindful of case when you do the media table edit. At this point, it isn't clear to me which version of ACCESSRT.MSI you're working with (i.e., 2002 or 2003)...and maybe that is an issue?

In respect to shortcuts, make sure you have the most recent script examples...I recently made a change for shortcut creation and included a PostInstall example. But to create a shortcut on the start menu, you'd use AllUsersStartMenu. I've also made some updates to reflect some of the comments you've made and issues encountered. My example puts the shortcut on the desktop, but you'd just modify it to AllUsersStartMenu and tack on any folder you want it in.

The idea behind a remove procedure or script is to ensure that the user actually gets the files you want installed, because there is no option to overwrite document type files...which includes MDB/MDE files. So, you either need to write a script that deletes those files for any previously installed version of your app OR...and this is how I do it, create an IExpress package and use the file overwrite option it includes. However, if you go the IExpress route, you'll have to use a fixed install path for your app. Going the IExpress route also makes the I2G package a little more bloated, but has the advantage of not causing an alarm with AV software (from what I've seen).

Yeah, I definitely got an education using these tools, but it was worthwhile. You should be able to apply what you learn to future packages easily though...I have.

.

Relevant Pages

  • Re: Installing data files with application?
    ... Have Setup install the files into your APP FOLDER. ... Create a Setting in your app called FirstRun and scoped to USER. ... I dont see where the zip thing totally solves the problem. ...
    (microsoft.public.dotnet.languages.vb)
  • Labels & Envelopes by Chronos
    ... There's a feature in the app called a Graphics Drawer. ... one to install the app ... The first disk has an uninstaller and I used ... found a Chronos folder in my Applications Support ...
    (comp.sys.mac.apps)
  • Desktop icons when creating shortcuts
    ... I have installation package for a .NET app that works just fine. ... The only problem the users have is with the shortcut creation in that they ... but the icon displayed is not the one compiled into ... it is their corporate policy to not install any Win2000 ...
    (microsoft.public.win2000.setup)
  • Re: Design Guidelines for Non-Power Users?
    ... Non-Power Users and Admins will not be able to install your app. ... You can get whatever this folder happens to be by ... If they don't have write permissions, ...
    (microsoft.public.vb.winapi)
  • Re: Design Guidelines for Non-Power Users?
    ... Non-Power Users and Admins will not be able to install your app. ... You can get whatever this folder happens to be by ... If they don't have write permissions, ...
    (microsoft.public.vb.general.discussion)