RE: Upgrade causing problem
From: Eric Butts [MSFT] (ebutts_at_online.microsoft.com)
Date: 03/14/04
- Next message: Eric Butts [MSFT]: "RE: can't dim db as database"
- Previous message: hanssoderstrom_at_yahoo.com: "can't dim db as database"
- In reply to: Paul O'Leary: "RE: Upgrade causing problem"
- Next in thread: Paul O'Leary: "RE: Upgrade causing problem"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 14 Mar 2004 23:17:40 GMT
Hi Paul,
Even though you stated "application ran fine on XP until Office 2003
Upgrade (including full licence of Access) was installed? " I would still
suspect the Microsoft JET Database Engine service pack. Again compare the
version # of the file "msjet40.dll" where it works and where it fails.
Regards,
Eric Butts
Microsoft Access Support
ebutts@online.microsoft.com
"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
<http://www.microsoft.com/security/security_bulletins/ms03-026.asp> and/or
to visit Windows Update at <http://windowsupdate.microsoft.com/> to install
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| Content-Class: urn:content-classes:message
| From: "Paul O'Leary" <pbosolutions@ntlworld.com>
| Sender: "Paul O'Leary" <pbosolutions@ntlworld.com>
| References: <955501c405bd$d32658c0$a001280a@phx.gbl>
<rM44$mfBEHA.3552@cpmsftngxa06.phx.gbl>
| Subject: RE: Upgrade causing problem
| Date: Thu, 11 Mar 2004 02:20:40 -0800
| Lines: 127
| Message-ID: <ad6201c40752$80ea2dc0$a501280a@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcQHUoDqCKQt4yKORPGpgAlM5DsjmQ==
| Newsgroups: microsoft.public.access.setupconfig
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.access.setupconfig:29413
| NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
| X-Tomcat-NG: microsoft.public.access.setupconfig
|
| Thanks Eric!
| I will now work through your recommendations. To be honest
| my application isn't that complicated ... but a useful
| Access database issued under Runtime licence largely
| consisting of simple queries, forms, and reports. No ODBC
| links and not running across a network (though it can do)
| nor anything else too clever or complicated.
| As indicated on my initial note such errors have arisen
| upgrading from 98 to XP but latterly when simply upgrading
| from MS Works (shipped with new PC) to Office 2003? That
| is to say the application ran fine on XP until Office 2003
| Upgrade (including full licence of Access) was installed?
| Now the database won't run properly either under Runtime
| or Full licence? Hey ho! These things are sent to try
| us ... !
| Best regards
| Paul
| >-----Original Message-----
| >Hi Paul,
| >
| >Not knowing what you have included in your Runtime
| application I would
| >troubleshoot it as follows:
| >
| >- Compare the version of the Microsoft JET Database
| Enging on the Win98 vs
| >WinXP, see the version # of the file "MsJET40.dll" (for
| 2000 and above) or
| >"MsJET35.dll" (for 97).
| >Note that even if they are the same version # there are
| cases where JET
| >behaves differently on one OS vs the other. For details
| on JET see:
| >http://support.microsoft.com/?id=239114
| >Also while checking I would go ahead and update the WinXP
| machine to the
| >latest version of JET anyway (it's the latest and
| greatest).
| >
| >- Then I would test a real generic MDB (runtime) that
| only includes a table
| >and a startup Form (no graphics, no ActiveX Controls,
| etc..) on the WinXP
| >machine
| >
| >- Should the generic MDB (runtime) file work on the WinXP
| machine then it's
| >something specific in your application. Look at things
| like an ActiveX
| >controls you include in your application, Graphics, etc..
| If eliminating
| >the extras in your application allows your application to
| run on WinXP then
| >you've narrowed done the troubleshooting
| >
| >I hope this helps! If you have additional questions on
| this topic, please
| >respond back to this posting.
| >
| >
| >Regards,
| >
| >Eric Butts
| >Microsoft Access Support
| >ebutts@online.microsoft.com
| >"Microsoft Security Announcement: Have you installed the
| patch for
| >Microsoft Security Bulletin MS03-026? If not Microsoft
| strongly advises
| >you to review the information at the following link
| regarding Microsoft
| >Security Bulletin MS03-026
| ><http://www.microsoft.com/security/security_bulletins/ms03
| -026.asp> and/or
| >to visit Windows Update at
| <http://windowsupdate.microsoft.com/> to install
| >the patch. Running the SCAN program from the Windows
| Update site will help
| >to insure you are current with all security patches, not
| just MS03-026."
| >
| >This posting is provided "AS IS" with no warranties, and
| confers no rights
| >
| >
| >
| >
| >
| >
| >--------------------
| >| Content-Class: urn:content-classes:message
| >| From: "Paul O'Leary" <pbosolutions@ntlworld.com>
| >| Sender: "Paul O'Leary" <pbosolutions@ntlworld.com>
| >| Subject: Upgrade causing problem
| >| Date: Tue, 9 Mar 2004 02:03:52 -0800
| >| Lines: 11
| >| Message-ID: <955501c405bd$d32658c0$a001280a@phx.gbl>
| >| MIME-Version: 1.0
| >| Content-Type: text/plain;
| >| charset="iso-8859-1"
| >| Content-Transfer-Encoding: 7bit
| >| X-Newsreader: Microsoft CDO for Windows 2000
| >| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| >| Thread-Index: AcQFvdMmjkOyFaCNRZKStHiGgcjgmg==
| >| Newsgroups: microsoft.public.access.setupconfig
| >| Path: cpmsftngxa06.phx.gbl
| >| Xref: cpmsftngxa06.phx.gbl
| microsoft.public.access.setupconfig:29386
| >| NNTP-Posting-Host: tk2msftngxa08.phx.gbl 10.40.1.160
| >| X-Tomcat-NG: microsoft.public.access.setupconfig
| >|
| >| When UPGRADING, say from W98, to Windows XP an existing
| >| MS Access runtime application then fails having
| previously
| >| run perfectly well on the previous Windows platform?
| >|
| >| The application also runs perfectly well on FULL XP
| >| licence.
| >|
| >| So, what is it about an UPGRADE to XP which causes the
| >| application to fail? Can I put things right somehow?
| >|
| >|
| >|
| >
| >.
| >
|
- Next message: Eric Butts [MSFT]: "RE: can't dim db as database"
- Previous message: hanssoderstrom_at_yahoo.com: "can't dim db as database"
- In reply to: Paul O'Leary: "RE: Upgrade causing problem"
- Next in thread: Paul O'Leary: "RE: Upgrade causing problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
