Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Invalid field name in on ASP.net server

Status
Not open for further replies.

bobhagan

MIS
Apr 28, 2001
111
US
I have a group of reports I'm converting from CR 8.0 to web CR.NET. All the reports but one convert and run from my machine as localhost and when copied to our server. One report works on my machine, but gives an "invalid field name" error when run from the server.

This report is slow (15 seconds for a supervisor, 2 minutes for site). It has 3 subreports and takes one of three possible parameters (worker, supervisor, site) plus start and end dates. I'm passing information to the aspx page in the query string and supplying null values for the two unused parameters:

...runreport.aspx?reportname=thisreport&site_cd=QUEENS&mgr_key=null&wkr_key=null&start_dt=06/01/2004&end_dt= 06/30/2004


With the report on my development machine and the server, I can literally edit the querystring changing localhost to servername. It runs from localhost, not from the server. Some threads here suggest there might be problems with date parameters. I've been removing things one at a time. I will try to hardcode the dates tomorrow, but I don't understand why one report would work in one environment and not the other when supplying it exactly the same information.

Any ideas?
Thanks
Bob Hagan
 
Removing the date params works, so this seems to be a date format issue.

As above, I was passing in the dates as char strings to the report running on the MS Oracle OLEDB provider. This works both in localhost and on the server in a report that uses just a start and end date where the param in the report is of type date. This also works on the report in question on localhost.

After looking here and on the ASP.NEt Crystal forum Ive done a few more things. I tried converting the param inside a function to a date in the report, and also using .net

Dim Start_dt as date = convert.date(Request.QueryString("Start_Dt"))

Neither of these error, they just timeout after a period.

Still hoping.
Bob Hagan
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top