Sage 100

Weird Crystal Reports problem. Client has a main report which includes a sub report. It works fine on my system but generates the attached error on the client system, for all workstations, for all users. The sub report has a parameter field called DateRange which requests a date from the user at run time. Again, this works fine on my system but when the client runs it, they get the attached error. If I go to the client's system and use their CR to edit the report and eliminate the DateRange parameter field from the sub report, then the report runs. No filtering, of course. If I then manually recreate the DateRange parameter, again, on their system, then the attached error reappears. Still trying a couple of other ideas but I don't have a lot of hopes up at this point......

Did you check the data type? Is the field data type 'date' or 'datetime'?

Is this a sales order FORM, i.e. not a report? Why are you using a date range parameter? To filter what??

@DougHiggs Data type is Date.

@ThereseLogeais it's a form that was modified from the original sales order form. The history sub form goes to the AR_InvoiceHistoryHeader file and selects past history for the customer, then prints details from the AR_InvoiceHistoryDetails file in a block on the form. The title of the form is called a ""work order"" and the field technician can see the history for the customer going back as far as ..... Our client has several versions of this form and all of them work without a Date parameter field, ergo, we just hard code a couple of them to go back six months or twelve months and in one instance, it prints all history for their customer.

So if you remove the date range parameter, it works? KB is saying there is something wrong with the path but that doesn't make sense if it works without the date parameter.

@ThereseLogeais Something like that. If I put the parameter field back in, it can't find the report file. If I take it out, it finds the report file but won't ask the user for the date.

Is this running from the Sage 100 menu? Can you use a UNC path instead of the mapped drive M:? Does it work stand-alone (off teh Sage 100) menu on the client machine?

@DougHiggs It's running from the Sales Order Printing screen. The form is selected in the Form Code. I've actually deleted the form and recreated it a couple of times to no avail. Oddly, if I click Design, Crystal can find the report and I can modify it but as soon as I try to print it, it gives the error above. I haven't tried to test it as a standalone form. The main form uses a *.wrk file but the DateRange parameter field doesn't refer to that file.

I had a similar problem, the main report used a WRK file and the sub report had non WRK tables. I added the WRK table used on the main report to the sub-report, without adding any field from the WRK file and it resolved my issue.

@LisaDion I'll give that a try........ EDIT: I just checked my local copy and it does, in fact, include the WRK table. I'll verify on theirs........

How is the DateRange Field being passed from the Main report to the Subreport? Is it a Global field? Maybe something in the Subreport link is not right

Quick update: @LisaDion Customer report has the WRK table. @KennyDaniel The DateRange field is not passed from the Main report to the Subreport. Again, this works on my system but not theirs. That's the most significant source of confusion. I looked at the subreport links and they are all correct. Also, other reports using this basic layout have the exact same subreport links and they work beautifully. I also changed the DateRange field to Date_Range which made no difference. Also, I set the parameter field order to put the Date_Range field at the top of the list. No difference there, either.

@DougHiggs Partial success changing the type from Date to DateTime. I would prefer to have the client simply enter the date but using DateTime make them have to click on the little calendar icon. Also, on my system, the type is simply Date.

Glad it is working. Clicking the calendar icon doesn't seem too bad.

No, not so bad. Most people seem to want to click that dang thing anyway whereas I'm a keyboard only fanatic! I'm still baffled as to why it's so different between my installation and theirs. I checked all of the relevant report and general options and they're all identical. As I said in the original title: Weird.

Exact same Sage 100 versions ?

No, however, I did test it on all of my local Sage versions from 2014 through 2016 and it worked every time with the original configuration. Anyhoo, I've spent too much time on it as of now. At least, I'll recognize this error again if it comes up......