Solution:
Add the Culture setting in the ReportViewer.aspx like below:
<%@ Page Language="C#" AutoEventWireup="true" Inherits="Microsoft.ReportingServices.WebServer.ReportViewerPage" Culture="en-AU"%>
Tip:
You can find the page here: C:\program files\microsoft SQL Server\MSQL.3\Reporting Services\ReportServer\Pages
If you want to find the path to the page go to your IIS under Default website select ReportServer or Reports Folder > right click Properties...
Friday, August 26, 2011
Friday, August 19, 2011
"Can't edit module" when running a VB project
When trying to run a VB project users of SourceSafe frequently encounter the error "Can't edit module." This message is not very helpful as it does not indicate precisely where the problem lies.
There are numerous suggestions for how to fix this issue. Those solutions which we have found to be most helpful are listed below in order of most to least helpful:
- Verify that checked-in components do not contain any blank event procedures. The IDE compiler automatically tries to remove any blank procedures when the project is run. If the file is checked-in, it is read-only, so the change cannot take place. Manually remove the blank procedures or check out the affected forms and run the project once to have the compiler automatically remove the blank procedures.
- Save, close, and check-in all files. Save and check-in the project file. Close and re-open VB.
- Delete the .vbw file for the VB project. It will automatically recreate it the next time you open the project.
There are numerous suggestions for how to fix this issue. Those solutions which we have found to be most helpful are listed below in order of most to least helpful:
- Verify that checked-in components do not contain any blank event procedures. The IDE compiler automatically tries to remove any blank procedures when the project is run. If the file is checked-in, it is read-only, so the change cannot take place. Manually remove the blank procedures or check out the affected forms and run the project once to have the compiler automatically remove the blank procedures.
- Save, close, and check-in all files. Save and check-in the project file. Close and re-open VB.
- Delete the .vbw file for the VB project. It will automatically recreate it the next time you open the project.
Subscribe to:
Posts (Atom)