VB 4.0, Windows 3.1 and dead Acces 2.0 
Author Message
 VB 4.0, Windows 3.1 and dead Acces 2.0

Quote:

> Hi!

> I used VB4.0 - 16 bit to compile my application, which uses a .MDB
> created with Access 2.0. This application works fine on my machine,
> with Windows95, but when I try to install it on another one, with
> Windows 3.1, I get the following error during installation:
> System DLL 'DDEML.DLL' could not be loaded

> and the installation is aborted.

> After this when I try to run Access, I have this error:
> This application requires a newer version of Windows

> and it doesn't load...

I've seen this before.  You've installed .DLLs specific to Win95.  When
Access sees these (under Win 3.1) after the installation, it realizes
that some .DLLs are newer than they should be.  For core .DLLs, install
the minimum required (Win 3.1 ones dated 8-15-95).  If you're not using
VB 4's SetupWiz for your installation, try using it only for the purpose
of obtaining a base list of .DLLs, etc. that should be installed (see
the file SETUP.LST created during the creation of the installation).

-Chris W.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CWW Development Company      | http://www.*-*-*.com/ ~chriswsj
VB Spell Checking, Nutrition Analysis, Football Pool! & More!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



Sat, 09 Oct 1999 03:00:00 GMT  
 VB 4.0, Windows 3.1 and dead Acces 2.0

Hi!

I used VB4.0 - 16 bit to compile my application, which uses a .MDB
created with Access 2.0. This application works fine on my machine,
with Windows95, but when I try to install it on another one, with
Windows 3.1, I get the following error during installation:
System DLL 'DDEML.DLL' could not be loaded

and the installation is aborted.

After this when I try to run Access, I have this error:
This application requires a newer version of Windows

and it doesn't load...

Any one has some idea how to solve this?

Many thanks!

--
Pedro Ferreira
PNF Informtica
Voice / Fax: (351) 1 362 33 55



Sat, 09 Oct 1999 03:00:00 GMT  
 VB 4.0, Windows 3.1 and dead Acces 2.0

This is a common problem. The only safe solution appears to be to develop
applications that may be run under WIN 3.x on a machine running WIN 3.x.
These applications will run under WIN 95 without causing the problems
referred to as WIN 95 is more intelligent when overwritting files with
older versions of DLLs etc.



snip >

Quote:
> I used VB4.0 - 16 bit to compile my application, which uses a .MDB
> created with Access 2.0. This application works fine on my machine,
> with Windows95, but when I try to install it on another one, with
> Windows 3.1, I get the following error during installation:
> System DLL 'DDEML.DLL' could not be loaded
> and the installation is aborted.
> After this when I try to run Access, I have this error:
> This application requires a newer version of Windows
> and it doesn't load...

snip>


Fri, 15 Oct 1999 03:00:00 GMT  
 VB 4.0, Windows 3.1 and dead Acces 2.0

I had a similar problem, which was due to the fact that the VER.DLL from my
Windows 95 machine was copied to the PC with Windows 3.x. I got hold of a
copy of VER.DLL from a WINDOWS 3.x pc and copied it onto the 'faulty'
machine, everything workd OK



Sun, 17 Oct 1999 03:00:00 GMT  
 
 [ 4 post ] 

 Relevant Pages 

1. .Wav sound access under Windows 3.1 for VB 4.0

2. VB 4.0 - EXE in Windows 3.1 ???

3. Restarting Windows 3.1 in VB 4.0

4. VB 4.0 Pro for use with Windows 3.1 only

5. Q: VB 4.0, 16 Bit, Windows 3.1, GPF VBA2.DLL

6. Netware 3.1 , Windows 3.1 and VB

7. Access 2.0 and VB3 w/ Windows 3.1

8. Visual Basic 4.0 for WIndows 3.1 problems

9. Visual Basic 4.0 for WIndows 3.1 problems

10. Using WINAPI 3.1 call FindExecutable on Windows 3.1

11. get adoce 3.1 running with vb toolkit 2.0

12. Accessing Acces Data Base files and win 3.1

 

 
Powered by phpBB® Forum Software