Great community. Great ideas.
Welcome to ASP/Free, a community dedicated to helping beginners and professionals alike in improving their knowledge of Microsoft's development and administration technologies. Sign up today to gain access to the combined insight of tens of thousands of members.
February 19th, 2013, 08:54 PM
Now this is strange...
Developed a very simple access report, after the report is run, the data is returned, maybe 20 rows or so, not much......if I let the results sit on the screen for about an hour, msaccess.exe crashes and the following is logged in event viewer. my csr's started reporting this about a month ago, doesn't matter if it is run locally or via a network drive. i should say we use the access runtime (.accdr file) as i have the only license for access in the company and i create all the reports and queries. they'll typically run the report and then go about doing other things, time passes by and then they see the crash message. i wish there was more info, but this is all i have. can anyone point me in the right direction?
ps - there's no VB code, modules or macros of anykinds, it's literally a query and then format it as a report to pretty up the results......ultra simple.....access 101 stuff....
Level Date and Time Source Event ID Task Category
Error 2/19/2013 9:37:01 PM Application Error 1000 (100) "Faulting application name: MSACCESS.EXE, version: 12.0.6606.1000, time stamp: 0x4e27ab6b
Faulting module name: MSACCESS.EXE, version: 12.0.6606.1000, time stamp: 0x4e27ab6b
Exception code: 0xc0000005
Fault offset: 0x000be585
Faulting process id: 0x1650
Faulting application start time: 0x01ce0f0ba6935882
Faulting application path: C:\Program Files\Microsoft Office\Office12\MSACCESS.EXE
Faulting module path: C:\Program Files\Microsoft Office\Office12\MSACCESS.EXE
Report Id: 673657a4-7b06-11e2-8315-180373728cfe"
February 20th, 2013, 08:28 AM
no Idea why it's crashing, but maybe you could use an on timer event to close the report for them.
February 27th, 2013, 06:52 AM
Do you see the same error if running the databaae with your full installation?
Unfortunately Access runtime doesn't offer any way of debugging so if your database throws a 'normal' error then the database will just close.
It may well be that there is a normal error happening but you can't see it.
By drl in forum ASP Development
Last Post: January 18th, 2008, 05:37 PM
By rollerblast in forum ASP Development
Last Post: June 11th, 2006, 04:25 PM
By Sluap in forum ASP Free Lounge
Last Post: March 23rd, 2006, 03:37 AM
By byatiraj in forum ASP Development
Last Post: January 13th, 2005, 02:57 AM
By kboek in forum .NET Development
Last Post: December 18th, 2004, 03:24 PM