Results 1 to 12 of 12

Thread: invalid data source

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Sep 2017
    Posts
    79

    invalid data source

    When the setup installation created using P&DW there is no error with the data report
    But i am getting the error " invalid data source" when the setup installation created using INNO at the line --

    DataReport.Show vbModal, Me

    Do i need to add the following dll in my INNO setup script

    MSDBRPTR.DLL

  2. #2
    PowerPoster
    Join Date
    Feb 2012
    Location
    West Virginia
    Posts
    14,205

    Re: invalid data source

    Look at the setup.lst file created by pdw the files that are listed there are the ones you need to get the same results.
    My advice would be to not use inno though

  3. #3
    PowerPoster
    Join Date
    Feb 2006
    Posts
    24,482

    Re: invalid data source

    Setup.lst can be way off if you haven't kept VB6DEP.INI up to date. That file must be manually updated to reflect changes over time, it was designed to support Windows 95 and many things need to be added to its [Do Not Redistribute] section.

    The updating must be done manually, based on 20 years worth of MS KB articles.

    Inno has no such knowledge base at all and requires omniscience and hypervigilence.

  4. #4

    Thread Starter
    Lively Member
    Join Date
    Sep 2017
    Posts
    79

    Re: invalid data source

    Thanks a lot for the reply.
    on scrutiny to file setup.lst under the -> Setup1 Files

    list of files added must be added to INNO setup. As listed in INNO...
    Ok but under the Setup1 Files list there is included
    MDAC_TYP.exe

    that (MS Data Access objects) file created during P&DW. Should that also need to be added in INNO script [Files]list ?

  5. #5
    gibra
    Guest

    Re: invalid data source

    Shows us the content of SETUP.LST file...

  6. #6
    PowerPoster
    Join Date
    Feb 2006
    Posts
    24,482

    Re: invalid data source

    MDAC_TYP.exe should not be deployed to anything newer than Windows NT 4.0 or Windows 98. As I said, your VB6DEP.INI is woefully out of date.

    For more details (the situation is more complex than this) see: Microsoft Data Access Components (MDAC) Installation.

    Beginning in Windows Vista MDAC is gone. It was replaced by Windows DAC and this is included in the OS.
    Last edited by dilettante; Dec 21st, 2017 at 10:30 AM.

  7. #7

    Thread Starter
    Lively Member
    Join Date
    Sep 2017
    Posts
    79

    Re: invalid data source

    #5 Setup.lst

    [Bootstrap]
    SetupTitle=Install
    SetupText=Copying Files, please stand by.
    CabFile=Analysis.CAB
    Spawn=Setup1.exe
    Uninstal=st6unst.exe
    TmpDir=msftqws.pdw
    Cabs=1

    [Bootstrap Files]
    File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,6/18/98 12:00:00 AM,102912,6.0.81.69
    File2=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 12:00:00 AM,22288,4.71.1460.1
    File3=@stdole2.tlb,$(WinSysPathSysFile),$(TLBRegister),,7/14/09 5:13:53 AM,16896,6.1.7600.16385
    File4=@asycfilt.dll,$(WinSysPathSysFile),,,11/21/10 2:59:06 AM,67584,6.1.7601.17514
    File5=@olepro32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,11/21/10 2:59:10 AM,90112,6.1.7601.17514
    File6=@oleaut32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,7/15/13 6:32:15 AM,571904,6.1.7601.17676
    File7=@msvbvm60.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,7/14/09 6:45:50 AM,1386496,6.0.98.15

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

    [Analysis]
    Icon1="Analysis.exe"
    Title1=Analysis
    StartIn1=$(AppPath)

    [Setup]
    Title=Analysis
    DefaultDir=$(ProgramFiles)\Analysis
    AppExe=Analysis.exe
    AppToUninstall=Analysis.exe

    [Setup1 Files]
    File1=@Output.xlsx,$(AppPath),,,12/19/17 5:31:03 PM,9393,0.0.0.0
    File2=@Analysis.xlsx,$(AppPath),,,12/19/17 5:31:38 PM,1229312,0.0.0.0
    File3=@icon(19).ico,$(AppPath)\Icons,,,10/31/17 1:09:56 PM,53910,0.0.0.0
    File4=@icon(18).ico,$(AppPath)\Icons,,,10/31/17 1:02:17 PM,75507,0.0.0.0
    File5=@icon(17).ico,$(AppPath)\Icons,,,10/31/17 1:00:11 PM,34089,0.0.0.0
    File6=@icon(16).ico,$(AppPath)\Icons,,,10/31/17 12:51:53 PM,35032,0.0.0.0
    File7=@icon(15).ico,$(AppPath)\Icons,,,10/31/17 12:42:40 PM,24903,0.0.0.0
    File8=@icon(14).ico,$(AppPath)\Icons,,,10/31/17 12:18:31 PM,24575,0.0.0.0
    File9=@icon(13).ico,$(AppPath)\Icons,,,10/31/17 12:15:43 PM,36662,0.0.0.0
    File10=@icon(12).ico,$(AppPath)\Icons,,,10/31/17 11:35:14 AM,34407,0.0.0.0
    File11=@icon(11).ico,$(AppPath)\Icons,,,10/31/17 7:13:35 AM,70830,0.0.0.0
    File12=@icon(10).ico,$(AppPath)\Icons,,,10/31/17 8:37:12 AM,20471,0.0.0.0
    File13=@icon(9).ico,$(AppPath)\Icons,,,10/31/17 8:20:48 AM,33845,0.0.0.0
    File14=@icon(8).ico,$(AppPath)\Icons,,,10/31/17 7:25:32 AM,27822,0.0.0.0
    File15=@icon(7).ico,$(AppPath)\Icons,,,10/31/17 8:02:20 AM,49188,0.0.0.0
    File16=@icon(6).ico,$(AppPath)\Icons,,,10/31/17 7:28:27 AM,30042,0.0.0.0
    File17=@icon(5).ico,$(AppPath)\Icons,,,10/31/17 7:17:22 AM,23437,0.0.0.0
    File18=@icon(4).ico,$(AppPath)\Icons,,,10/30/17 3:09:18 PM,15934,0.0.0.0
    File19=@icon(3).ico,$(AppPath)\Icons,,,10/31/17 7:09:00 AM,90565,0.0.0.0
    File20=@icon(2).ico,$(AppPath)\Icons,,,10/31/17 7:07:29 AM,44923,0.0.0.0
    File21=@icon(1).ico,$(AppPath)\Icons,,,10/31/17 7:05:38 AM,91436,0.0.0.0
    File22=@icon(0).ico,$(AppPath)\Icons,,,10/31/17 7:01:54 AM,54675,0.0.0.0
    File23=@hand.ico,$(AppPath)\Icons,,,10/11/05 10:26:00 AM,2238,0.0.0.0
    File24=@244.ico,$(AppPath)\Icons,,,10/31/17 6:49:03 AM,10462,0.0.0.0
    File25=@MDAC_TYP.EXE,$(AppPath),,,6/26/98 12:00:00 AM,8124720,4.71.1015.0
    File26=@Findtate.ocx,$(AppPath),$(DLLSelfRegister),$(Shared),10/31/17 8:02:07 PM,839680,2.1.0.32
    File27=@MSBIND.DLL,$(AppPath),$(DLLSelfRegister),$(Shared),6/18/98 12:00:00 AM,77824,6.0.81.69
    File28=@MSDBRPTR.DLL,$(AppPath),$(DLLSelfRegister),$(Shared),6/18/98 12:00:00 AM,299008,6.0.81.69
    File29=@MSDERUN.DLL,$(AppPath),$(DLLSelfRegister),$(Shared),6/9/98 12:00:00 AM,137216,6.0.0.3005
    File30=@Analysis.exe,$(AppPath),,,12/19/17 5:33:18 PM,27291648,1.0.0.0

    ; The following lines may be deleted in order to obtain extra
    ; space for customizing this file on a full installation diskette.

  8. #8
    PowerPoster
    Join Date
    Feb 2006
    Posts
    24,482

    Re: invalid data source

    These are already part of the OS as of at least Windows XP SP3 if not earlier (even Windows 98SE should have them):

    Code:
    File2=COMCAT.DLL
    File3=stdole2.tlb
    File4=asycfilt.dll
    File5=olepro32.dll
    File6=oleaut32.dll
    File7=msvbvm60.dll
    File25=MDAC_TYP.EXE
    Don't deploy them. Your VB6DEP.INI is out of date.

  9. #9

    Thread Starter
    Lively Member
    Join Date
    Sep 2017
    Posts
    79

    Re: invalid data source

    Thank you dilettante, for the quick reply and guidance.

    The files under [Setup1 Files]
    At sl 25 (Now i know it need not to be added) , 27,28, 29. Are these also included in OS. (XP )

  10. #10
    PowerPoster
    Join Date
    Feb 2006
    Posts
    24,482

    Re: invalid data source

    Excel documents can also be incredibly problematic:

    Code:
    File1=Output.xlsx
    File2=Analysis.xlsx
    Unless your program is very careful to open these strictly read-only you will either run into filesystem virtualization (appcompat) or die on a security violation (if your program is marked Vista aware).

    You also haven't deployed the necessary ACE Provider to read them via ADO. The only legal way to do this is via the official MSI package, so you'd have modify your setup to chain to that install. This isn't necessary if all users are required to have Office 2007 or later preinstalled though.

  11. #11
    PowerPoster
    Join Date
    Feb 2006
    Posts
    24,482

    Re: invalid data source

    Read: Support Statement for Visual Basic 6.0 on Windows.

    Skip down to the sections:

    Supported and shipping in Windows, and

    Supported runtime files to distribute with your application

    As hinted in the Executive summary there, nothing before Windows 7 SP1 is considered supported at all anymore. Thus there is no such set of lists for the earlier dead OSs any more.

  12. #12

    Thread Starter
    Lively Member
    Join Date
    Sep 2017
    Posts
    79

    Re: invalid data source

    dilettante,
    'MSDERUN.DLL' is listed under - Unsupported runtime files // Ref #11

    That means the dll is no more supported in Windows Server 2008 or later. Right ?

    If it is true. Then the file created in P&DW is actually not installed during installation in Win 7 (My test Machine). Right?

Posting Permissions

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



Click Here to Expand Forum to Full Width