beckybear3
Programmer
We have a piece of legacy software written eons ago that is VB6 using the Crystal ActiveX control with version 8.5.
About 50 or so users have this program loaded and it runs a single crystal report from a server location. Most days, everything runs just fine, but lately more and more we've been having a problem where our some of our users get the message "Runtime Error 20544. Access to report file denied. Another program may be using it." The same user will continue to get this error, even after rebooting, while others continue with no issues. It's never the same people affected day to day. And it always works for everyone the next day.
I've read about a 20 limit on previewed reports, but new users can log in and use the program with no problem, so if it's a connection limit, it doesn't seem right that new users would work. We cannot reliably reproduce the problem.
So I guess my questions are, do you have any idea why it would work the next day without a reboot of the server or the user's machine? If this is a limit problem, where is that limit stored, or how can I test to see that it is the limit problem? What else could it be and is there anything I can add in the VB program to try and prevent this (cleanup, checks, etc.)?
Oh, and I have discovered this ActiveX control is no longer recommended, but I really don't want to rewrite this thing now, as this component belongs to a whole set of software that's being redesigned and will be rewritten in probably a year or so as a whole different animal and web app.
Thanks in advance for any help you can offer for this frustrating problem.
About 50 or so users have this program loaded and it runs a single crystal report from a server location. Most days, everything runs just fine, but lately more and more we've been having a problem where our some of our users get the message "Runtime Error 20544. Access to report file denied. Another program may be using it." The same user will continue to get this error, even after rebooting, while others continue with no issues. It's never the same people affected day to day. And it always works for everyone the next day.
I've read about a 20 limit on previewed reports, but new users can log in and use the program with no problem, so if it's a connection limit, it doesn't seem right that new users would work. We cannot reliably reproduce the problem.
So I guess my questions are, do you have any idea why it would work the next day without a reboot of the server or the user's machine? If this is a limit problem, where is that limit stored, or how can I test to see that it is the limit problem? What else could it be and is there anything I can add in the VB program to try and prevent this (cleanup, checks, etc.)?
Oh, and I have discovered this ActiveX control is no longer recommended, but I really don't want to rewrite this thing now, as this component belongs to a whole set of software that's being redesigned and will be rewritten in probably a year or so as a whole different animal and web app.
Thanks in advance for any help you can offer for this frustrating problem.