I have an MS Access report that crashes when the mouse wheel is used to scroll through the report in view mode. I've been verbose. For a quicker version, read bold text only.
Before I go further, when I say crashes Access, I mean a spinning wheel pops up and Access becomes unresponsive (i.e. "Not Responding"). The only way to get out of this state is to force Access to close. No error codes or explanation are given.
This problem only occurs in report view mode. If I open the report in design, layout, or print mode there are no issues. The issue only occurs when using the mouse wheel. Scrolling with the vertical scroll bar or arrow keys poses no problem. This issue is repeatable across users on different machines with different mice. Though it is likely we're both running Access 2016 and Windows 7 Enterprise SP1. I have not configured any "on mouse wheel" vba code anywhere in the database.
The report itself contains ~20 fields, 2 very simple subreports (single tables with 2 columns liked off a single field on the main report), and a rather lengthy report body with 3 layers of grouping and roughly 150 rows sprinkled among the various groups. The rows are retrieving longer memo fields (hundreds of characters per row).
In addition, I have added a field that numbers each row (text box with control source=1, configured as a running sum "over all"). Oddly, if I delete the running sum text box, the problem goes away. If I add it back again, the problem returns. This is the only calculated field in the report. All of the other data originate from queries. I should point out that the report worked fine with the field that numbered each row prior to adding the two subreports. So it seems that the combination of counting from 1 to 150 + subreports is overwhelming Access. [This is surprising to me given that my database is fairly small - 15-20 tables with less than 1000 rows total.]
Configuration of text box that seems to be causing the problem
Has anyone seen this problem before? Does anyone know of a work around I could use to number each row versus just storing the row number in a table? [I don't want to do it this way because I'd like the numbers to remain sequential and in order when a user adds or deletes a row or if a subset of rows is queried. I could write code to detect changes and renumber, but I'm hoping for something simpler.]
Related
Updated***
To quickly summarize what I said before which was lengthy and probably too roundabout confusing...
My issue was I have a main form interface with 2 subforms that does the following:
the First one is always shown for current daily event task(s) based on a label control with current date or any given dates via the prev/next toggle buttons as criteria.
The second one is part of the main subform that will be called based on the selection from the main navigation controls. This subform shows all the event tasks that are created in the database.
Both use saved query select statements with a snapshot and no record lock as recordsource in a continuous form. The table source is linked via split database in the same shared network drive and the table itself contains only 8 fields:
ID (12 chars randomly generated with specific sequence via VBA with no duplicate allowed)
Event Name (Text)
Event Desc (Long Text/Memo)
Occurrence (Text)
Start Date (Date)
Selected Day (Text)
Allow Weekend (Text)
Active (Boolean)
To edit a selected record, it will be called and populated onto a popup unbound model form via VBA. Here everything works fine as for records with fewer chars found in the Event Desc field. However, for records with a large number of chars (so far those that I noticed with issues were the ones with >4000 chars). I can call and display them fine to the detail view form (unbound) but when making edits, by the time it gets to the updating field for Event Desc, it would generate the record locking error by the same user (me) for those with large text size.
After several trials and errors, I noticed it has to do with the displayed continuous subforms that I have presenting. I noticed that the form for them were originally set as dynaset to which I tried to switch over to snapshot and it was a hit and miss (mostly miss). I don't know how much of this setting was an issue to the record updating as I had no problem saving records with smaller character counts.
Finally, I decided to before saving the record, I went and remove the recordsource for both of the continuous forms to empty ("") then save then reassign the query (saved or direct doesn't matter) and it worked without errors after. I personally don't like doing it this way as it makes the continuous forms update look ugly and not smooth (see the #Name?) in the assigned controls due to unrecognized control source since the recordsource is now empty. However, this was the best way that I could think up at the moment.
I even tried using a bounded form for editing the record instead of the unbound form and the same error outcome, but that time it gave a different record locking error# but pretty much for the same reason.
I'm sure this issue is not related to how my VBA code was written nor the queries used in the continuous forms. It's most likely the form settings themselves or just some limitation of Access?
I have a report in SSRS that contains many textboxes that pull data from our Epicor 10 database. One in particular only displays the first 30 characters. In our ERP system, the field format is x(16000) so the user can enter quite a bit of data. The textbox size is definitely large enough to contain more than 30 characters (it's about half a page wide). I enabled the "Can Grow" option, and I've expanded the text box box horizontally and vertically, but still, only the first 30 characters display.
Typically, the text in this field begins with a number (these are shipping comments so it will say, for example, "2 Skids #60 boxes... etc.). That's the only real difference I can find between this particular text box and the other ones on the report that display the entire field value. Am I missing some Option, or do I need to convert the field in some way?
Thanks in advance.
Pull up your report in System Management | Reporting | Report Data Definition and check to see if it is a Calculated field limited the number of characters as Hannover Fist has posited. Searching the table Ice.RptCalcField I see a number of out of the box things that limit to x(30), but I don't see anything larger than x(2000). There are couple of DataFields in Ice.ZDataField that are that large, so I am assuming this isn't an out of the box sort of thing.
If the Data Definition field is set to x(16000) try changing it to x(100) and see if that makes a difference. Maybe the value you have is large for the printing framework and it is reverting to some sort of default.
Good luck, I would be interested to see how this turns our for you as we may eventually run into a similar problem.
I been trying to figure out a answer to this question. Maybe its just not possible. But basically I have loaded into a table 20 Million records.
I am using SSRS to get the report and using parameters. I got one paremeter which has the selection process, so say this is userID. There is over 1000 userids. When I select all userids in the parameter the report (it is a bar graph) fails to show all the results.
But when I say select about 200-400 userids the report will show up the results with the bar graph.
The data looks clean, i just think there is a limit which is holding it back bringing everything.
Step is when I click on view report it would just click and then the screen will just remain as it is. Anyone come across any of these issues or can help thank you.
Set interval of axis from Auto to 1 (X or Y, concerned where you are showing user id).
One of our SSRS 2005 reports would time out when executed at the "All" level (was returning upwards of 80K records), so I added a group to the table whose sole purpose was to force a page break after every 500 records. I found the grouping in another post. It looks like this:
=IIF(Fields!ShowPageBreaks.Value = 1, Floor((RowNumber(Nothing) - 1) / 500), Nothing)
The problem is that the user sort no longer works correctly. E.g., "A"s show up at the top of multiple pages. I haven't been able to find any pattern in how SSRS decides to perform the sort. I've tried playing around with the Sort Scope and the Sort Target, like setting one to the Table and one the other to the Group, both to the Table, one or the other to nothing, etc and nothing seems to work.
Has anyone found a solution to a problem like this?
The sorting is happening within each group, aka, "working as intended." You're creating a somewhat arbitrary and random set of record groups based on row position in an un-ordered set.
You need to find a way to sort properly (in the SQL?) prior to applying any sort of grouping, or use a less random means of paging.
I'm using VS2005 to create my reports.
I have a matrix report that works beatifully. I have country going down on the left hand side (row group called "matrix1_country_name") and data going across for 2 column groups, product_node and month (column groups "matrix1_Node" and "matrix1_calendar_month_name" respectively)
The only thing I want to improve is that this report will always show 5 year/60 months of data, and with multiple nodes I'd rather have each node be on its own page (Ideally I'd love to have it on the same page but in the rows just below to first node, but I'm not sure that's even possible).
I've seen numerous responses on these boards about putting in page breaks on column groups, but I can't seem to find how to do that in VS2005. The examples I've read that can do that seem to have a different interface so I'm guessing they aren't in VS2005.
Does VS2005 allow you to add page breaks after each group item and I'm just missing it? Or is there a trick I can do to get that to happen? I've also read about nestin matrix reports in list reports but that seems more complicated than doing the page break on the column group, so I'd rather do the easiest solution if I can.
Ah, I see pagebreaks are ignored on column_groups. Well I guess I'll try one of these workarounds.
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/ea9d795b-8d17-41d2-a1d7-a4069ebb4539