PDA

View Full Version : Access 97: IDDA3532.dll as default



NewsArchive
01-25-1997, 01:00 AM
David Bogartz wrote:
>
> Brad Bode <brad.bode@born.com> wrote in article <32E520B7.1BC3@born.com>...
> > Has anyone used Installshield Express Pro with Access 7.0 runtime ? I
> > have a list of files needed from the Access Developers Toolkit, but Im
> > not getting registry entries correct.
>
> I'm going to be doing this pretty soon. It would be amazingly valuable to
> hear a little bit more about your successes and failures.
>
> --
> David Bogartz <bogartz@instinctive.com> http://www.instinctive.com
> Instinctive Technology, 725 Concord Ave., Cambridge MA 02138 USA
> Voice: 617 497 6300 x121 Fax: 617 497 5055
Hello,
I've been trying to do this for about 6 months. I am using IS3 Pro.
I could get filelist and most of the registries, but couldn't get
licensing stuff to work.

InstallShield promised to have an example about 4 months ago, but
I haven't heard from them at all. Too bad because a lot of people
would like to have it. Look at the Compuserve IS and Access forums,
You'll find at least 10 requests for Access runtime setup. That
number is steady, meaning that more and more people (InsatallShield
customers) want it.

At this point we are combining IS and Setup Wizard. Let me tell you
it is a pain in the ....

Good Luck.
If you find anything, PLEASE let me know.

Yuriy Kotlyar
Applied Voice Technology
Pomona, CA

NewsArchive
09-20-1998, 12:00 AM
Hi,

Anyone who knows how to get IS 2.03 to install the BDE so that it uses
DA3532.DLL instead of IDDAO32.DLL when accessing Access 97 databases?

It seems to me that idapi.cnf still references IDDAO32.DLL, and I don't know
how to change that.

Thanks, Ronald Ruijs

ruijs@rvc.nl

NewsArchive
09-21-1998, 12:00 AM
On Sun, 20 Sep 1998 16:41:03 +0200, "Ronald Ruijs" <ruijs@rvc.nl> wrote:
>Anyone who knows how to get IS 2.03 to install the BDE so that it uses
>DA3532.DLL instead of IDDAO32.DLL when accessing Access 97 databases?

Modify the IDAPI.CNF with BDE Administrator and set the DLL32 value to
IDDA3532.DLL. Also select the option to save the file for Windows 3.1. This
ensures that ALL values are written into the CNF file.

Stefan Paetow
InstallShield Software Corp.

NewsArchive
10-01-1998, 12:00 AM
Stefan

Exactly which cnf file(s) (redist, redist\bde5 etc) need changing ?

--
Andrew Tully
LSC Group


InstallShield Software Corporation wrote in message
<3606c634.231898302@news.installshield.com>...
>On Sun, 20 Sep 1998 16:41:03 +0200, "Ronald Ruijs" <ruijs@rvc.nl> wrote:
>>Anyone who knows how to get IS 2.03 to install the BDE so that it uses
>>DA3532.DLL instead of IDDAO32.DLL when accessing Access 97 databases?
>
>Modify the IDAPI.CNF with BDE Administrator and set the DLL32 value to
>IDDA3532.DLL. Also select the option to save the file for Windows 3.1. This
>ensures that ALL values are written into the CNF file.
>
>Stefan Paetow
>InstallShield Software Corp.

NewsArchive
10-02-1998, 12:00 AM
On Thu, 1 Oct 1998 15:17:45 +0100, "Andrew Tully" <ajt@lsc.co.uk> wrote:
>Exactly which cnf file(s) (redist, redist\bde5 etc) need changing ?

IDAPI.CNF and if you have it, IDAPI32.CNF. You can load these with BDE
Administrator and rename them back afterwards.

Stefan Paetow
InstallShield Software Corp.

NewsArchive
06-12-1999, 12:00 AM
First, let me say that Paul is doing an outstanding job in trying to help me
get my Access 97 app published.

I would like to add a few comments to his posting, if I may.

I purchased this product after seeing a news release entitled "Microsoft®
Access 97 Support and Advanced Dependency Checking Added to InstallShield®
ExpressT".

Imagine my surprise when I purchased the product, and it didn't find a
single dependency in my Access 97 database!

Not one... not a OCX, not a DLL Reference, not a ODBC Driver, not a DSN, not
one single dependency was picked up by Installshield.

It installed the Runtime files, but that is really no different than the
Microsoft Setup Wizard, and not even needed for my application.

In addition to not picking up the OCX's or ODBC DSNs, there are several
other issues that I would like answers for.

Access 97 is one of the most popular development platforms for front-ends
for SQL Server and Oracle databases, both of with require an ODBC driver and
DSN.

Having an Access 97 implementation without ODBC support is like having the
Lone Ranger without Tonto, or Hillary without Bill.

If you use an Access97 project in Installshield, you cannot even add an ODBC
component. If I wanted to make sure that the Access (or other) ODBC driver
is installed, I can't do this, because the ODBC component is completely
neglected on the Access 97 implementation of Installshield.

Setting up a DSN is also not implemented in the Access 97 implementation.
To do it, you have to manually add the registry entries, and pray that the
person already has the driver installed.

Other objects that should be available in the Access 97 project are
inexplicably missing.

For instance, If I use an OCX or DLL that depends on the VB Runtime files, I
should be able to select the VB Runtime object. No such object exists in an
the Access 97 project.

If I want to use ADO or another MDAC component, I can't select the MDAC
object to install, because no such object exists.

The absence of these objects in the Access 97 implementation makes no sense,
since they are present in all of the other implementations.

It seems to me that they could have been easily added, since they use the
exact same dependencies as the VB objects.

I'm really hoping that someone there can tell me that I'm doing something
wrong and that your product really does all of these things that it seems
that it should do.

If I am doing something wrong in my install, and I simply missed seeing
these features on a menu somewhere, please let me know.

If not, I really need to see a white-paper on performing these tasks in a
Access-97 implementation of Installshield.

If it's true that Installshield does not handle these concerns, then I am
struggling to see any practical difference between Installshield and the
Microsoft Setup Wizard when it comes to deploying Access 97 apps.

Thanks,

Rob Hudson
972-578-0058
1630 Laurel Lane
Plano, TX 75074


paul <paulw@installshield.com> wrote in message
news:376039ff.0@news.installshield.com...
> Hi All,
>
> Does Express2.12 suppose to pick up all the ODBC and OCX file for Access97
> project? A customer complain that
> we only pick up some rumtime file for his project.
>
> Thank you!
>
> Paul
>
>

NewsArchive
06-25-1999, 12:00 AM
Perhaps the support is incomplete due to a licensing issue? I was always
under the impression that one has to have purchased MS Office Developer
Edition in order to legally package Access databases. Buying Installshield
Express would not seem to impart any license to distribute the Access
runtime files that MS owns in such a case.

Keith E. Risler
keith_risler@zdnetmail.com

paul <paulw@installshield.com> wrote in message
news:376039ff.0@news.installshield.com...
> Hi All,
>
> Does Express2.12 suppose to pick up all the ODBC and OCX file for Access97
> project? A customer complain that
> we only pick up some rumtime file for his project.
>
> Thank you!
>
> Paul
>
>

NewsArchive
06-25-1999, 12:00 AM
Nope, that's not it.

The message that I posted detailing my complaint was inexplicably deleted
from the newsgroup.

I own the MS-ODE, and Installshield did an acceptable job bringing in the
run-time files.

What I'm talking about are the "other" files... like OCX's and referrenced
DLL's.

Also, there is no way to add the ODBC components and no way (short of
manually creating registry entries) to add a DSN.

My chief complaints are:

* The Access 97 InstallShield project should scan the mdb and bring in
automatically any linked datasources, including linked mdb's, ODBC DSN's,
and ISAM files.
* It should also pick up all OCX files and referrenced DLLs, scan their
dependency files, and bring in their dependencies as well.
* The Access 97 InstallShield project should include a ODBC object with the
ability to easily create a DSN
* The Access 97 InstallShield project should include a VB Runtime object
(for OCX's or DLL's that require the runtime files)
* The Access 97 InstallShield project should include the MDAC object in
case you want to use ODBC 3.51 or use ADO in your code.
* The Access 97 InstallShield project presents a false and misleading
warning when building your disk if you use the <DATABASEDIR> specifier in a
registry value.

Installshield actually responded to the now deleted message and basically
said that "they are sorry for the inconvenience", but that InstallShield
Express isn't capable of any of these things.

I haven't received any communication since then.

Thanks for the idea though!

Rob Hudson
972-578-0058


<hk@cal.com> wrote in message news:37731bb0.0@news.installshield.com...
> Perhaps the support is incomplete due to a licensing issue? I was always
> under the impression that one has to have purchased MS Office Developer
> Edition in order to legally package Access databases. Buying Installshield
> Express would not seem to impart any license to distribute the Access
> runtime files that MS owns in such a case.
>
> Keith E. Risler
> keith_risler@zdnetmail.com
>
> paul <paulw@installshield.com> wrote in message
> news:376039ff.0@news.installshield.com...
> > Hi All,
> >
> > Does Express2.12 suppose to pick up all the ODBC and OCX file for
Access97
> > project? A customer complain that
> > we only pick up some rumtime file for his project.
> >
> > Thank you!
> >
> > Paul
> >
> >
>
>