J
JamesLynn
Windows XP with Office 2003 / Access 2003.
Visual Basic Version 6.
I have developed several VB6 applications that make use of ACCESS 2003
databases. VB6 and these standalone applications were working fine until I
installed a software product that installed / required ACCESS 2000 runtime.
Since installing ACCESS 2000 runtime everytime I start one of my VB6
Applications (standalone) or go to maintain them with VB6 the Access 2000
Runtime install fires up. It appears to start the runtime install on for each
database / table being accessed by the application.
If I just keep cancelling the Runtime Install my application eventually
starts and runs OK.
Does anyone know how I prevent this Access 2000 runtime from being invoked.
I figure there's an entry somewhere saying Access 2000 is the default instead
of 2003.
Visual Basic Version 6.
I have developed several VB6 applications that make use of ACCESS 2003
databases. VB6 and these standalone applications were working fine until I
installed a software product that installed / required ACCESS 2000 runtime.
Since installing ACCESS 2000 runtime everytime I start one of my VB6
Applications (standalone) or go to maintain them with VB6 the Access 2000
Runtime install fires up. It appears to start the runtime install on for each
database / table being accessed by the application.
If I just keep cancelling the Runtime Install my application eventually
starts and runs OK.
Does anyone know how I prevent this Access 2000 runtime from being invoked.
I figure there's an entry somewhere saying Access 2000 is the default instead
of 2003.