![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
VFP has a wonky way to set printer orientation: sys(1037). This is intended for end-user use. I have to use keyboard to use it programmatically. The flash on the screen is a kludge and a bit bothersome. My boss recently commented on the latter. Since I am using set printer on and ? -style reporting, this is what I have to use. How can I get rid of it? |
#3
| |||
| |||
|
|
Hi Gene, VFP has a wonky way to set printer orientation: sys(1037). This is intended for end-user use. I have to use keyboard to use it programmatically. The flash on the screen is a kludge and a bit bothersome. My boss recently commented on the latter. Since I am using set printer on and ? -style reporting, this is what I have to ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ use. How can I get rid of it? Did you try my idea from oct.13 in your thread "VFP9: Alternative to sys(1037)" about using the additional parameters of sys(1037) |
#4
| |||
| |||
|
|
Bernhard Sander <fuchs (AT) no (DOT) spam> wrote: Hi Gene, VFP has a wonky way to set printer orientation: sys(1037). This is intended for end-user use. I have to use keyboard to use it programmatically. The flash on the screen is a kludge and a bit bothersome. My boss recently commented on the latter. Since I am using set printer on and ? -style reporting, this is what I have to ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ use. How can I get rid of it? Did you try my idea from oct.13 in your thread "VFP9: Alternative to sys(1037)" about using the additional parameters of sys(1037) No, because it does not apply. From the VFP 9 docs on sys(1037): "All three report-related SYS(1037,<N>) variants require access to a cursor or open table with the same format as a report (.frx) or label (.lbx) definition file. The report must be selected as a cursor or opened as a table before you call the function, and Visual FoxPro requires the report table to be opened exclusively. Otherwise, an error occurs when you call the function. For more information about the structure of report and label tables, see Table Structures of Table Files (.dbc, .frx, .lbx, .mnx, .pjx, .scx, .vcx)." Please note that I am not using the Report Writer. That is the significance of the above caret-captioned text. Sincerely, Gene Wirchenko Computerese Irregular Verb Conjugation: I have preferences. You have biases. He/She has prejudices. |
#5
| |||
| |||
|
|
Why would you NOT use the Foxpro report writer?? I am confused here... |
#6
| |||
| |||
|
|
"tony_becky_mikey_verizon_news" <tony_becky_mikey (AT) verizon (DOT) net> wrote: Why would you NOT use the Foxpro report writer?? I am confused here... Control. Some of my reports are rather complex, and my boss can give arbitrarily complex changes. I find straight code much easier to read for this, and I have tools for searching my code, which aids considerably in maintaining it. [snip] Sincerely, Gene Wirchenko Computerese Irregular Verb Conjugation: I have preferences. You have biases. He/She has prejudices. |
#7
| |||
| |||
|
|
So you are saying you don't have control of the layout in a report form? This sounds kind fishy here.. Is it a matter of you don't like using the more MODERN tools available? Please tell me you are atleast using forms in VFP... |
|
If I had to maintain someone's code that was not using report forms, I would not be maintaining that version of code for long... When you move up to the more involved development environments, see Oracle and SQL Server, you will find it hard NOT to use a report writer (Crystal Reports, Oracle Report Writer, Cognos...). |
|
But then again, some folks will always be using Foxpro... |
#8
| |||
| |||
|
|
VFP has a wonky way to set printer orientation: sys(1037). This is intended for end-user use. I have to use keyboard to use it programmatically. The flash on the screen is a kludge and a bit bothersome. My boss recently commented on the latter. Since I am using set printer on and ? -style reporting, this is what I have to use. How can I get rid of it? If there is a way to have it "show up" off-screen, that would be a purely-VFP solution. That would be acceptable, though granted, it is still somewhat of a kludge. Is there such a way? Another way *might* be to jump into the Windows API. I really do not want to recode all my reports, so I would want to be able to just insert the OS calls at the appropriate point. HOW? The big question is how do I refer to a VFP printjob? Can I combine the two usages? Presumably, if I can set orientation this way, I could do other things as well, but just getting printer orientation working would meet the current and likely needs. Has anyone worked with the printing part of the Windows API? Pointers are also and especially welcome. Sincerely, Gene Wirchenko Computerese Irregular Verb Conjugation: I have preferences. You have biases. He/She has prejudices. |
#9
| |||
| |||
|
|
A Screen Flash might be indicative of the talk setting - whats the value of 'set talk' right prior to calling the sys(1037) function ? |
#10
| |||
| |||
|
|
Hi Gene, VFP has a wonky way to set printer orientation: sys(1037). This is intended for end-user use. I have to use keyboard to use it programmatically. The flash on the screen is a kludge and a bit bothersome. My boss recently commented on the latter. Since I am using set printer on and ? -style reporting, this is what I have to ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ use. How can I get rid of it? Did you try my idea from oct.13 in your thread "VFP9: Alternative to sys(1037)" about using the additional parameters of sys(1037) No, because it does not apply. From the VFP 9 docs on sys(1037): "All three report-related SYS(1037,<N>) variants require access to a cursor or open table with the same format as a report (.frx) or label (.lbx) definition file. The report must be selected as a cursor or opened as a table before you call the function, and Visual FoxPro requires the report table to be opened exclusively. Otherwise, an error occurs when you call the function. For more information about the structure of report and label tables, see Table Structures of Table Files (.dbc, .frx, .lbx, .mnx, .pjx, .scx, .vcx)." Please note that I am not using the Report Writer. That is the significance of the above caret-captioned text. I know, that you don't use the Report Writer (neither do I). |
![]() |
| Thread Tools | |
| Display Modes | |
| |