threecans
asked on
Crystal Reports Viewer - Export Button Not Working
I have an application that was developed in Visual Basic and implemented in 2002. Part of this software featured a custom report viewer which used crystal runtimes and the crystal report viewer. Operators were able to generate reports and use the Export function to create PDF versions of the reports and save them on the hard drive. This worked splendidly until two weeks ago.
The company using the software was small and did not have a lot of formal security on their network or workstations. This company was recently bought by a larger company and the workstations were moved to the large company network. As soon as this move occurred, the Export button in the crystal viewer ceased working.
The only thing that is immediately evident is that the large company has a high level of workstation security: a security "policy" is applied to each workstation when a user logs in. The company's network personnel are not intimately aware of what that policy entails as that job is outsourced to another company and I am travelling the corporate maze to try to find the right person to provide some answers.
There are several workstations using the application. Most are running windows 2000 but several are on Windows XP, SP 2. Up until they moved to the new network, the Crystal viewer was working on both operating systems.
So, the question for the forum is: Am I traveling the right path? Is this a security issue? If so, what can I do to get the export button to work?
The company using the software was small and did not have a lot of formal security on their network or workstations. This company was recently bought by a larger company and the workstations were moved to the large company network. As soon as this move occurred, the Export button in the crystal viewer ceased working.
The only thing that is immediately evident is that the large company has a high level of workstation security: a security "policy" is applied to each workstation when a user logs in. The company's network personnel are not intimately aware of what that policy entails as that job is outsourced to another company and I am travelling the corporate maze to try to find the right person to provide some answers.
There are several workstations using the application. Most are running windows 2000 but several are on Windows XP, SP 2. Up until they moved to the new network, the Crystal viewer was working on both operating systems.
So, the question for the forum is: Am I traveling the right path? Is this a security issue? If so, what can I do to get the export button to work?
ASKER
This is a client side application.
Crystal does need to use the temp directories and they would need permissions to the directory where the application is.
mlmcc
mlmcc
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was able to use the direction offered by the experts exchange to seek a solution. There was not a single source for the solution but a combination of many resources.
Is the application installed on the client or is it server based?
mlmcc