Re: Couldn't find installable ISAM error from VB 6 / Access 2003


<stacy@xxxxxxxxxxxxxxxx> wrote in message
news:1131735946.213739.272560@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Time to cuss - no, no I won't do that since you are kind enough to try
> to help. The sp5 install didn't work, so I installed vp6 and still
> have the same results. My version of MSVBVM60.dll is 6.0.97.82 which
> didn't change when I installed the other service packs, should it have?
> If so, in which location?
>
> I have a question regarding DAO350.dll, I generated a dependencies file
> with the Package and Deployment Wizard on the original app and that
> file lists DAO360.dll version 3.60.8618.0 as a dependency. Was your
> suggestion about dao350.dll was based on the references list? I also
> noticed that I can un-register DAO350.dll numerous times without any
> errors, the regsvr32 always says the unregister was successful, that
> makes me wonder what is really happening. Why can I unregister a dll
> that was already unregistered, maybe I just don't understand what
> unregister does. The register is also successful. Seems I can't fail
> there!!
>

The point about the DAO350.dll is that DAO "controls" use it, although in
your application you might actually be referencing the 3.6/x DAO 'Data
Access Library'. It can cause problems since it is occasionally not
registered correctly with some Jet 4.0 installs. A similar issue came up
recently and it was on my mind.

When you register a dll it merely makes various entries for COM to use in
finding the correct DLL. When you unregister a DLL, it merely removes those
entries for that DLL. So yes it will always report success if it in fact
remove an entry or if it didn't find one.

However, it will not necessarily remove another 'similar' registered
versions of that DLL. (A bizarre situation) So it is often useful to open up
Ole Viewer and peek at what is registered. But I doubt if this is what is
wrong in your case.

Let's go over it again. And see if I understand the current situation...
(Forgetting for a moment the 'old' application.)
If you create a simple single form app and use DAO 3.6 to access a MSAccess
2003 database, and place a DAO Data Control on the form, you get a "can't
find installable ISAM" error.
You are running WinXP/SP2.
You are using VB6 SP6 (upgraded to latest 'n greatest)
You have installed the latest 'n greatest Jet 4.0 and MDAC packages for
WinXP.
You checked and dao350.dll is registered.
Yet you still can not compile.

What is bizarre is that if you run the setup package to install the app, it
runds correctly. Therefore we are assuming that anything missing would have
been installed by the package and therefore equally available to any
subsequent attempts to compile and run?

Does this describe the current situation accurately?

If you still have the old P&D files that created the package, send the
contents of the Setup.Lst and the <projectname>.DDF file (found in the
package folder) - perhaps there is a clue in there.

-ralph


.

Relevant Pages

  • Re: Installing COM add-in
    ... It looks as though you need admin priv to register the DLL ... > You don't need admin rights to install, just user rights to install new ...
    (microsoft.public.outlook.program_vba)
  • Re: Self registering a COM dll in a VS2003 Windows setup project...
    ... Most of the Register settings extract the settings at build time and put the ... at install time. ... code in that DLL is doing something that isn't being put into the MSI file. ... I have not been able to make a customized Redemption dll ...
    (microsoft.public.dotnet.framework.setup)
  • Re: 429 ActiveX Component cant create Object
    ... dll object inside the application folder and not the system32 folder. ... >> package using VB pkg and depl. ... >> After a succesful install, the user runs the exe and the above subject ...
    (microsoft.public.vb.com)
  • Re: Installing components in D2005
    ... Deleting the Clocks.bpl does not do it, trying to install the components in a new package does not succeed, as f.ex. ... If you delete the BPL, then nothing will be registered because things only get registered when Delphi executes the Register procedures in the BPL. ...
    (alt.comp.lang.borland-delphi)
  • Re: Help and support only shows green arrows
    ... I am missing a few files that is needed to run the Help and support menu. ... I couldn't install them. ... *** You can register your HHActiveX.dll using the "Register a DLL" button. ...
    (microsoft.public.windowsxp.general)
Loading