Liveware Publishing Support Forum

Hi,____A client of mine is changing the user^s platform from Windows 2000 to Windows XP. Although this seems like a dumb idea to me, I^ve got to live with it.____The version of R&R runtime that is currently shipped to their Windows 2000 desktop is 9.0.9(Xbase).____My question is - am I likely to...

I^m using R&R Report Writer, Xbase Edition Version 9.0 with the Version 9.0.009 Update. The backend database is Visual FoxPro 6.0____A user has reported the following problem:____When printing customer^s addresses on letters the application seems to be ^remembering the customer^s old address^.__...

Yes, oddly the original posting (and your your reply) is no longer available on this forum (I^ve tried searching the archives as well).____The problem I have is with printer names in excess of 80 chars.____The applications in question use RI_WPTR to send the printer name.__To be fully Windows 2000 c...

Before I spend some money on version 10 of R&R Xbase can anyone tell me if the bug regarding long printer names that was raised against version 9.0.9 has been fixed?____Regards____John Cawley__Schlumberger

Kathleen,____Thanks for your speedy reply. ____We tried increasing RI_WPTR on Windows 2000 and this appears to work up to 81 chars - anything greater fails as you suggest.____We also tried removing the function that uses RI_WPTR and constrain the user to printing to the default printer.____However, ...

Hi,____I have a problem with Windows 2000 and R&R runtime that I wonder if anyone has a solution for:____Windows 2000 supports printer names up to 220 characters but the RI_WPTR parameter has a maximum width of 40.____As a result of the limitation my application only prints to those printers tha...

Latest update on this:____RRWRUN.EXE crashes when you supply a control table with a path greater than 81 characters (84 if you include the file extension).____Still no response from tech support.

It seems that rrwrun.exe crashes with command lines greater than 172 characters (and possibly a lot less). Not so much of a problem if the database is on a local drive but if it^s located on a server...

No, it isn^t fixed in the latest release. It looks like the buffer used to store the command line is insufficient or it^s getting walked over by some other part of the run-time. In a nutshell our application which accesses a database held on a server path cannot print any reports (which is a pity ^c...

Well, I found the problem - if you pass in a command line of greater than 240 characters rrwrun.exe crashes.____Has this been fixed in the latest version?____Regards,____John Cawley__SchlumbergerSema__