Dao350.dll unsupported under Windows 7
in [Visual Basic]
|
From: Nobody on 12 Nov 2009 23:28 "Tony Toews [MVP]" <ttoews(a)telusplanet.net> wrote in message news:a0mpf5l72jau91s2hm35c69clmphkbi6lr(a)4ax.com... > How would that be letting down your customers? The changes should be > transparent to your app. It's been a while but I don't recall any > problems when moving from Access 97 to Access 2000. One of the differences I hear about between DAO and the newer ADO is that DAO is faster with Access DB because it's tightly optimized to it.
From: Marc Henderson on 12 Nov 2009 23:40 "Tony Toews [MVP]" <ttoews(a)telusplanet.net> wrote: >Marc Henderson <genesis77Re-move-this(a)usa.com> wrote: > >>>Switch to using Jet 4.0. It is present on Windows 2000 through to >>>Windows 7. As it is installed with the OS and updated as part of the >>>OS updates you don't need to worry about installing it. >>> >>>Tony >> >>Thanks for your quick response, Tony. The problem with switching to >>Jet 4.0 is that we have many customers now using our app with DAO 3.51 >>and we'd be letting them down if we switched at this point. Also, >>nobody on our staff is familiar with Jet 4.0. Would it mean that we'd >>have to change our code, e.g., for SQL queries ? > >How would that be letting down your customers? The changes should be >transparent to your app. It's been a while but I don't recall any >problems when moving from Access 97 to Access 2000. > >Do note though that my expertise is in Access. I'm not a VB expert >although I'm learning. > >>One thing I thought of is switching to DAO 3.6, because it's >>distributed with Win7 and I seem to remember that there's a utility >>for converting from DAO 3.5 to 3.6. Do you happen to know if there is >>such a utility and whether it's distributable ? > >No idea. And I don't think there's much of a conversion required >other than removing the DAO 3.5 reference and putting in the DAO 3.6 >reference. Obviously you'll need to test things out. > >Hmm, I forgot about Sandbox mode stuff. Do ensure you test with a bog >standard user account in Windows to ensure none of the Sandbox >settings affect you. I don't know if they would or not. > >How to configure Jet 4.0 to prevent unsafe functions from running in >Access 2000 and Access 2002 >http://support.microsoft.com/kb/239482 > >>Of course the ideal solution would be to get the updated dao350.dll if >>it really exists. :) There must be some way to contact MS to ask >>questions like this. > >The last one of which I'm aware is >Jet 3.5 SP3 - msjet35.dll - 3.51.3328.0 >Updated version of Microsoft Jet 3.5 available for download >http://support.microsoft.com/kb/172733 >The above is dated 1999. > >Tony Thanks a lot for all that info, Tony. I thought there was a data format change between Access 97 and Access 2000. Hope I'm wrong. :) Looks like we'll all be pretty busy in the next few days trying out your suggesions. Many thanks. Marc
From: Tony Toews [MVP] on 12 Nov 2009 23:43 "Nobody" <nobody(a)nobody.com> wrote: >How to obtain the latest service pack for the Microsoft Jet 4.0 Database >Engine >http://support.microsoft.com/kb/239114 Note though that the latest versions of msjet40.dll should be in your OS already if you are using Windows/Microsoft Update as these are part of the OS and are part of security patches. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a free, convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/
From: Marc Henderson on 12 Nov 2009 23:45 "Nobody" <nobody(a)nobody.com> wrote: >I think you could update to DAO360.DLL, but I am not sure. Also, check these >articles: > >MDAC version 2.6 and later do not contain Jet or Desktop ODBC drivers >http://support.microsoft.com/default.aspx?kbid=271908 > >How to obtain the latest service pack for the Microsoft Jet 4.0 Database >Engine >http://support.microsoft.com/kb/239114 > >DAO360.DLL is listed in the above article. > >How to keep a Jet 4.0 database in top working condition in Access 2000 >http://support.microsoft.com/kb/300216 > >HOW TO: Keep a Jet 3.x Database in Top Working Condition(Link came from the >article above): >http://support.microsoft.com/kb/303519/ > Thanks, Nobody, for all those links. They look pretty useful. I'll check every one of them out. Marc
From: Tony Toews [MVP] on 12 Nov 2009 23:52
Marc Henderson <genesis77Re-move-this(a)usa.com> wrote: >Thanks a lot for all that info, Tony. I thought there was a data >format change between Access 97 and Access 2000. Hope I'm wrong. :) >Looks like we'll all be pretty busy in the next few days trying out >your suggesions. Many thanks. Oh, there is. if you want it to. That is there are Access 97 format MDBs, A2000 MDBs and A2007 MDBs, ACCDBs. But this is optional. Jet 4.0 still works just fine against an A97 MDB. I had a client running a mixture of 25 A97 and A2000 workstations against an A97 format MDB for at least five years. So that won't be a problem. (I fired them due to a PHB (Dilbert's Pointy Haired Boss) they hired. Last I heard they had spent about triple on what I cost them to replace the Access solution with a .Net solution and it wasn't close to being implemented.) Now if you want to you can run one line of code that converts the file format from A97 to Access 2000 format. I'd suggest though ensuring that all old copies of your VB exe that use Jet 3.5 no longer exist. From Access 2003 help DBEngine.CompactDatabase olddb, newdb, , options where options would be dbversion40 aka 64. Note that I haven't tested this myself but it should work. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a free, convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/ |