DNS creation problem

[bendrouet]

Hi,

I have a DNS creation problem on a VmWare Windows 95 system.

The code I use to test this is very simple.
I copy a file ODBCJT35.DLL (this file generates errors when it is copied in the System directory of the target but I have to ensure that all my tests are reliable before posting a new thread on it) in the Targetdir of the installation program and I create a folder DATABASE containing my 2 databases.

Then 2 DNS are created (using CREATE ODBC DNS command) to point to the databases installed.

I tried my program on Windows 98 and all works perfectly. All the files are copied and the 2 DNS are created in the System DNS tab of the ODBC admin console.

But when I try to use the same program on Windows 95 VmWare, I have this error message (nevertheless the files are copied) :

"Error configuring ODBC datasources XXX (name of the DNS), ODBC error 13. Impossible to load the installation library or converter. Check that XXX exists and you can access it."

I get the same message for the 2 DNS.

I should point that the command CREATE ODBC DNS is executed after the command install files for my databases.
All the code is entered in the [OFFLINE CONTENT] section

Have you any idea why it crashes for W95 ?


thank you

[MichaelNesmith]

Hi!

The Windows 95 system may be missing required ODBC drivers or support files. You may want to install the latest MDAC update together with your setup on Windows 95.

[bendrouet]

Hi,

Like you say, I verified the W95 vmware configuration. On the Odbc admin console I have on the "Odbc driver" tab this information :

Microfsoft Access Driver (*.mdb) 4.00.6019.00 Microsoft Corporation odbcjt32.dll 01/04/06

i also verified the existence of the odbcjt32.dll in the Windows\\System directory.

So it seems that the system can work with access databases.

The attributes used for the creation of the DNS are these :

DBQ=[TARGETDIR]\\DATABASE\\ADMDB.MDB
DriverId=25
Exclusive=1
JetIniPath=odbcddp.ini
UID=admin
MaxBufferSize=1024

So the installation works (files copied and DNS created) on VmWare 98 but not on W95.

I also tried To add the MDAC Refresh 2.8 for the W95 installation but it generates this error message :

This product requires at least Windows 98
Setup cannot continue


Why should I do to install my DNS on a W95 system ?

best regards

[MichaelNesmith]

Hi!

I would try and find if Windows 95 has updates you may need to install. You may want to install an older MDAC version that is available for this platform - MDAC 2.7, 2.5 come to mind. These are available from the Microsoft web site and you may add them to your setup and run them using the Run Program command in your setup script.

[bendrouet]

ok,

I will try older MDAC and I will give you feedback about my tests.

thank you

[bendrouet]

Hi,

I have downloaded the MDAC 2.5 on the microsoft website and included it in my installation program

Here is the code sequence I used for that : (section OFFLINE CONTENT)

Install Files .........MDAC_TYP_Fr.EXE to $TARGETDIR$
Run Program $TARGETDIR$\\MDAC_TYP_Fr.EXE (WAIT)
Delete Files $TARGETDIR$\\MDAC_TYP_Fr.EXE (when installing and uninstalling)

...then comes the instructions for the database files installation and the DNS creations.

There is no condition on the version of the target system so these lines of code are surely executed.

When the programs runs on a WXP system, the MDAC is copied in the TARGETDIR but not executed ! (no error message saying me that I have a better version on XP and that it is not safe to install the old MDAC)
So I test with a result variable for the run program instruction but the result is 0. I don't know what it means.

On the vmWare 95 system it is the same and of course I have the same error messages like before because the MDAC or something else is missing.

Is there any solution to create DNS on Windows 95 ?
Is there a relation between DNS System and Windows 95 ?
Should I create User DNS instead of System DNS ?

[MichaelNesmith]

You need to insert the command for Run Program after Apply Install. Until Apply Install executes, none of the purple commands in your setup script (default highlighting) execute - these are the MSI commands in your script. This is why Run Program doesn't work, it cannot find anything to run.

In your case, the better solution is to add the file as a Support File (also called Creative in the visual view). This way you can run it directly using Run Program from the $SUPPORTDIR$ folder, without waiting for Apply Install to execute. Support Files are intended specifically for files like your MDAC 2.5 install which are only needed at install time. So there is no need to manually install them and then remove them - just add them as a support file, and run them directly!