Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Set preview magnification programmatically 1
- Thread starter tiborheld
- Start date
-
1
- #2
ChrisRChamberlain
Programmer
tiborheld
Not sure it's possible.
Normal technique would be to set the values up on the preview toolbar and then make the toolbar read only in FOXUSER.dbf.
That works initially but the preview magnification immediately reverts to 100%.
It's also significant that the preview magnification combobox is the only control that cannot be added to or removed from the toolbar.
I personally favour forms that "read" and display single page reports. There can be scaled simply by dragging to size or the magnification value can be preselected or selected from a combobox.
This might be an option for you, if no one else has an answer.
Chris
Not sure it's possible.
Normal technique would be to set the values up on the preview toolbar and then make the toolbar read only in FOXUSER.dbf.
That works initially but the preview magnification immediately reverts to 100%.
It's also significant that the preview magnification combobox is the only control that cannot be added to or removed from the toolbar.
I personally favour forms that "read" and display single page reports. There can be scaled simply by dragging to size or the magnification value can be preselected or selected from a combobox.
This might be an option for you, if no one else has an answer.
Chris
It seems this worth a FAQ. Asked quite often...
Vlad Grynchyshyn
vgryn@softserve.lviv.ua
The professional level of programmer could be determined by level of stupidity of his/her bugs
Vlad Grynchyshyn
vgryn@softserve.lviv.ua
The professional level of programmer could be determined by level of stupidity of his/her bugs
ChrisRChamberlain
Programmer
Vlad
Thanks for the encouragment to write the FAQ.
Two problems - legally I can't publish the code, only outline the methodology which may not be much use to anyone.
Secondly, any developer needing to create such a class needs to have an in-depth knowledge of report tables, before starting.
A beginning would be to study John Koziol's excellent article, Demystifying Visual FoxPro Report Files, at
Chris
Thanks for the encouragment to write the FAQ.
Two problems - legally I can't publish the code, only outline the methodology which may not be much use to anyone.
Secondly, any developer needing to create such a class needs to have an in-depth knowledge of report tables, before starting.
A beginning would be to study John Koziol's excellent article, Demystifying Visual FoxPro Report Files, at
Chris
No code. Just a technique of creating an entry in foxuser.dbf, finding it in browse window and what to change to make it read-only. Than best approach to include that DBF into EXE and distribute.
What is required to be edited here in the report files?
Vlad Grynchyshyn
vgryn@softserve.lviv.ua
The professional level of programmer could be determined by level of stupidity of his/her bugs
What is required to be edited here in the report files?
Vlad Grynchyshyn
vgryn@softserve.lviv.ua
The professional level of programmer could be determined by level of stupidity of his/her bugs
ChrisRChamberlain
Programmer
Vlad
Apologies - I misunderstood you.
I was referring to forms that "read" and display single page reports.
Can and will do a FAQ on locating objects in FOXUSER.dbf.
Chris
Apologies - I misunderstood you.
I was referring to forms that "read" and display single page reports.
Can and will do a FAQ on locating objects in FOXUSER.dbf.
Chris
- Status
Similar threads
