Is this a known issue? I don't know how to correct
the problem.
Ron White
It's that last Report link that is the "button". It's enabled after a
field has been selected.
HTH
Thanks Tony
Ron
There is probably a older version screen file in the DBIFORMS file.
SELECT DBIFORMS = "DBI]"
(If you haven't named any files that start with DBI..... then you can
delete any items found, otherwise:
SELECT DBIFORMS =
"DBIPROP*]""DBIFORMS*]""DBIFILES*]""DBISELECT*]""DBIMENUS*]"
DELETE DBIFORMS
Regards,
David
Thanks
[comments, since we're here...]
For end-user forms, I think it's best for all of us to design forms which
are about 800 pixels wide, and eliminate the need for users to have to
horizontal scroll for data. On a 1024 pixel monitor this leaves about 150
pixels for the left side menu, a few for a scrollbar and borders, a small
aesthetic margin on the right. Then in the forms designer we can make full
use of the form width up to the red line. Some say the horizontal real
estate is as liberating as vertical space when compared to 80x24 screens.
To some extent I'll agree but in a heads-down app you want people to grab
and move the mouse as little as possible, and if there are issues when a
user horizontal-scrolls, then it's best to avoid it.
T
I completely agree with your assessment. As a matter of fact this is
exactly what I tell users in training classes. They must standardized
on a screen width. The most common screen resolution today is 1024 x
768. If you maximize IE, you will probably get about 840 pixels worth
of workable real estate. But be careful, as not all monitors/graphics
cards are made equal and if your user has selected a large windows
font, you may not get 840 pixel width
Just my 25 cents (inflation),
Rick
Ron