Determine if DAO Jet engine version 3.5 is installed
Posted
by Thomas Blenkers
on March 1st, 1999
bool DAO35Installed()
{
HKEY hLM;
bool ret=false;
// let's open the Registry key for DAO
if (RegOpenKeyEx(HKEY_LOCAL_MACHINE,
"Software\\Microsoft\\Jet\\3.5\\Engines",
0,KEY_QUERY_VALUE, &hLM) == ERROR_SUCCESS)
{
ret = true;
RegCloseKey(hLM);
}
return ret;
}
That's it. If you need to insure that DAO is installed just test
if (!DAO35Installed()) // warning here else // it's OK

Comments
What should I install to get DAO Jet Engine working in my setup program?
Posted by Legacy on 07/26/1999 12:00amOriginally posted by: J.H. Lee
What should I install to get DAO Jet Engine working in my setup program?
ReplyWould you know what or which DLLs and registry info... is needed on that situation?
--- in korea (sorry. I'm not native English speaker.)
What should I install to get DAO Jet Engine working (without Access)?.
Posted by Legacy on 03/13/1999 12:00amOriginally posted by: David
I'd like to know what should I install (which Dll, etc...) to
get a DAO Jet engine working.
thx in advance
ReplyAn even better way to determine the DAO version
Posted by Legacy on 02/02/1999 12:00amOriginally posted by: Chris Yourch
Call this member function to determine the version of the Microsoft Jet database engine in use. The value returned represents the version number in the form "major.minor"; for example, "3.0". The product version number (for example, 3.0) consists of the version number (3), a period, and the release number (0).
ReplyCString version = CDaoWorkspace::GetVersion();
LPTSTR pszMajor = version.GetBuffer(0);
LPTSTR pszMinor = strchr(pszMajor, '.');
*pszMinor++ = '\0';
int major = atoi(pszMajor);
int minor = atoi(pszMinor);
MFC will do it for you if you open a database
Posted by Legacy on 10/28/1998 12:00amOriginally posted by: Eric Cholet
ReplyIs testing just for 3.5 good enough?
Posted by Legacy on 10/13/1998 12:00amOriginally posted by: John L. Stanley
Thanks for the useful function.
Just one question:
What happens when Microsoft releases the "next" version of Jet? Are they going to put entries in the registry to make it look like a version of 3.5 is loaded -or- are the CDaoXXXX objects suppost to auto-sense the version 4.0 (or whatever) registry hooks and use those?
I guess what I'm asking is, if I use your function to auto-sense Jet 3.5, will my program fail when a user installs a higher version of Jet?
Thanks,
Reply... JLS