Tom,
It seem like you are having lots of problems with reports. I am going to
guess that the example you posted was not cut and pasted from your code. 
The code you posted likely will not run as you are missing a "." (dot) in
front of vardate; also, date is a reserved word; the command should be
PRINT reportname WHERE your_date_column = .vardate OPTION PRINTER
As it always true in cases such as yours, it helps to post the exact code
that you are running, that way we can maybe find another reason why your
code is not working.
As I mentioned in a previous post, I would suggest you TRACE your code to
make sure your variables are being initialized, not only with the correct
type but with the correct value as well. You need to make sure that the
printer is properly configured and available at the workstation in question.
 
Javier,
 
Javier Valencia, PE
913-829-0888 Office
913-915-3137 Cell
913-649-2904 Fax
 <mailto:[email protected]> [email protected]
 
  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of TOM HART
Sent: Sunday, September 12, 2010 4:08 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - 9.0 compiled printer problem
 
I have posted this before but still can't understand why this locks up.  On
a form I enter some data and have a print button with the following eep:
 
prnsetup printername
print reportname where date = vardate option printer
 
This has worked fine on 7.6 compiled at 3 different location (2 running XP,
1 running Windows 7).  It will print fine from the main  computer, but will
lock up right when the printing window opens(it opens, is dim, and freezes)
when run on any of the networked computers.  Same is true if I use option
screen  I have also found other places in my program that prints other
reports and they also freeze if a where clause is present.  Other reports,
that are either variable reports or print from a temp table(in both cases
there is no where clause) print fine.  I just cannot seem to understand why
it will run on the computer hosting the program but will lock up on all
other network computers.
 
Tom Hart

Reply via email to