Prev: Wrong message with cascading deletes (bug?)
Next: Access runtime and activation
From: raif on 26 May 2010 13:31


"Tony Toews [MVP]" <ttoews(a)telusplanet.net>, iletide sunu yazdi
news:k03jv5hpkk0d22ri8209jmn6j9469dvrc7(a)4ax.com...
> "David C. Holley" <David.C.Holley> wrote:
>
>>At what point in time is MS going to alter Forms so that controls only tab
>>between controls on the same page? Building a wizard where you want the
>>user
>>to be able to TAB, just like the rest of every application out there,
>>would
>>be so much easier.
>
> I don't quite understand the problem here. Using the tab key skips
> from page to page?
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
> For a convenient utility to keep your users FEs and other files
> updated see http://www.autofeupdater.com/
> Granite Fleet Manager http://www.granitefleet.com/

From: David W. Fenton on 26 May 2010 17:16
"David C. Holley" <David.C.Holley> wrote in
news:#EzImoF$KHA.3840(a)TK2MSFTNGP02.phx.gbl:

> But you could design the layout and shake down the functionality
> by placing the controls in regions of a very enlarged form, thus
> avoiding the headache of the overlap. If you go with a naming
> schema such as tb1_, tb2_ you can then you code to move the
> controls into and out of position.

I'd rather not code that. I certainly use naming conventions for my
tab pages (pge is my prefix for it), but don't see the point of
coding, as I don't know when the code should run. There's also the
new issue in A2002/2003 with runtime changes getting saved when they
oughtn't, which is a real thorn in my side in apps where I set
background colors and so forth at runtime.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
First  |  Prev  | 
Pages: 1 2 3 4 5 6
Prev: Wrong message with cascading deletes (bug?)
Next: Access runtime and activation