W
WGHayes
Hi,
We are currently in the process of trialling various Resize/Rescale
controls/code and have come across a number of issues with this approach.
We have an MS Access 2000 application designed at 800x600 screen resolution
and are wanting to use a resize control to allow forms to resize to the
available screen resolution, or, operate on any form size between 800x600
and the maximum screen resolution.
Controls/code trialled include:-
- Code from 'Access 2000 Developers Handbook'
- A2K Resize Control MDE (apparently developed from code in handbook but
seems to work better)
- Shrinker Stretcher
- FMS Resize Control
Our approach has been that we DO NOT want to use Scaling, only resizing, and
we only want this to work on specific controls. It seems from the controls
above that the only control/code that will allow us to selectively choose
controls to 'resize' is the 'Access 2000 Developers Handbook' and A2K Resize
control.
The 'primary' controls on our forms that we want to resize are:-
- TAB Controls
- Sub Forms
NOTE:- Specifically, but allowing SUB forms to expand users are able to see
more data across a 'datasheet' view. This is our primary objective. It
also happens that these sub-forms may be on TAB controls therefore both the
TAB and SUB FORM must be able to be resized.
What we are finding is that with the 'Access 2000 Developers Handbook' code
and A2K Resize control is that where there are TAB controls on the form
(which are set to resize) then when a form is resized DOWN to less than 20%
of it's original size then these TAB controls move over existing controls
(which is correct) but do not then move back to there correct position when
the form is then resized UP (i.e. the TOP position of the TAB control is NOT
as it was designed - it has moved). Whilst this problem can be avoided by
setting MIN width and height properties this is not ideally how we would
want to use the control (i.e. impacts on form TILING).
Questions we have:-
- Is anyone else using the 'Access 2000 Developers Handbook' code, OR, the
A2K Resize control that have found similar issues? Where these issues
resolved and/or what work around was used?
- What other Resize controls are available for Access 2000 that I have not
already mentioned?
Any comments regarding our approach to 'resizing' are also welcome.
Thanks,
Wayne.
We are currently in the process of trialling various Resize/Rescale
controls/code and have come across a number of issues with this approach.
We have an MS Access 2000 application designed at 800x600 screen resolution
and are wanting to use a resize control to allow forms to resize to the
available screen resolution, or, operate on any form size between 800x600
and the maximum screen resolution.
Controls/code trialled include:-
- Code from 'Access 2000 Developers Handbook'
- A2K Resize Control MDE (apparently developed from code in handbook but
seems to work better)
- Shrinker Stretcher
- FMS Resize Control
Our approach has been that we DO NOT want to use Scaling, only resizing, and
we only want this to work on specific controls. It seems from the controls
above that the only control/code that will allow us to selectively choose
controls to 'resize' is the 'Access 2000 Developers Handbook' and A2K Resize
control.
The 'primary' controls on our forms that we want to resize are:-
- TAB Controls
- Sub Forms
NOTE:- Specifically, but allowing SUB forms to expand users are able to see
more data across a 'datasheet' view. This is our primary objective. It
also happens that these sub-forms may be on TAB controls therefore both the
TAB and SUB FORM must be able to be resized.
What we are finding is that with the 'Access 2000 Developers Handbook' code
and A2K Resize control is that where there are TAB controls on the form
(which are set to resize) then when a form is resized DOWN to less than 20%
of it's original size then these TAB controls move over existing controls
(which is correct) but do not then move back to there correct position when
the form is then resized UP (i.e. the TOP position of the TAB control is NOT
as it was designed - it has moved). Whilst this problem can be avoided by
setting MIN width and height properties this is not ideally how we would
want to use the control (i.e. impacts on form TILING).
Questions we have:-
- Is anyone else using the 'Access 2000 Developers Handbook' code, OR, the
A2K Resize control that have found similar issues? Where these issues
resolved and/or what work around was used?
- What other Resize controls are available for Access 2000 that I have not
already mentioned?
Any comments regarding our approach to 'resizing' are also welcome.
Thanks,
Wayne.