Filtering reports based on dates on Ipad is not working

[kingcarol]

I have some reports that are filtered by dates entered in fields on a UX component. The reports open fine as html or pdf on a pc. But one of my customers called me who has a Surface, and when he clicks the button to open the report, absolutely nothing happens. I tried it on my Ipad and it is doing the same as his Surface... nothing happens... no message, no nothing, just sits there, report never opens. Other reports that are not based on ranges of dates open fine as html or pdf on my iPad. The date arguments for my report are based on the date fields on the ux component. I did experiment with setting session variables for the dates and used those as the arguments for the reports, but that also fails on Ipad and works fine on pc.

I am on build 3962-4772. My customer tells me that the reports used to open fine on his Surface, but now they don't. The other weird thing is that I have a Surface, too, and the reports open fine on it... but not on my customer's Surface. Does anyone have any clue about what is happening?

[Pizzadude]

Re: Filtering reports based on dates on Ipad is not working

This sounds like the same problem I had when I tried to render reports as .pdfs on an iPad. It had to do with rendering fonts. I forget exactly how I diagnosed it, but I added this code to all my xbasic functions that generate reports....

DIM PrintOptions as P
With PrintOptions
.MultilingualSupport = .t.
.EmbedFonts = .t.
End with

If you are using the builder "Open a Report, Label or Letter layout" to generate the report, these same options are available. Open the "PDF Options" and at the bottom is a button "Set PDF Options"

[kingcarol]

Re: Filtering reports based on dates on Ipad is not working

Thanks, Joe. That's a good thought, but I had learned about that before from Alpha, and I do include that code IF I generate a pdf using Xbasic. In the case of these reports, I generate them using Alpha's report genie, and have even made sure that those Print Options are there, especially the embed fonts one. ALSO, the PDF Printing Options in my project properties are check marked to imbed fonts, and multilingual support.

It is ONLY reports that get their DATE arguments directly from date fields on the window that has the button to open the report. It's like they don't even try to open. Other reports are opening fine on Ipad.

[Pizzadude]

Re: Filtering reports based on dates on Ipad is not working

So I just got out my iPad... I am using Chrome.

I have a few reports that render as .pdfs, that are not based on date controls. These work.

But I have some that are based on unbound date controls on a UX. In my application I open the reports as html (works fine on the iPad), and I have the options set to allow the report to then be produced as .pdf, Exel, Word, or Text. None of those buttons work. If I hold the button for a few seconds, it give a option to "Open image in new tab", but it opens a tab to ...\images\$$application.adobe.pdf.png.a5mage which does nothing.

It is strange that you are having problems even with the html reports.

[kingcarol]

Re: Filtering reports based on dates on Ipad is not working

Well, it turns out that it is not a date thing. The problem is that I was calling an Xbasic function to check some things about dates in the database before opening the report, so back before the feature for the JavaScript Actions Editor was available, I had to call the action of a hidden button to open the report. See code below. The code still works fine on a PC, AND used to work fine on my customer's Surface device. My Xbasic code for calling the click event of button is below, but now mobile devices are not liking it. SO, I created a javascript action to open the report and now my Xbasic function calls the javascript action instead of a button, and it started working to open the html report!

OLD XBASIC CODE that no longer works on touch device:

dim js as c = ""
js = js + "$('{dialog.componentname}.V.R1.BUTTON_28').click();"
js = js + "var ele = $('{dialog.componentname}.V.R1.BUTTON_28');"
[I]functionName[/I] = js

NEW XBASIC CODE that DOES work:

[I]functionName[/I] = "{dialog.object}.runAction('[I]javascriptActionName[/I]');"