Jim DeMarco
Jdemarco at hudsonhealthplan.org
Fri Feb 24 12:19:54 CST 2006
Thanks for the detailed reply Marty. We're probably going to have to mix and match possible solutions. We don't have A2K here. The app was given to us by a company in Idaho as freeware and it came via an install disk so we never put them together (the app and runtime). All we do is modify the front-end and copy over the original. I think I've got enough possibilities here to get us on track though. Thanks again, Jim D. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of MartyConnelly Sent: Friday, February 24, 2006 11:59 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access 2000 Runtime Error (X-posted) I am guessing without knowing the client's dll version numbers The problem maybe best fixed by recreating your runtime Access 2000 program ensuring it is recompiled with Office 2000 SP3 and Jet SP8 installed. Then reinstalling that, if your Access 2000 program isn't split into a backend, you will have trouble recovering the users tables. If they try to use DAO 3.6 with VB 6 code for mdb database creation they will be creating in 2000 format not 97 unless specifically coded and that may cause problems since DAO 3.5 cannot read 2000 DAO 3.6 format. It is however backward compatible. Their may also be ANSI vs Unicode problems. You might get lucky by re-registering MSJET35.dll In the Run dialog, type the following command: Regsvr32.exe <DLL Name> where DLL Name is the name of the DLL file, such as "C:\WINDOWS\system32\msjet35.dll". Path name should be in quotes to avoid spaces problem or perhaps installing the old (last century) Jet SP3 security service pack for DAO 350 only This will re-register dll Pay attention to what version of MSJET35.dll is installed otherwise the SP won't install. http://support.microsoft.com/kb/q172733/ How to determine the current service pack level for Jet 3.5 Use the following steps to determine the Jet 3.5 service pack level that is currently installed on your computer. Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.1. On the Start menu, click Search. 2. In the Search Results pane under Search Companion, click All files and folders. 3. In the All or part of the file name box, type msjet35.dll, and then click Search. 4. In the list of files, right-click the msjet35.dll file located in the Windows\System32 (or Windows\System) folder, and then click Properties. 5. Click the Version tab, and then use the following table to determine the current Jet 4.0 service pack level: Msjet35.dll Version Jet 3.5 Service Pack Level 3.51.2723.0 Service Pack 2 (SP2) 3.51.3203.0 Service Pack 3 (SP3) 3.51.3328.0 Service Pack 3 (SP3) with enhanced security Also see http://msdn.microsoft.com/data/downloads/updates/default.aspx#jet If you're running Access on an NT box being a DHCP/WINS server etc, then you need to stop the services, cause they themselves use Jet to handle their databases. Jim DeMarco wrote: >>>They maybe running old VB6 programs calling DAO 3.51 >>> >>> > >Thanks Marty. This is exactly what they're doing. > >So will SP3 still fix for them? Or should they recompile their VB apps using a newer Jet version? > >Jim D. > > > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of MartyConnelly >Sent: Thursday, February 23, 2006 2:34 PM >To: Access Developers discussion and problem solving >Subject: Re: [AccessD] Access 2000 Runtime Error (X-posted) > > >Have client look at this file in windows explorer > >c:\program files\common files\microsoft shared\vba\vba6\vbe6.dll > >Right click on file select properties then selectr version tab and then >file version >For Office 2003 I have version number for vbe6.dll >6.04.9972 >If you have equal to or lower than > 6.3.91.8 >then it is the faulty Office 2000 vbe6.dll >And needs the Office 2000 SP3 installed > >Jet or DAO 3.51 in msjet35.dll is only installed by Office 97 or MDAC >2.1 (hasn't been downloadable for 2 years from MS) >Access 2000 uses DAO 3.6 msjet40.dll > >They maybe running old VB6 programs calling DAO 3.51 > >I have Office 97 and 2003 installed > >C:\WINDOWS\system32\msjet35.dll My version is 3.51.3328.0 >C:\WINDOWS\system32\msjet40.dll version 4.00.8618.0 > >I have heard of certain DAO 3.6 installs removing DAO 3.51 so you might >want to check they are both there >Most DAO calls that ran against 3.51 will run against DAO 3.6 except for >security fixes. > > >Jim DeMarco wrote: > > > >>Thanks Gustav. >> >>It looks like they may have changed the link to that article. I get this article when I click the link you attached: >> >>"You receive an error message when you try to view the code in a module, compile a database, create an MDE file or execute code in Access 2000" >> >>I think they're running WinXP as well but I'm waiting for an answer on that. >> >>I'm the meantime I think I need to find a better search phrase. I'm coming up blank (irrelevant) on Google and kbalertz.com. >> >>Jim >> >>-----Original Message----- >>From: accessd-bounces at databaseadvisors.com >>[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gustav Brock >>Sent: Thursday, February 23, 2006 12:28 PM >>To: accessd at databaseadvisors.com >>Subject: Re: [AccessD] Access 2000 Runtime Error (X-posted) >> >> >>Hi Jim >> >>Could it be the old VBE6.dll issue: >> >><snip> >> >>Take a look at >>http://support.microsoft.com/default.aspx?scid=kb;en-us;Q304548 >> >>This is a typical error when you do not have O2k SR-3 and you have a 2002 or later app installed on the same machine. The VBE6.DLL for 2002 breaks the 2000 Access executable. >> >>Charlotte Foust >> >></snip> >> >> >> >> >> >>>>>Jdemarco at hudsonhealthplan.org 23-02-2006 17:47:27 >>> >>>>> >>>>> >>>>> >>>>> >>X-posted AccessD: dba-VB >> >>Lists, >> >>We inherited (and distribute) an Access 2K app that uses the Access runtime. One of our user sites (not affiliated with our company) is having a problem running VB apps on machines where this app is installed. Here's a copy of what I got from their IT resource: >> >><errorDescr> >>"...happens when an application is started. >>A window opens saying somthing like "Loading Access 2000 Runtime" and displaying a Windows progress bar. >>Then a "File Not Found" message window opens. If you cancel out of the window, another "File Not Found" windows opens, etc.. >>If you cancel out of these windows about 3 or 4 times, the program will start. >></errorDescr> >> >>They're using Jet 3.51 for "ADO and DAO data access" (quoting their IT resource). Is anyone familiar with this? I searched M$KB but didn't find anything. >> >>TIA >> >>Jim DeMarco >>Director of Application Development >>Hudson Health Plan >> >> >> >> >> > > > -- Marty Connelly Victoria, B.C. Canada -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com *********************************************************************************** "This electronic message is intended to be for the use only of the named recipient, and may contain information from Hudson Health Plan (HHP) that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately, either by contacting the sender at the electronic mail address noted above or calling HHP at (914) 631-1611. If you are not the intended recipient, please do not forward this email to anyone, and delete and destroy all copies of this message. Thank You". ***********************************************************************************