Liveware Publishing Support Forum

My application is calling reports using the viewer executable. After installing v11, I^m getting errors on those reports being called with RI_QUERY="?" to display the selection rule dialog box. The error is:____Cannot display dialog box. Check available memory.____If it^s relevant, the command being used to call the report is:__ cmd.exe /c "rrwrun.exe g: empZJXDHP 1 /og: emp rZZJXDH.dbf /wy /h /b /d. /i."____Help!____Dennis

One additional piece of info. The error is happening on my Windows 2000 desktop, but _not_ on my WinXP Home laptop.____>My application is calling reports using the viewer __>executable. After installing v11, I^m getting errors on __>those reports being called with RI_QUERY="?" to display the __>selection rule dialog box. The error is: __>__>Cannot display dialog box. Check available memory. __>__>If it^s relevant, the command being used to call the report __>is: __> cmd.exe /c "rrwrun.exe g: empZJXDHP 1 __>/og: emp rZZJXDH.dbf /wy /h /b /d. /i." __>__>Help! __>__>Dennis __

Darn! I was so hopeful that this upgrade would survive in the first round, but with these comments, I can^t possibly start upgrading clients without knowing that they will bomb when they first start using the upgrade.____Can somebody from Liveware please confirm either that there is a problem (the one here is critical) or there is not a problem but rather this is a syntax error. I was within an hour of upgrading people when I read this message.____Thanks, Kathleen, or whoever is going to answer this.____Jeff

I just did a test report here and set all of the prompt dialogs to a ? and each of the dialogs displayed fine. But since you are the third person to report this problem, I just need to dig more to reproduce it. And once I do, we will have a fix ASAP.____Kathleen__R&R Support

When I test on a an XP machine, it works fine.____But when I test on a 2000 machine, I get the error for both the SQL and the Xbase runtimes. The designer on 2000 has no problem with the query/filter dialog.____I will have the development folks look at this one.______Kathleen__R&R Support

Well it is not because it is 2000. Just tested on a second 2000 laptop and it was fine. And both machines use the same 1024x668 screen resolution so it is even more difficult to find what is the source of the problem..____So I am still investigating..____Kathleen

Kathleen,____Any progress on this one?____Thanks,__Dennis

I don^t have V11 runtime but do have V10 that gets a Winspool error (on some computers) and it sounds pretty similar. I^m wondering if the RI_PRINTER could be set to "D" instead of "?" and it might help ?

The problem happens when RI_QUERY is set to "?", not RI_PRINTER.____Dennis

We are still struggling to find the source of the problem. The strange thing is that it happens only at runtime and we have found that changing the default printer can make it go away. And it is only some reports. It seems that reports that have a parameteRR prompt as well as a query prompt can display the query on bad machines. We added a calendar control to the query in V11 and something in that code seems to be causing the problem.__Several of our developers are experiencing some hair loss over this one but will hopefully be victorious in the near future.______Kathleen__R&R Support__