Search results for query: *

Stacy, I have had similar problems on Win2k & WinXP machines. Make sure that in the disk drive properties, policies tab, the write caching is disabled. You might also issue a FLUSH command after the GATHER.

Not knowing how your screens are layed out, you could put a button with a validation command: MODIFY REPORT ? , which would let the user select which report to modify. Then they could use the FPW report writer to do the modifications, and eliminate CR all together.

Check out this low cost solution at http://www.pdf995.com. Some of the features I've found useful include: combing output from multiple print jobs, emailing output, and being able to change options (.ini files) with low-level file functions from inside of FPW on the fly. Wayne

Try using two button objects, instead of one. Make the variables m.op1 and m.op2, both with initial values of 0. Then, in your case starement, you can trap for m.op1=1 or m.op2=1. Besure to reset the button value back to 0 in each case. This method also allows you to enable/disable each...

I use this as the report field expression: LEFT(cardnumber,4)+REPL('*',LEN(ALLTRIM(cardnumber))-8)+RIGHT(ALLTRIM(cardnumber),4) This prints the first 4 and last 4 digits of the credit card number, regardless of the type of card. You can change it to fit your needs.

I'm using a utility from Abri Technologies, called FPW Printer Select, which handles this all through code, and stores the printer information you need in a small dbf. I've been using it for several years and it works on Win9x, Win2k, and XP. Here's a link to it...

I had similar problems with Win ME. Disable "write-behind caching" and that should solve the problem. Issuing a FLUSH didn't always work.