 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / General 1 / November 2004JET4.0 Downgrade - confusion
How do I know which version of MSJET40.dll is currently being used by Access on my PC? and can I distribute an older version and still expect it to work? If not, can I go back to an older version on my PC so that I can distribute with the older version which used to work? My app is crashing when running some parts, (it runs OK until one particular element is called which uses an external 3rd party activeX control) but I do not appear to have any references missing. This is difficult to tell because I have a problem installing the run-time without breaking an A2K retail installation or installing A2K retail after my app, so am currently unable to get into it to check properly. I am assuming now that this is a MSJET dll problem. Marian Look at the following article http://support.microsoft.com/default.aspx?scid=kb;en-us;829558 Hope it helps Alfred > How do I know which version of MSJET40.dll is currently being used by > Access on my PC? [quoted text clipped - 12 lines] > > Marian >Look at the following article >http://support.microsoft.com/default.aspx?scid=kb;en-us;829558 Trouble is Security Path MS04-14 supercedes Jet 4.0 SP8. Microsoft Access Fixes, Patches and Updates http://www.granite.ab.ca/access/msfixes.htm Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm >My app is crashing when running some parts, (it runs OK until one >particular element is called which uses an external 3rd party activeX >control) but I do not appear to have any references missing. What's the error message? If any? Are you distributing your 3rd party Activex control along with all it's dependencies? OCX/DLL Version Checker http://www.granite.ab.ca/access/ocxdllversionchecker.htm This MDB verifies the remote systems OCX/DLL versions against your version. You want to avoid the use of any Microsoft OCX/DLL due to version (DLL Hell) and distribution problems. Many of them are just wrappers around API calls anyhow. >I am assuming now that this is a MSJET dll problem. I kinda doubt it. Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.