Guest_imported
New member
- Jan 1, 1970
- 0
Here tis the error,
MSACCESS caused an invalid page fault in
module VBA332.DLL at 017f:651503f7.
Registers:
EAX=00000000 CS=017f EIP=651503f7 EFLGS=00010246
EBX=00000000 SS=0187 ESP=0062efe8 EBP=0062f018
ECX=0062fe28 DS=0187 ESI=ffffffff FS=367f
EDX=02c4f4e4 ES=0187 EDI=0062f014 GS=0000
Bytes at CS:EIP:
8b 46 04 8b 50 04 b8 00 00 00 00 8b 8a 28 02 00
Stack dump:
015af250 00000000 00000b88 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0062f04c 300f1fe2 ffffffff 00000000
Just to recap the situation.
I have an mdb (office 97) which I have been using for well over 18 months. When I compile it into an mde on my ME machine, the mde will run fine on mine and toots pc (win 98), when I load it onto the client machine or another pc I have (win 98) it gives the above error. The same behaviour occurs if I compile it on toots machine.
Then I take the original mdb to my spare pc, compile it there, the mde will work there, but when I transfer the mde back to my own or toots pc it gives the above error again.
I have all service packs up to sp2b
dll versions
dao350.dll 3.51.1608
vba332.dll 3.0.0.7019
I have also created a new database, imported all the objects and compiled with no luck. I also created a new database completely unrelated to the original project, and when I compile it as above I get the same sort of results.
About the only thing I haven't done yet is compare each and every single file installed with access for version differences ( I am not really looking forward to that one).
Any lead would be appreciated.
MSACCESS caused an invalid page fault in
module VBA332.DLL at 017f:651503f7.
Registers:
EAX=00000000 CS=017f EIP=651503f7 EFLGS=00010246
EBX=00000000 SS=0187 ESP=0062efe8 EBP=0062f018
ECX=0062fe28 DS=0187 ESI=ffffffff FS=367f
EDX=02c4f4e4 ES=0187 EDI=0062f014 GS=0000
Bytes at CS:EIP:
8b 46 04 8b 50 04 b8 00 00 00 00 8b 8a 28 02 00
Stack dump:
015af250 00000000 00000b88 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0062f04c 300f1fe2 ffffffff 00000000
Just to recap the situation.
I have an mdb (office 97) which I have been using for well over 18 months. When I compile it into an mde on my ME machine, the mde will run fine on mine and toots pc (win 98), when I load it onto the client machine or another pc I have (win 98) it gives the above error. The same behaviour occurs if I compile it on toots machine.
Then I take the original mdb to my spare pc, compile it there, the mde will work there, but when I transfer the mde back to my own or toots pc it gives the above error again.
I have all service packs up to sp2b
dll versions
dao350.dll 3.51.1608
vba332.dll 3.0.0.7019
I have also created a new database, imported all the objects and compiled with no luck. I also created a new database completely unrelated to the original project, and when I compile it as above I get the same sort of results.
About the only thing I haven't done yet is compare each and every single file installed with access for version differences ( I am not really looking forward to that one).
Any lead would be appreciated.
