Access 97 Invalid Page Faults in MSACCESS.EXE
| Author |
Message |
|
E. Wilso
#1 / 6
|
 Access 97 Invalid Page Faults in MSACCESS.EXE Thanks in advance to anyone who can shed some light here...
With Access97, I am getting Invalid Page Faults all over the place: when I
try to run a Wizard, when the little "auto-help" things pop-up in the the
VBA editor, when I try to add a graphic to a tab-control, etc.
In addition, some VBA functions are simply refusing to work, such as
recorset operations (FindFirst, etc.). I receive error messages that the
function is "marked as restricted" or "not supported"--and these are lines
of code *directly* from the Access Help and Wizards.
What I've tried:
I've searched up and down the MS Knowledge base, to no avail. I've
reinstalled Office 97 multiple time (finally removing *all* previous Office
programs and trying again) -- but nothing. I installed Access97 on my
machine at work just to see if it worked and, behold, no problems at all.
If anyone has any suggestions or explanations, I thank you sincerely.
Eric Wilson
|
| Wed, 12 Jan 2000 03:00:00 GMT |
|
 |
|
Ethan Ray Pos
#2 / 6
|
Access 97 Invalid Page Faults in MSACCESS.EXE
Quote: > Thanks in advance to anyone who can shed some light here... >With Access97, I am getting Invalid Page Faults all over the place: when I
>try to run a Wizard, when the little "auto-help" things pop-up in the the
>VBA editor, when I try to add a graphic to a tab-control, etc.
>In addition, some VBA functions are simply refusing to work, such as
>recorset operations (FindFirst, etc.). I receive error messages that the
>function is "marked as restricted" or "not supported"--and these are lines
>of code *directly* from the Access Help and Wizards.
>What I've tried:
>I've searched up and down the MS Knowledge base, to no avail. I've
>reinstalled Office 97 multiple time (finally removing *all* previous Office
>programs and trying again) -- but nothing. I installed Access97 on my
>machine at work just to see if it worked and, behold, no problems at all.
>If anyone has any suggestions or explanations, I thank you sincerely.
>Eric Wilson
Easy, Re-Install.
|
| Thu, 13 Jan 2000 03:00:00 GMT |
|
|
|
aaausti
#3 / 6
|
Access 97 Invalid Page Faults in MSACCESS.EXE
Quote: > Thanks in advance to anyone who can shed some light here... > With Access97, I am getting Invalid Page Faults all over the place: when
I
> try to run a Wizard, when the little "auto-help" things pop-up in the the
> VBA editor, when I try to add a graphic to a tab-control, etc....
..I installed Access97 on my machine at work just to see if it worked and, behold, no problems at all. Quote: The problem reeks of mismatched library files...compare dll lists between your working and nonworking machines with System Info in any Office app (under "Help") most especially the VBA modules. When installing Office, do you get any "a file being copied is older than..." messages? Are your other apps stable? I've also had problems with a particular Intel motherboard, what are you running? Regards, Andrew
|
| Thu, 13 Jan 2000 03:00:00 GMT |
|
|
|
E. Wilso
#4 / 6
|
Access 97 Invalid Page Faults in MSACCESS.EXE Thanks for your suggestion. However, I've reinstalled Access alone and
reinstalled Office97 *multiple* times to try to fix this. Any other
suggestions?
Quote:
>> Thanks in advance to anyone who can shed some light here...
>>With Access97, I am getting Invalid Page Faults all over the place: when I
>>try to run a Wizard, when the little "auto-help" things pop-up in the the
>>VBA editor, when I try to add a graphic to a tab-control, etc.
>>In addition, some VBA functions are simply refusing to work, such as
>>recorset operations (FindFirst, etc.). I receive error messages that the
>>function is "marked as restricted" or "not supported"--and these are lines
>>of code *directly* from the Access Help and Wizards.
>>What I've tried:
>>I've searched up and down the MS Knowledge base, to no avail. I've
>>reinstalled Office 97 multiple time (finally removing *all* previous
Office
>>programs and trying again) -- but nothing. I installed Access97 on my
>>machine at work just to see if it worked and, behold, no problems at all.
>>If anyone has any suggestions or explanations, I thank you sincerely.
>>Eric Wilson
> Easy, Re-Install.
|
| Thu, 13 Jan 2000 03:00:00 GMT |
|
|
|
John Fue
#5 / 6
|
Access 97 Invalid Page Faults in MSACCESS.EXE No kidding I get these a lot too. Do a search on the Microsoft knowledge
base for "IPF" (Read as Internal Protection Fault) and you get a gazillion
hits. ARGHHH!
Quote: > Thanks in advance to anyone who can shed some light here... > With Access97, I am getting Invalid Page Faults all over the place: when
I
> try to run a Wizard, when the little "auto-help" things pop-up in the the
> VBA editor, when I try to add a graphic to a tab-control, etc.
|
| Wed, 19 Jan 2000 03:00:00 GMT |
|
|
|
stev
#6 / 6
|
Access 97 Invalid Page Faults in MSACCESS.EXE
Quote:
> > Thanks in advance to anyone who can shed some light here...
> > With Access97, I am getting Invalid Page Faults all over the place:
when
> I
> > try to run a Wizard, when the little "auto-help" things pop-up in the
the
> > VBA editor, when I try to add a graphic to a tab-control, etc....
> ..I installed Access97 on my machine at work just to see if it worked
and,
> behold, no problems at all.
> The problem reeks of mismatched library files...compare dll lists between
> your working and nonworking machines with System Info in any Office app
> (under "Help")
> most especially the VBA modules. When installing Office, do you get any
"a
> file being copied is older than..." messages? Are your other apps
stable?
> I've also had problems with a particular Intel motherboard, what are you
> running?
> Regards,
> Andrew
Same problem here, I keep getting page faults all over the place, and I've checked my DLL files to make sure they are the newest ones or the correct ones, whichever are right. I got rid of some, but others, for example, when changing a text box to a combo box and then either [Edit] undo-ing it or using the "change to" command to change it back, still causes a page fault. I'm almost positive I've got the right DLLs.
|
| Sat, 22 Jan 2000 03:00:00 GMT |
|
| |
|
