Problems with Access 2000 on W2K
Hello! I´ve encountered a serious problem while working with the Office 2000 suite (esp. with Access) under Windows 2000. I´ve developed an Access application, with a moderate number of tables, forms and reports and with some VBA coding involved. The development process was under Windows 98, and the client seemed to (almost) flawlessly use the application with W2K. At some point I also decided to migrate to W2K and proceed with the application´s fine tuning there. But, to my amazement, the application responded very harshly to this "turmoil". It started to behave very unpredictably, especially with reports and coded event procedures. It started to generate absolutely inappropriate error-messages and crush (with "MS Access has generated a fatal error..." kind of messages). The point is, that with every instance it takes a different time and circumstances for the software to crush. And, lately, I´ve noticed that Word also crushes sometimes, with no apparent reason whatsoever. I suspect it has something to do with my system´s pretty "weak" configuration. Here´s the system summary generated by the appropriate computer management option: System Information report written at: 03/08/02 23:31:03 LocalMachine[System Summary] Item Value OS Name Microsoft Windows 2000 Professional Version 5.0.2195 Build 2195 OS Manufacturer Microsoft Corporation System Name HOME System Manufacturer System Manufacturer System Model System Name System Type X86-based PC Processor x86 Family 6 Model 8 Stepping 1 GenuineIntel ~500 Mhz BIOS Version Award Modular BIOS v4.51PG Windows Directory E:\WINNT System Directory E:\WINNT\System32 Boot Device \Device\Harddisk0\Partition1 Locale Israel User Name HOME\Ostap Bender Total Physical Memory 130,600 KB Available Physical Memory 19,020 KB Total Virtual Memory 440,652 KB Available Virtual Memory 216,024 KB Page File Space 310,052 KB Page File E:\pagefile.sys Maybe I have to enlarge the virtual memory? But the reported suggested virtual memory is 190M! Has anyone encountered similar problems? What do I do in this case? I know, that the client´s system runs this application OK (but his system has 256M RAM - could this be the reason?). Any suggestions? Thanks, sosed.
Hello! I´ve encountered a serious problem while working with the Office 2000 suite (esp. with Access) under Windows 2000. I´ve developed an Access application, with a moderate number of tables, forms and reports and with some VBA coding involved. The development process was under Windows 98, and the client seemed to (almost) flawlessly use the application with W2K. At some point I also decided to migrate to W2K and proceed with the application´s fine tuning there. But, to my amazement, the application responded very harshly to this "turmoil". It started to behave very unpredictably, especially with reports and coded event procedures. It started to generate absolutely inappropriate error-messages and crush (with "MS Access has generated a fatal error..." kind of messages). The point is, that with every instance it takes a different time and circumstances for the software to crush. And, lately, I´ve noticed that Word also crushes sometimes, with no apparent reason whatsoever. I suspect it has something to do with my system´s pretty "weak" configuration. Here´s the system summary generated by the appropriate computer management option: System Information report written at: 03/08/02 23:31:03 LocalMachine[System Summary] Item Value OS Name Microsoft Windows 2000 Professional Version 5.0.2195 Build 2195 OS Manufacturer Microsoft Corporation System Name HOME System Manufacturer System Manufacturer System Model System Name System Type X86-based PC Processor x86 Family 6 Model 8 Stepping 1 GenuineIntel ~500 Mhz BIOS Version Award Modular BIOS v4.51PG Windows Directory E:\WINNT System Directory E:\WINNT\System32 Boot Device \Device\Harddisk0\Partition1 Locale Israel User Name HOME\Ostap Bender Total Physical Memory 130,600 KB Available Physical Memory 19,020 KB Total Virtual Memory 440,652 KB Available Virtual Memory 216,024 KB Page File Space 310,052 KB Page File E:\pagefile.sys Maybe I have to enlarge the virtual memory? But the reported suggested virtual memory is 190M! Has anyone encountered similar problems? What do I do in this case? I know, that the client´s system runs this application OK (but his system has 256M RAM - could this be the reason?). Any suggestions? Thanks, sosed.