I'm trying to determine if a file exists by using the line:
=system.IO.File.Exists("C:\camera.log")
I know for a fact the file exists. But no matter how I phrase the line of code, it always returns false. I've changed the permissions in RSPreviewPolicy.config and rssrvpolicy.config to no effect. I'm running the report locally, so permissions shouldn't come into it.
Please let me know if I can provide any further information.
UPDATE: The line works fine in a regular Console Application. So far as I know, this problem is unique to .rdlc reports.
UPDATE 2: It also works on previewed SSRS reports. But I have verified it also doesn't work on another .RDLC report.
Related
Does anyone know how I can fix this?
In MSSMS I'm running query's where I want the result to be saved to file.
I choose that option in the toolbar and it was working find until yesterday when it stopped asking me where I want to save the result.
It's running the query and tells me that the "Query executed successfully" but I don't know where the result went. I've looked in the default folder for where MSSMS is supposed to save files but there is no new or just updated file there.
The only thing I tried so far is switching back and forth between result to grid and to file. And of course restarted my computer.
Greetings to the community.
I have the following report in Crystal-Reports using VB.NET and it comes out in "order" so to speak. Each account has its credit detail.
However, in this image I don't understand why it could be wrong. It is another report with other parameters, but the idea is still the same, only here it does not list the detail of each accounting account.
I am new to Crystal-Reports and I don't know where the error might be. I checked the following and everything is identical in both reports:
Formulas.
Section Wizard.
EDIT (MORE DETAILS):
The report that is causing me problems has the following structure:
However, I go by the report which is perfect and does not cause me any problems (practically a copy and paste):
Assuming the content of your Details section (or some other section) is "missing":
Check it is not set to Hide (Drill-Down OK)
Check it is not set to Suppress (either directly or via an expression)
If that was not the issue, please clarify what content and in what section is not visible.
I'm quite new to .NET and very new to TableAdapters. I am currently working on updating an existing program and am required to alter some SQL code to update a field in one of the databases where I work. I've changed my VB and code and everything in terms of my UI is good to go so I am now trying to update the TableAdapter that is used to account for my change.
I am adding a parameter (#jobNumber) and wish to update the field 'DISCRETE_JOB' in the database table I'm working in.
I've added in the 'DISCRETE_JOB' parameter to my INSERT INTO statement as the third parameter and added the '#jobNumber' as the third parameter in the VALUES() line of my SQL.
After Finishing the changes are there when I bring up the tool-tip (by hovering mouse over the TableAdapter Query) but the actual parameters listed beside the name of the Query int the DataSet.xsd file are not updated
Looks like-> InsertData(#Param1,#Param2,#Param3)
Should look like -> InsertData(#Param1, #Param2, #jobNumber, #Param3)
Even after saving changes to the .xsd file the parameters don't SHOW the changes of parameters. I also took a look at the DataSet.Designer.vb file for the DataSet.xsd file and it doesn't appear that my new parameter has been taken into account.
Again, I am new and there may be a couple of things I'm supposed to do to make these changes happen, but I just don't want to mess anything up, as there's a lot of queries in the file for this program.
Thanks! Let me know if I need to provide more detail.
UPDATE: I fixed my problem, though I'm still not sure exactly what was going on and why the parameters weren't updated automatically.
Here's the fix:
The SQL code I added remained in place, but I needed to manually add the parameter I wanted. To do this I went to the properties of the query in question and clicked 'Add', filling in the correct fields based on what the existing parameters looked like as a guide line.
Hopefully this can help someone else too!
I struggled with this issue for too long before finally tracking down how to avoid/fix it. It seems like something that should be on StackOverflow for the benefit of others.
I had an SSRS report where the query worked fine and displayed the string results I expected. However, when I tried to add that field to the report, it kept showing "ERROR#". I was eventually able to find a little bit more info:
The Value expression used in [textbox] returned a data type that is
not valid.
But, I knew my data was valid.
Found the answer here.
Basically, it's a problem with caching and you need to delete the ".data" file that is created in the same directory as your report. Some also suggested copying the query/report to a new report, but that appears to be the hard way to achieve the same thing. I deleted the .data file for the report I was having trouble with and it immediately started working as-expected.
After you preview the report, click the refresh button on the report and it will pull the data again creating an updated rdl.data file.
Another solution to this issue is to click Refresh Fields in the Dataset Properties menu.
This will update the list of fields, and force SSRS to get new data, rather than relying on a cached version.
I'm facing an error with a .prpt file.
While running the prpt in report designer it just works fine .
But when the same prpt ran in PUC (user console), the report contents are not displayed.
It is a simple report containing total 8 columns with only text and number fields in the detail section and only labels (formulated also) in headers.
Please help with your valuable tips
Check the server logs - there'll be an exception. I've seen this before - frequently it is due to layout issues, not sure why but for some reason in some cases the server bombs, yet the client does manage to render it. Double check the obvious like overlapping elements etc.
Also check the version of your PRD client, and the exact version of the reporting libraries on the server, they MUST match.
I've seen this happen when you have a prpt file that was created in an older (or newer) version of PRD than the server. You'll get javascript errors and onscreen you'll just see a blank page/tab. Make sure your version of PRD matches the server version.