>>>Rob, in addition to the solutions the others have suggested, check the list of VFP reserved words and try NOT to use these in tables. Recently people have written about problems with fields named DESC, NUMBER and now DATE and TIME. All of these words are used internally by VFP, so it has trouble figuring out which meaning is the right one.
>>>
>>>Keep this in mind for future tables, and you'll have fewer problems.
>>>
>>>HTH
>>>Barbara
>>
>>Hi Barbara and thanks for answering...
>>I inherited the problems with this program. My job is to makedo with what
>>I have and not redo. I do not have to explain the problems one gets when they have to modify an inherited program. As a rule, I try and stay away from reverse words, verbs, syntax and whatever.. :)
>
>This was just generic advice, Rob. We've ALL had old code with bad field and table names.
>
>More specifically about your problem, in an earlier message you mentioned using ??? 3 (three) question marks. That tells VFP you are sending a printer code, not text to be printed. I don't know how your printer handles this, but if you ARE using 3 ??? try again with ?? (2) question marks.
>
>HTH
>Barbara

Hi Barbara...
I am sending flds with values to the printer using vfp50. I had tried
?? and that did not work. I have to use ??? for this to work.
Here is a sample for HP III...
??? chr(27)+'(10U'+chr(27)+'(s0p16.66h8.5v0s0b0T'
??? chr(27)+'*p0x0Y'
??? mytable.name
??? mytable.address
I stuff everything in the printer's memory and print everything at one time.
This code works, but if you have another idea, please let us know.
Thanks..rob