If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
crosstab qry as report source breaks Access2007
We have 3 reports whose record sources are crosstab queries. All have work
fine on the pc's running Access2003. But, the one pc running Access2007 doesn't like the crosstab queries as the report source. We don't get an error - only the dreaded 'Access has encountered a problem and has closed...' It totally shuts down the access application. I stepped through the little bit of onOpen code while opening the reports and all works fine. I open the crosstab query and it opens just fine. To test the theory that it is a crosstab source problem, I tried to recreate one of the reports and when any crosstab query was selected as the source there were no fields to choose from. Is this a known problem in Access2007 or some new setting I'm not aware of? Any suggestions appreciated. -- TIA Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...ports/200708/1 |
#2
|
|||
|
|||
crosstab qry as report source breaks Access2007
Yes: if you programmatically assign fields to controls in Report_Open,
Access 2007 will crash. We have this issue listed he http://allenbrowne.com/Access2007.html#Bugs Hopefully MS will fix it in Service Pack 1. -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "backToASP via AccessMonster.com" u27805@uwe wrote in message news:76727dab74023@uwe... We have 3 reports whose record sources are crosstab queries. All have work fine on the pc's running Access2003. But, the one pc running Access2007 doesn't like the crosstab queries as the report source. We don't get an error - only the dreaded 'Access has encountered a problem and has closed...' It totally shuts down the access application. I stepped through the little bit of onOpen code while opening the reports and all works fine. I open the crosstab query and it opens just fine. To test the theory that it is a crosstab source problem, I tried to recreate one of the reports and when any crosstab query was selected as the source there were no fields to choose from. Is this a known problem in Access2007 or some new setting I'm not aware of? Any suggestions appreciated. |
#3
|
|||
|
|||
crosstab qry as report source breaks Access2007
There is at least one method/solution for creating crosstab reports without
first knowing any of the field names and without having to assign control sources at run-time. -- Duane Hookom Microsoft Access MVP "Allen Browne" wrote: Yes: if you programmatically assign fields to controls in Report_Open, Access 2007 will crash. We have this issue listed he http://allenbrowne.com/Access2007.html#Bugs Hopefully MS will fix it in Service Pack 1. -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "backToASP via AccessMonster.com" u27805@uwe wrote in message news:76727dab74023@uwe... We have 3 reports whose record sources are crosstab queries. All have work fine on the pc's running Access2003. But, the one pc running Access2007 doesn't like the crosstab queries as the report source. We don't get an error - only the dreaded 'Access has encountered a problem and has closed...' It totally shuts down the access application. I stepped through the little bit of onOpen code while opening the reports and all works fine. I open the crosstab query and it opens just fine. To test the theory that it is a crosstab source problem, I tried to recreate one of the reports and when any crosstab query was selected as the source there were no fields to choose from. Is this a known problem in Access2007 or some new setting I'm not aware of? Any suggestions appreciated. |
#4
|
|||
|
|||
crosstab qry as report source breaks Access2007
Don't tease, Duane! :-)
Perhaps you are talking about this link: http://www.access.hookom.net/Dynamic...rosstabRpt.htm -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Duane Hookom" wrote in message news There is at least one method/solution for creating crosstab reports without first knowing any of the field names and without having to assign control sources at run-time. -- Duane Hookom Microsoft Access MVP "Allen Browne" wrote: Yes: if you programmatically assign fields to controls in Report_Open, Access 2007 will crash. We have this issue listed he http://allenbrowne.com/Access2007.html#Bugs Hopefully MS will fix it in Service Pack 1. "backToASP via AccessMonster.com" u27805@uwe wrote in message news:76727dab74023@uwe... We have 3 reports whose record sources are crosstab queries. All have work fine on the pc's running Access2003. But, the one pc running Access2007 doesn't like the crosstab queries as the report source. We don't get an error - only the dreaded 'Access has encountered a problem and has closed...' It totally shuts down the access application. I stepped through the little bit of onOpen code while opening the reports and all works fine. I open the crosstab query and it opens just fine. To test the theory that it is a crosstab source problem, I tried to recreate one of the reports and when any crosstab query was selected as the source there were no fields to choose from. Is this a known problem in Access2007 or some new setting I'm not aware of? Any suggestions appreciated. |
#5
|
|||
|
|||
crosstab qry as report source breaks Access2007
Allen,
That solution is one I always recommend for date intervals since dates are actually numeric. The one I had in mind is hosted over at Roger's site: http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='Cross%20Tab' This solution uses much less code and is much more efficient than the solution that assigns control sources at run-time. -- Duane Hookom Microsoft Access MVP "Allen Browne" wrote: Don't tease, Duane! :-) Perhaps you are talking about this link: http://www.access.hookom.net/Dynamic...rosstabRpt.htm -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Duane Hookom" wrote in message news There is at least one method/solution for creating crosstab reports without first knowing any of the field names and without having to assign control sources at run-time. -- Duane Hookom Microsoft Access MVP "Allen Browne" wrote: Yes: if you programmatically assign fields to controls in Report_Open, Access 2007 will crash. We have this issue listed he http://allenbrowne.com/Access2007.html#Bugs Hopefully MS will fix it in Service Pack 1. "backToASP via AccessMonster.com" u27805@uwe wrote in message news:76727dab74023@uwe... We have 3 reports whose record sources are crosstab queries. All have work fine on the pc's running Access2003. But, the one pc running Access2007 doesn't like the crosstab queries as the report source. We don't get an error - only the dreaded 'Access has encountered a problem and has closed...' It totally shuts down the access application. I stepped through the little bit of onOpen code while opening the reports and all works fine. I open the crosstab query and it opens just fine. To test the theory that it is a crosstab source problem, I tried to recreate one of the reports and when any crosstab query was selected as the source there were no fields to choose from. Is this a known problem in Access2007 or some new setting I'm not aware of? Any suggestions appreciated. |
#6
|
|||
|
|||
crosstab qry as report source breaks Access2007
Thanks to both of you for the info - I assumed it was an Access 2007 issue
because the 2003 versions were running just great. I can make a pretty easy fix - I can name my columns because the reports are designed for current year and previous year columns of data only. Then I can change my two column headings in the report to be lable fields to display the selected year and previous year from the Report Selection Form. Thanks again Duane Hookom wrote: Allen, That solution is one I always recommend for date intervals since dates are actually numeric. The one I had in mind is hosted over at Roger's site: http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='Cross%20Tab' This solution uses much less code and is much more efficient than the solution that assigns control sources at run-time. Don't tease, Duane! :-) [quoted text clipped - 37 lines] of? Any suggestions appreciated. -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...ports/200708/1 |
Thread Tools | |
Display Modes | |
|
|