From the first entry in the MS-Access software library on www.microsoft.com:
Updated MSJT3032.DLL and MSWNG300.DLL
The Msjtwng.exe file contains updates to the Msjt3032.dll and Mswng300.dll
files that are included with Microsoft Access for Windows 95, Microsoft Visual
Basic version 4.0, and Microsoft Windows NT version 4.0. (658784 bytes,
published 09/13/96 )
^^^^^^^^
The link goes to a file that doesn't exist:
http://www.microsoft.com/kb/softlib/mslfiles/MSJTWNG.EXE
Has anyone got this file? Can you send it to me please!
Tx,
-Paul
pa...@ups.purdue.edu wrote in article
<NEWTNews.84291...@ws13.ups.purdue.edu>...
BTW, the README says:
NOTE: The issues resolved with these updates are specific to
Microsoft Windows NT version 4.0.
David W. Fenton |
New York University | The way of stylistic tolerance
dfe...@bway.net | dwf...@is2.nyu.edu | may lead to the final horror of
http://www.bway.net/~dfenton | John Tesh. --Alex Ross, NYTimes
As of 7:10pm EST on 9-17-96, it's there. I just finished downloading it.
I announced the problem in the appropriate MSN-news group
(Access/conversion)
Invalid page fault, Access 7.0
I have converted an application from Access 2.0 to 7.0. Now we are facing
serious problems in relation to stability.
The typical situation:
From a form with - an included subform - another form is launched. When the
new form is closed and another record is selected via the primary form, I
constantly get an invalid page fault. Most often related to oleaut32.dll
but sometimes also to one of the Jet-ddl's.
If I don't close any form, things seem to work as intended.
I've gone through all the steps "Troubleshooting Invalid Page Faults in MS
Access 7.0", Q148424 without any results. I've even tried it on different
hardware.
As far as I can see: Whenever a form is closed some internal tables are
damaged resulting in various page faults.
The official response was: Wait for a new version of Access!
I suppose other fixes then those mentioned in the readme-file are actually
included in the new Jet-dll!
--
/Ole Rydahl
David W. Fenton <dwf...@is2.nyu.edu> wrote in article
<51nbdv$6...@news.nyu.edu>...
>
> BTW, the README says:
>
> NOTE: The issues resolved with these updates are specific to
> Microsoft Windows NT version 4.0.
>
If anyone has any further advice on this, feel free to contact me...I'm
dieing here...and subsequently spewing Anti-Microsoft banter...
Thanks, -Jeff. :)
Ole Rydahl (o-ry...@pip.dknet.dk) wrote:
: I suppose you are right the NT focus, but at least it cured problems that
: >
--
-------- University of Michigan Artificial Intelligence Laboratory --------
Jeff Kopmanis * Sr. Sys. Analyst * 1101 Beal Ave, Ann Arbor, MI, 48109-2110
Phone: 313-763-9352 * URL: http://ai.eecs.umich.edu/people/kopmanis
I missed the start of this thread - so if some one could fill me in with
the basic details at the same time, it woud be apprectiated.
Ian
In article <NEWTNews.84291...@ws13.ups.purdue.edu>,
pa...@ups.purdue.edu wrote
>
>From the first entry in the MS-Access software library on www.microsoft.com:
>
>Updated MSJT3032.DLL and MSWNG300.DLL
>The Msjtwng.exe file contains updates to the Msjt3032.dll and Mswng300.dll
>files that are included with Microsoft Access for Windows 95, Microsoft Visual
>Basic version 4.0, and Microsoft Windows NT version 4.0. (658784 bytes,
>published 09/13/96 )
> ^^^^^^^^
>
>The link goes to a file that doesn't exist:
>
>http://www.microsoft.com/kb/softlib/mslfiles/MSJTWNG.EXE
>
>Has anyone got this file? Can you send it to me please!
>Tx,
>-Paul
>
>
--
Ian Ormonroyd
e-mail: i...@heretics.demon.co.uk
Jeff Kopmanis <kopm...@krusty.eecs.umich.edu> wrote in article
<51qoms$d...@news.eecs.umich.edu>...
> I'm having severe troubles with the old DLLs as well...page faults taht
> crash VB4 after doing 5 or 6 Refreshes to a data control. I need to
> re-query the tables after the user interacts (to "weed out" more
records).
> The refreshes just kill it all.
You need to get the updated VBA232.DLL available from microsoft. This Fix
various problems with Invalid Page Faults in Access 7.0 and VB 4.0. These
faults normally generate from cotinued use of forms and associated
refreshes of these forms. Hope this helps. The Download filename is
VBA232A.EXE