Need to print a crosstab report without complete data

[Lkwdmntr]

So I did a complete reinstall of 365, and as I said, it worked for the first time. I could see the query, but the next time I tried, it crashed. I looked in the Event Viewer, and this is what was found.

Faulting application name: MSACCESS.EXE, version: 16.0.18324.20168, time stamp: 0x677829a1
Faulting module name: ntdll.dll, version: 10.0.26100.2454, time stamp: 0x7cb6b6a8
Exception code: 0xc0000374
Fault offset: 0x00000000000881f5
Faulting process id: 0x2B88
Faulting application start time: 0x1DB64388FE7DA79
Faulting application path: C:\Program Files\Microsoft Office\root\Office16\MSACCESS.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 317bc520-dab1-4550-b497-07e5b754f14c
Faulting package full name:
Faulting package-relative application ID:

 

[DHookom]

I’m not sure if this helps but I found this page about ntDLL.dll.

 

[Gasman]

So I did a complete reinstall of 365, and as I said, it worked for the first time. I could see the query, but the next time I tried, it crashed. I looked in the Event Viewer, and this is what was found.

Faulting application name: MSACCESS.EXE, version: 16.0.18324.20168, time stamp: 0x677829a1
Faulting module name: ntdll.dll, version: 10.0.26100.2454, time stamp: 0x7cb6b6a8
Exception code: 0xc0000374
Fault offset: 0x00000000000881f5
Faulting process id: 0x2B88
Faulting application start time: 0x1DB64388FE7DA79
Faulting application path: C:\Program Files\Microsoft Office\root\Office16\MSACCESS.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 317bc520-dab1-4550-b497-07e5b754f14c
Faulting package full name:
Faulting package-relative application ID:

0xc0000374 - Google Search

 

[Lkwdmntr]

Thanks for that information. I did the scans and ran a malware scan; it got a few things, but nothing major. It's still happening every time I go to access that query. I'm perplexed. My next option is to complete a Windows installation, reinstall 365, and see what happens. It is troubling that it only happens with that query "qrptSAsByWeek'. I have no trouble accessing any other queries. I have never used the "Transform' statement and am wondering if that's what is causing the issue. I will try the Windows installation; it wouldn't hurt to get a fresh start. I usually do one every three years, and I think it's been five.

 

[DHookom]

Did the example I attached in post #9 work as expected?

The only other thing I see in the application is the data type of parameters in crosstab queries (or their sources) typically need to be specified. This isn't typically the case when the column headings are specified. It would hurt to modify qfrmWeeklyReports like:

 

[Lkwdmntr]

I am trying all the suggestions with no success. I am resetting my computer. It doesn't make sense that it works on my work computer and not my personal one. I'll let you know.

So, if I do get this to work, my next question is to ask why there is a W0. It doesn't seem very clear. I tried to eliminate it and lost the week 12 data on the report.

There are also duplicate Actions displayed on the report. Attached is the report the way it should look, except for the weeks not working on this one. It is also not sorting by index, and won't let me sort it because the index isn't on the report.

 

[DHookom]

There is a week 0 because the expression creating the column heading in the crosstab query calculates the number of weeks between the start date and the data date. You can easily add 1 so your start week becomes Week 1 but nobody sees the Week 0.
Expr2: "W" & DateDiff("w",DMin("StartDate","qfrmWeeklyReports"),[ChallengeDate])+1

You can use the Format property of a text box to display an X for all positive values.

You should also be able to add the index field so you have something to sort by in the report design.

 

[Lkwdmntr]

Well, this would all be great if I could get in and access the query. I'll have to wait till I'm back on my work computer. I did a fresh install of Windows, and I still can't open the query without it crashing.

Still have the issue of duplicated actions.

 

[DHookom]

I had some issues simply running the report until I deleted a bunch of the text boxes in the header (using tempvars etc). The issue I had wasn't related the beef of the report, just the non-record data.