StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I know of no exact duplication of the 2007 functionality in 2003. There are multiple components for resolution independence (resizing the controls on a form based on the users monitor resolution) and for resizing with the form resize event (such as <a href="http://www.fmsinc.com/products/components/ControlTour/resize.htm" rel="nofollow noreferrer">http://www.fmsinc.com/products/components/ControlTour/resize.htm</a>). None that I'm aware of quite replicate the 2007 experience, but a similar question (and code to handle it) can be found here: <a href="http://www.experts-exchange.com/Microsoft/Development/MS_Access/Q_23662850.html" rel="nofollow noreferrer">http://www.experts-exchange.com/Microsoft/Development/MS_Access/Q_23662850.html</a></p> <p>Personally, I just handled the resize event myself. The easiest way is to do so is to create the form in the minimum size you wish to support, and then record the base positions and widths (either in a table or as form scoped constants). From there you can resize using: </p> <pre><code>resizeRatio = currentFormWidth / baseFormWidth control.left = baseLeft * resizeRatio control.width = baseWidth * resizeRatio </code></pre> <p>The advantage to doing this yourself is that over time you evolve it, with things such as keeping the labels on the left side the same width but expanding the fields to the right (this is done by not resizing the labels at all, and subtracting the end of the labels area off from the width of the form before applying the position and width changes, such as):</p> <pre><code>resizeRatio = (currentFormWidth - labelsAreaWidth) / (baseFormWidth - labelsAreaWidth) control.left = (baseLeft - labelsAreaWidth) * resizeRatio + labelsAreaWidth control.width = baseWidth * resizeRatio </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload