Results 1 to 3 of 3
  1. #1
    Star Lounger
    Join Date
    Apr 2001
    Location
    Naperville, Illinois, USA
    Posts
    61
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Access Runtime Packager (XP Developer)

    I have a application that consists of 2 Access databases. When I use the Packaging Wizard to setup w/o installing the Runtime Access it works okay. However, when I add the Access RunTime files, I get a Path/File Access error when trying to install on another computer. I don't know how to debug the setup.lst.

    Below is a copy of the setup.lst. Is this a problem with the Miscrosoft Installer program that some are warning us about? Do the other installation programs allow you to include Runtime Access as part of the setup process?

    Any help would be appreciated.

    Alan


    [Bootstrap]
    SetupTitle=Install
    SetupText=Copying files, please stand by.
    CabFile=BTS03.cab
    Spawn=Setup1.exe
    Uninstal=odeunst.exe
    TmpDir=msftqws.pdw
    Cabs=1

    [Bootstrap Files]
    File1=@ODSTKIT.DLL,$(WinSysPathSysFile),,,11/3/98 12:00:00 AM,101888,6.0.82.67
    File2=@COMCAT.DLL,&(WinSysPathSysFile),$(DLLSelfRe gister),,11/3/98 12:00:00 AM,22288,4.71.1460.1
    File3=@stdole2.tlb,$(WinSysPathSysFile),$(TLBRegis ter),,12/7/99 6:00:00 AM,16896,2.40.4512.1
    File4=@asycfilt.dll,$(WinSysPathSysFile),,,12/7/99 6:00:00 AM,147728,2.40.4512.1
    File5=@olepro32.dll,$(WinSysPathSysFile),$(DLLSelf Register),,12/7/99 6:00:00 AM,164112,5.0.4512.1
    File6=@oleaut32.dll,$(WinSysPathSysFile),$(DLLSelf Register),,12/7/99 6:00:00 AM,614672,2.40.4512.1
    File7=@msvbvm60.dll,$(WinSysPathSysFile),$(DLLSelf Register),,12/7/99 6:00:00 AM,1384448,6.0.84.95

    [Language]
    LangID=1033

    [IconGroups]
    Group0=BTS03
    PrivateGroup0=True
    Parent0=$(Programs)

    [BTS03]
    ShortcutPath1=""$(ARTFolder)MSAccess.exe" /Runtime "$(AppPath)devBTS03.mdb""
    IconImage1=
    Title1=devBTS03
    StartIn1=$(AppPath)


    [Setup]
    Title=BTS03
    DefaultDir=$(ProgramFiles)BTS03
    AppExe=$(AppPath)devBTS03.mdb
    AppToUninstall=$(AppPath)devBTS03.mdb

    [Setup1 Files]
    File1=@devBTS03.mdb,$(AppPath),,,1/23/2003 10:27:57,15048704,0.0.0.0
    File2=@new2.ico,$(AppPath),,,8/16/2000 0:0:0,766,0.0.0.0
    File3=@devBTS03_be.mdb,$(AppPath),,,1/17/2003 12:55:48,598016,0.0.0.0

    [Runtime]
    Included=-1
    OSPIncluded=-1
    OSPLCID=1033
    IEIncluded=0

    [RunCommands]

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Access Runtime Packager (XP Developer)

    Exactly what error are you getting? Path/file access on what, can you tell? If the setup runs without the runtime files, does the application run on the target machine? If Access is installed on the target machine, you may be trying to overwrite the installed files for Access, which can cause a lot of problems. The runtime files should always be installed in their own folder, separate from the application and from the Office folders. Are you running the installation on the same version of Windows as your development machine? Is there an earlier or later version of Office/Access installed on the target machine?
    Charlotte

  3. #3
    Star Lounger
    Join Date
    Apr 2001
    Location
    Naperville, Illinois, USA
    Posts
    61
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Access Runtime Packager (XP Developer)

    I have been experimenting with the package wizard. I get this error at the end of the installation. It appears that everything installed, including the entry in the Start Programs menu. The program works. It just comes up with a dialog box at the end of the process. After clicking through., I did get another error message: Runtime error 75 in a box titled Visual Basic 6.0 Setup Toolkit.

    The program consists of two .mdb databases linked together. I also did a package that only had the data database and runtime. It installed okay - no error message. In that setup, I did set the files as being shared. In neither case, did I specify a program to run at the end.

    Well, with egg on my face, I did find a description in the Microsoft Knowledgebase. Apparently this is a known problem when installing on a Win98 computer. Their solution is to install the XP Developer Service pack 1. I thought I had done this already but I must of missed something.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •