FYI,
I was getting access violation errors in my report using CR native SQL Server driver accessing SQL Server 7.0 stored proc. My report required that I pass a CSV list of IDs to include. The list could be very long so I created the report to receive 10 string parameters, pass them to the proc, where the proc reassembles the list and uses them all. This worked well, until I passed more than about 919 total bytes of data. This caused the access violation (and a crash) in P2SSQL.DLL. By researching this issue on CR's support site (which didn't address the issue), I got the idea to switch the data source to OLEDB using Microsoft OLEDB Provider for SQL Server. This corrected the violation and I was able to pass more that 1200 total bytes of data through the parameters (I still had to chop up the list). I don't know if there is a limit, but if I hit it I'll write, especially if I find a work-around. If you know of a limit here, please post it so others can learn from us.
I think that I spend as much, if not more, time working around the limitations and bugginess of CR than I do building what my clients are paying me to build.
Craig Boland
I was getting access violation errors in my report using CR native SQL Server driver accessing SQL Server 7.0 stored proc. My report required that I pass a CSV list of IDs to include. The list could be very long so I created the report to receive 10 string parameters, pass them to the proc, where the proc reassembles the list and uses them all. This worked well, until I passed more than about 919 total bytes of data. This caused the access violation (and a crash) in P2SSQL.DLL. By researching this issue on CR's support site (which didn't address the issue), I got the idea to switch the data source to OLEDB using Microsoft OLEDB Provider for SQL Server. This corrected the violation and I was able to pass more that 1200 total bytes of data through the parameters (I still had to chop up the list). I don't know if there is a limit, but if I hit it I'll write, especially if I find a work-around. If you know of a limit here, please post it so others can learn from us.
I think that I spend as much, if not more, time working around the limitations and bugginess of CR than I do building what my clients are paying me to build.
Craig Boland