Access crashes when switching Form View to Datasheet View

[bsacheri]

I've got a continuous form that is bound to a SQL Server View (linked table). The form is editable by a team of users. I have a button on the form that switches the form to Datasheet View because some users prefer working in a grid. Recently we've noticed that switching to the datasheet view causes Access show "Calculating..." in the status bar and then it crashes with no error message. The datasheet view is more likely to crash if a filter has been applied in form view before switching to datasheet view. The form view and datasheet view are using the same recordsource (the code simply changes the view). If the user right-clicks on the form tab to change the view the same results happen as when they click the button that changes the view.

Prior to switching this application to use a SQL Server backend earlier this year, this feature has been in use with an Access back-end for 10 years and no issues.

If I open the recordsource on its own, as a table in datasheet view, there are no crashes happening.

I'm wondering if an anyone else has seen cases where a form in datasheet view is less stable than the normal form view when SQL Server is used.

Windows Version: 10.0.17763.7136
Windows Bitness: 64-bit OS

Office Version: 16.0.17928.20512
Office Platform: x86
Release: 2408

 

[The_Doc_Man]

On any machine that exhibits the crash, see if you can run the Event Viewer to find that crash. From the Win11 Start Button, click All> and then scroll down to find Windows Tools; Event Viewer will be in the middle of that list. You would probably want the System events, but the Applications Events MIGHT have the crash if the regular System events doesn't.

If you have a date & time of day for such a crash, the system Event Viewer will find it easily because system events are sorted chronologically. A system "task crash" event will name one or two programs active during the crash (two file names if a sub-process / child process / external library module was involved). It will tell you an exact error message. There will be a status code that would look like either 0x80nnnnnn or 0xC0nnnnnn where the nnnnnn will be a six-digit hexadecimal number. The program addresses that are normally part of such a report are unlikely to be helpful to us because the Access program is not open-sourced.

 

[MajP]

Post in thread 'Invalid Procedure Call Or Argument On Everything!' https://www.access-programmers.co.u...or-argument-on-everything.333154/post-1948521

Post in thread 'Crash When Add Option Group' https://www.access-programmers.co.uk/forums/threads/crash-when-add-option-group.151609/post-1636921