473,396 Members | 1,749 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,396 software developers and data experts.

How to control the Access Title Bar

Hello

I'm using Access2000, SplitDB, ALL MenuBars are Off. The
AccessTitleBar(BlueBar) displays at the top with its (Min/Max/[X])
Controlbox.

I have a MainMenuForm (Modal-On), that Calls a ReportMenuForm
(Modal-On) that lets me select a REPORT. If I set the ReportMenuForm
(Popup-On) and I select a REPORT, the AccessTitleBar becomes disable (a
good thing), however the REPORT displays underneath the ReportMenuForm
(a bad thing). If I set the ReportMenuForm (Popup-Off) and I select a
REPORT, the REPORT displays OnTop (a good thing). However, a new
problem emerges. If the user maximizes the REPORT, the REPORTS TitleBar
disappears under the AccessTitleBar confusing the user. The user will
then press the Close[X] button, and the whole application shuts down (a
bad thing). I found unconventional code on the MS Web site, and was
able to shut off the [X] button of the AccessTitleBar, but the Min/Max
stays on.
Access2000 does not support the PopUp option in REPORTS. This would be
my solution. This MUST be a common frustration to many developers!

I need to display the REPORT OnTop, without the AccessTitleBar
concerns!

How do I disable the AccessTitleBar, or its (Min/Max[X]) Controlbox ?

Jul 6 '06 #1
15 3518
go to
http://home.bendbroadband.com/conrad...osebutton.html
and scroll down to #10. there is complete code there to "turn off/on" the
Minimize, Maximize, and X buttons all at the same time, on the Access title
bar. it works like a charm!

hth
<Ap******@gmail.comwrote in message
news:11**********************@v61g2000cwv.googlegr oups.com...
Hello

I'm using Access2000, SplitDB, ALL MenuBars are Off. The
AccessTitleBar(BlueBar) displays at the top with its (Min/Max/[X])
Controlbox.

I have a MainMenuForm (Modal-On), that Calls a ReportMenuForm
(Modal-On) that lets me select a REPORT. If I set the ReportMenuForm
(Popup-On) and I select a REPORT, the AccessTitleBar becomes disable (a
good thing), however the REPORT displays underneath the ReportMenuForm
(a bad thing). If I set the ReportMenuForm (Popup-Off) and I select a
REPORT, the REPORT displays OnTop (a good thing). However, a new
problem emerges. If the user maximizes the REPORT, the REPORTS TitleBar
disappears under the AccessTitleBar confusing the user. The user will
then press the Close[X] button, and the whole application shuts down (a
bad thing). I found unconventional code on the MS Web site, and was
able to shut off the [X] button of the AccessTitleBar, but the Min/Max
stays on.
Access2000 does not support the PopUp option in REPORTS. This would be
my solution. This MUST be a common frustration to many developers!

I need to display the REPORT OnTop, without the AccessTitleBar
concerns!

How do I disable the AccessTitleBar, or its (Min/Max[X]) Controlbox ?

Jul 6 '06 #2
ThankYou Tina

The Code for AccessTitleBar (Min/Max/[X]) controlbox worked Perfectly!

Unfortunately, my problem did not resolve. If a Report gets Maximized
by the user, the REPORTS (Min/Max/[X]) controlbox disappears instead of
displaying at the top of the page over the AccessTitleBar. It may be
going underneath, but not sure. Anybody have
any ideas ?

Greg

tina wrote:
go to
http://home.bendbroadband.com/conrad...osebutton.html
and scroll down to #10. there is complete code there to "turn off/on" the
Minimize, Maximize, and X buttons all at the same time, on the Access title
bar. it works like a charm!

hth
<Ap******@gmail.comwrote in message
news:11**********************@v61g2000cwv.googlegr oups.com...
Hello

I'm using Access2000, SplitDB, ALL MenuBars are Off. The
AccessTitleBar(BlueBar) displays at the top with its (Min/Max/[X])
Controlbox.

I have a MainMenuForm (Modal-On), that Calls a ReportMenuForm
(Modal-On) that lets me select a REPORT. If I set the ReportMenuForm
(Popup-On) and I select a REPORT, the AccessTitleBar becomes disable (a
good thing), however the REPORT displays underneath the ReportMenuForm
(a bad thing). If I set the ReportMenuForm (Popup-Off) and I select a
REPORT, the REPORT displays OnTop (a good thing). However, a new
problem emerges. If the user maximizes the REPORT, the REPORTS TitleBar
disappears under the AccessTitleBar confusing the user. The user will
then press the Close[X] button, and the whole application shuts down (a
bad thing). I found unconventional code on the MS Web site, and was
able to shut off the [X] button of the AccessTitleBar, but the Min/Max
stays on.
Access2000 does not support the PopUp option in REPORTS. This would be
my solution. This MUST be a common frustration to many developers!

I need to display the REPORT OnTop, without the AccessTitleBar
concerns!

How do I disable the AccessTitleBar, or its (Min/Max[X]) Controlbox ?
Jul 6 '06 #3
try putting a custom toolbar or menu bar on your report, or a shortcut
(right-click pop-up) menu, to allow the user to Print and Close.

hth
<Ap******@gmail.comwrote in message
news:11**********************@b68g2000cwa.googlegr oups.com...
ThankYou Tina

The Code for AccessTitleBar (Min/Max/[X]) controlbox worked Perfectly!

Unfortunately, my problem did not resolve. If a Report gets Maximized
by the user, the REPORTS (Min/Max/[X]) controlbox disappears instead of
displaying at the top of the page over the AccessTitleBar. It may be
going underneath, but not sure. Anybody have
any ideas ?

Greg

tina wrote:
go to
http://home.bendbroadband.com/conrad...osebutton.html
and scroll down to #10. there is complete code there to "turn off/on"
the
Minimize, Maximize, and X buttons all at the same time, on the Access
title
bar. it works like a charm!

hth
<Ap******@gmail.comwrote in message
news:11**********************@v61g2000cwv.googlegr oups.com...
Hello
>
I'm using Access2000, SplitDB, ALL MenuBars are Off. The
AccessTitleBar(BlueBar) displays at the top with its (Min/Max/[X])
Controlbox.
>
I have a MainMenuForm (Modal-On), that Calls a ReportMenuForm
(Modal-On) that lets me select a REPORT. If I set the ReportMenuForm
(Popup-On) and I select a REPORT, the AccessTitleBar becomes disable
(a
good thing), however the REPORT displays underneath the ReportMenuForm
(a bad thing). If I set the ReportMenuForm (Popup-Off) and I select a
REPORT, the REPORT displays OnTop (a good thing). However, a new
problem emerges. If the user maximizes the REPORT, the REPORTS
TitleBar
disappears under the AccessTitleBar confusing the user. The user will
then press the Close[X] button, and the whole application shuts down
(a
bad thing). I found unconventional code on the MS Web site, and was
able to shut off the [X] button of the AccessTitleBar, but the Min/Max
stays on.
Access2000 does not support the PopUp option in REPORTS. This would
be
my solution. This MUST be a common frustration to many developers!
>
I need to display the REPORT OnTop, without the AccessTitleBar
concerns!
>
How do I disable the AccessTitleBar, or its (Min/Max[X]) Controlbox ?
>

Jul 6 '06 #4
Thankyou for the quick response, and the interesting suggestions.
I'll give it a try!

Greg
tina wrote:
try putting a custom toolbar or menu bar on your report, or a shortcut
(right-click pop-up) menu, to allow the user to Print and Close.

hth
<Ap******@gmail.comwrote in message
news:11**********************@b68g2000cwa.googlegr oups.com...
ThankYou Tina

The Code for AccessTitleBar (Min/Max/[X]) controlbox worked Perfectly!

Unfortunately, my problem did not resolve. If a Report gets Maximized
by the user, the REPORTS (Min/Max/[X]) controlbox disappears instead of
displaying at the top of the page over the AccessTitleBar. It may be
going underneath, but not sure. Anybody have
any ideas ?

Greg

tina wrote:
go to
>
http://home.bendbroadband.com/conrad...osebutton.html
and scroll down to #10. there is complete code there to "turn off/on"
the
Minimize, Maximize, and X buttons all at the same time, on the Access
title
bar. it works like a charm!
>
hth
>
>
<Ap******@gmail.comwrote in message
news:11**********************@v61g2000cwv.googlegr oups.com...
Hello

I'm using Access2000, SplitDB, ALL MenuBars are Off. The
AccessTitleBar(BlueBar) displays at the top with its (Min/Max/[X])
Controlbox.

I have a MainMenuForm (Modal-On), that Calls a ReportMenuForm
(Modal-On) that lets me select a REPORT. If I set the ReportMenuForm
(Popup-On) and I select a REPORT, the AccessTitleBar becomes disable
(a
good thing), however the REPORT displays underneath the ReportMenuForm
(a bad thing). If I set the ReportMenuForm (Popup-Off) and I select a
REPORT, the REPORT displays OnTop (a good thing). However, a new
problem emerges. If the user maximizes the REPORT, the REPORTS
TitleBar
disappears under the AccessTitleBar confusing the user. The user will
then press the Close[X] button, and the whole application shuts down
(a
bad thing). I found unconventional code on the MS Web site, and was
able to shut off the [X] button of the AccessTitleBar, but the Min/Max
stays on.
Access2000 does not support the PopUp option in REPORTS. This would
be
my solution. This MUST be a common frustration to many developers!

I need to display the REPORT OnTop, without the AccessTitleBar
concerns!

How do I disable the AccessTitleBar, or its (Min/Max[X]) Controlbox ?
Jul 6 '06 #5
you're welcome, good luck! :)
<Ap******@gmail.comwrote in message
news:11**********************@m79g2000cwm.googlegr oups.com...
Thankyou for the quick response, and the interesting suggestions.
I'll give it a try!

Greg
tina wrote:
try putting a custom toolbar or menu bar on your report, or a shortcut
(right-click pop-up) menu, to allow the user to Print and Close.

hth
<Ap******@gmail.comwrote in message
news:11**********************@b68g2000cwa.googlegr oups.com...
ThankYou Tina
>
The Code for AccessTitleBar (Min/Max/[X]) controlbox worked Perfectly!
>
Unfortunately, my problem did not resolve. If a Report gets Maximized
by the user, the REPORTS (Min/Max/[X]) controlbox disappears instead
of
displaying at the top of the page over the AccessTitleBar. It may be
going underneath, but not sure. Anybody have
any ideas ?
>
Greg
>
>
>
>
>
tina wrote:
go to
http://home.bendbroadband.com/conrad...osebutton.html
and scroll down to #10. there is complete code there to "turn
off/on"
the
Minimize, Maximize, and X buttons all at the same time, on the
Access
title
bar. it works like a charm!

hth


<Ap******@gmail.comwrote in message
news:11**********************@v61g2000cwv.googlegr oups.com...
Hello
>
I'm using Access2000, SplitDB, ALL MenuBars are Off. The
AccessTitleBar(BlueBar) displays at the top with its (Min/Max/[X])
Controlbox.
>
I have a MainMenuForm (Modal-On), that Calls a ReportMenuForm
(Modal-On) that lets me select a REPORT. If I set the
ReportMenuForm
(Popup-On) and I select a REPORT, the AccessTitleBar becomes
disable
(a
good thing), however the REPORT displays underneath the
ReportMenuForm
(a bad thing). If I set the ReportMenuForm (Popup-Off) and I
select a
REPORT, the REPORT displays OnTop (a good thing). However, a new
problem emerges. If the user maximizes the REPORT, the REPORTS
TitleBar
disappears under the AccessTitleBar confusing the user. The user
will
then press the Close[X] button, and the whole application shuts
down
(a
bad thing). I found unconventional code on the MS Web site, and
was
able to shut off the [X] button of the AccessTitleBar, but the
Min/Max
stays on.
Access2000 does not support the PopUp option in REPORTS. This
would
be
my solution. This MUST be a common frustration to many
developers!
>
I need to display the REPORT OnTop, without the AccessTitleBar
concerns!
>
How do I disable the AccessTitleBar, or its (Min/Max[X])
Controlbox ?
>
>

Jul 7 '06 #6
Hello Tina - Hope you're still in HelpMode!
Access2000, split DB

Took your advice on nearly all your suggestions. Reworked my code and
things are as I want them:

Startup has all menus OFF, I display the Access TitleBar with
Controlbox OFF, a ReportMenuForm (Modal) is brought up, I have buttons
for each report. Each report uses the same Custom1 MenuBar
(Print,Close) that displays at the top of the screen just under the
TitleBar. This was set in the Reports properties. In code, on Report
Open, I have DoCmd.Maximize. All this stuff works great. However, the
Reports "Horizontal Scroll Bar" disappears under the windows "Start"
bar (ie bars name?) at the bottom of the screen. The user needs this
because the reports are landscape.

Any suggestions ?

Thanks Again
Greg

tina wrote:
you're welcome, good luck! :)
<Ap******@gmail.comwrote in message
news:11**********************@m79g2000cwm.googlegr oups.com...
Thankyou for the quick response, and the interesting suggestions.
I'll give it a try!

Greg
tina wrote:
try putting a custom toolbar or menu bar on your report, or a shortcut
(right-click pop-up) menu, to allow the user to Print and Close.
>
hth
>
>
<Ap******@gmail.comwrote in message
news:11**********************@b68g2000cwa.googlegr oups.com...
ThankYou Tina

The Code for AccessTitleBar (Min/Max/[X]) controlbox worked Perfectly!

Unfortunately, my problem did not resolve. If a Report gets Maximized
by the user, the REPORTS (Min/Max/[X]) controlbox disappears instead
of
displaying at the top of the page over the AccessTitleBar. It may be
going underneath, but not sure. Anybody have
any ideas ?

Greg





tina wrote:
go to
>
>
http://home.bendbroadband.com/conrad...osebutton.html
and scroll down to #10. there is complete code there to "turn
off/on"
the
Minimize, Maximize, and X buttons all at the same time, on the
Access
title
bar. it works like a charm!
>
hth
>
>
<Ap******@gmail.comwrote in message
news:11**********************@v61g2000cwv.googlegr oups.com...
Hello

I'm using Access2000, SplitDB, ALL MenuBars are Off. The
AccessTitleBar(BlueBar) displays at the top with its (Min/Max/[X])
Controlbox.

I have a MainMenuForm (Modal-On), that Calls a ReportMenuForm
(Modal-On) that lets me select a REPORT. If I set the
ReportMenuForm
(Popup-On) and I select a REPORT, the AccessTitleBar becomes
disable
(a
good thing), however the REPORT displays underneath the
ReportMenuForm
(a bad thing). If I set the ReportMenuForm (Popup-Off) and I
select a
REPORT, the REPORT displays OnTop (a good thing). However, a new
problem emerges. If the user maximizes the REPORT, the REPORTS
TitleBar
disappears under the AccessTitleBar confusing the user. The user
will
then press the Close[X] button, and the whole application shuts
down
(a
bad thing). I found unconventional code on the MS Web site, and
was
able to shut off the [X] button of the AccessTitleBar, but the
Min/Max
stays on.
Access2000 does not support the PopUp option in REPORTS. This
would
be
my solution. This MUST be a common frustration to many
developers!

I need to display the REPORT OnTop, without the AccessTitleBar
concerns!

How do I disable the AccessTitleBar, or its (Min/Max[X])
Controlbox ?
Jul 7 '06 #7
Forgot to mention, this is how I open the Report:

DoCmd.OpenReport strReport, acViewPreview, , strWhere

Thanks
Greg

Ap******@gmail.com wrote:
Hello Tina - Hope you're still in HelpMode!
Access2000, split DB

Took your advice on nearly all your suggestions. Reworked my code and
things are as I want them:

Startup has all menus OFF, I display the Access TitleBar with
Controlbox OFF, a ReportMenuForm (Modal) is brought up, I have buttons
for each report. Each report uses the same Custom1 MenuBar
(Print,Close) that displays at the top of the screen just under the
TitleBar. This was set in the Reports properties. In code, on Report
Open, I have DoCmd.Maximize. All this stuff works great. However, the
Reports "Horizontal Scroll Bar" disappears under the windows "Start"
bar (ie bars name?) at the bottom of the screen. The user needs this
because the reports are landscape.

Any suggestions ?

Thanks Again
Greg

tina wrote:
you're welcome, good luck! :)
<Ap******@gmail.comwrote in message
news:11**********************@m79g2000cwm.googlegr oups.com...
Thankyou for the quick response, and the interesting suggestions.
I'll give it a try!
>
Greg
>
>
tina wrote:
try putting a custom toolbar or menu bar on your report, or a shortcut
(right-click pop-up) menu, to allow the user to Print and Close.

hth


<Ap******@gmail.comwrote in message
news:11**********************@b68g2000cwa.googlegr oups.com...
ThankYou Tina
>
The Code for AccessTitleBar (Min/Max/[X]) controlbox worked Perfectly!
>
Unfortunately, my problem did not resolve. If a Report gets Maximized
by the user, the REPORTS (Min/Max/[X]) controlbox disappears instead
of
displaying at the top of the page over the AccessTitleBar. It may be
going underneath, but not sure. Anybody have
any ideas ?
>
Greg
>
>
>
>
>
tina wrote:
go to
http://home.bendbroadband.com/conrad...osebutton.html
and scroll down to #10. there is complete code there to "turn
off/on"
the
Minimize, Maximize, and X buttons all at the same time, on the
Access
title
bar. it works like a charm!

hth


<Ap******@gmail.comwrote in message
news:11**********************@v61g2000cwv.googlegr oups.com...
Hello
>
I'm using Access2000, SplitDB, ALL MenuBars are Off. The
AccessTitleBar(BlueBar) displays at the top with its (Min/Max/[X])
Controlbox.
>
I have a MainMenuForm (Modal-On), that Calls a ReportMenuForm
(Modal-On) that lets me select a REPORT. If I set the
ReportMenuForm
(Popup-On) and I select a REPORT, the AccessTitleBar becomes
disable
(a
good thing), however the REPORT displays underneath the
ReportMenuForm
(a bad thing). If I set the ReportMenuForm (Popup-Off) and I
select a
REPORT, the REPORT displays OnTop (a good thing). However, a new
problem emerges. If the user maximizes the REPORT, the REPORTS
TitleBar
disappears under the AccessTitleBar confusing the user. The user
will
then press the Close[X] button, and the whole application shuts
down
(a
bad thing). I found unconventional code on the MS Web site, and
was
able to shut off the [X] button of the AccessTitleBar, but the
Min/Max
stays on.
Access2000 does not support the PopUp option in REPORTS. This
would
be
my solution. This MUST be a common frustration to many
developers!
>
I need to display the REPORT OnTop, without the AccessTitleBar
concerns!
>
How do I disable the AccessTitleBar, or its (Min/Max[X])
Controlbox ?
>
>
>
Jul 7 '06 #8
This problem seems to be the result of the user resizing the
ApplicationWindow. When
the Window is expanded, it causes the botton scroll bar to descend
below the "Start Bar"
at the bottom. I'm now working on figuring out how to stop Re-sizing of
the AppWindow!

Greg

Ap******@gmail.com wrote:
Forgot to mention, this is how I open the Report:

DoCmd.OpenReport strReport, acViewPreview, , strWhere

Thanks
Greg

Ap******@gmail.com wrote:
Hello Tina - Hope you're still in HelpMode!
Access2000, split DB

Took your advice on nearly all your suggestions. Reworked my code and
things are as I want them:

Startup has all menus OFF, I display the Access TitleBar with
Controlbox OFF, a ReportMenuForm (Modal) is brought up, I have buttons
for each report. Each report uses the same Custom1 MenuBar
(Print,Close) that displays at the top of the screen just under the
TitleBar. This was set in the Reports properties. In code, on Report
Open, I have DoCmd.Maximize. All this stuff works great. However, the
Reports "Horizontal Scroll Bar" disappears under the windows "Start"
bar (ie bars name?) at the bottom of the screen. The user needs this
because the reports are landscape.

Any suggestions ?

Thanks Again
Greg

tina wrote:
you're welcome, good luck! :)
>
>
<Ap******@gmail.comwrote in message
news:11**********************@m79g2000cwm.googlegr oups.com...
Thankyou for the quick response, and the interesting suggestions.
I'll give it a try!

Greg


tina wrote:
try putting a custom toolbar or menu bar on your report, or a shortcut
(right-click pop-up) menu, to allow the user to Print and Close.
>
hth
>
>
<Ap******@gmail.comwrote in message
news:11**********************@b68g2000cwa.googlegr oups.com...
ThankYou Tina

The Code for AccessTitleBar (Min/Max/[X]) controlbox worked Perfectly!

Unfortunately, my problem did not resolve. If a Report gets Maximized
by the user, the REPORTS (Min/Max/[X]) controlbox disappears instead
of
displaying at the top of the page over the AccessTitleBar. It may be
going underneath, but not sure. Anybody have
any ideas ?

Greg





tina wrote:
go to
>
>
http://home.bendbroadband.com/conrad...osebutton.html
and scroll down to #10. there is complete code there to "turn
off/on"
the
Minimize, Maximize, and X buttons all at the same time, on the
Access
title
bar. it works like a charm!
>
hth
>
>
<Ap******@gmail.comwrote in message
news:11**********************@v61g2000cwv.googlegr oups.com...
Hello

I'm using Access2000, SplitDB, ALL MenuBars are Off. The
AccessTitleBar(BlueBar) displays at the top with its (Min/Max/[X])
Controlbox.

I have a MainMenuForm (Modal-On), that Calls a ReportMenuForm
(Modal-On) that lets me select a REPORT. If I set the
ReportMenuForm
(Popup-On) and I select a REPORT, the AccessTitleBar becomes
disable
(a
good thing), however the REPORT displays underneath the
ReportMenuForm
(a bad thing). If I set the ReportMenuForm (Popup-Off) and I
select a
REPORT, the REPORT displays OnTop (a good thing). However, a new
problem emerges. If the user maximizes the REPORT, the REPORTS
TitleBar
disappears under the AccessTitleBar confusing the user. The user
will
then press the Close[X] button, and the whole application shuts
down
(a
bad thing). I found unconventional code on the MS Web site, and
was
able to shut off the [X] button of the AccessTitleBar, but the
Min/Max
stays on.
Access2000 does not support the PopUp option in REPORTS. This
would
be
my solution. This MUST be a common frustration to many
developers!

I need to display the REPORT OnTop, without the AccessTitleBar
concerns!

How do I disable the AccessTitleBar, or its (Min/Max[X])
Controlbox ?

Jul 7 '06 #9

<Ap******@gmail.comwrote in message
news:11**********************@p79g2000cwp.googlegr oups.com...
This problem seems to be the result of the user resizing the
ApplicationWindow. When
the Window is expanded, it causes the botton scroll bar to descend
below the "Start Bar"
at the bottom. I'm now working on figuring out how to stop Re-sizing of
the AppWindow!
That's not the "Windows way," which is to let the user have control over
his/her own desktop, and is guaranteed to irritate some users*. Better to
let the users know that they will lose report scrolling if they resize the
window, and let it be the user's choice.

* some of us have been known to discard apps where the developer decided
he knew better than we did how our screen ought to be arranged. <G>

Larry Linson
Microsoft Access MVP
Jul 7 '06 #10
"Larry Linson" <bo*****@localhost.notwrote in
news:WCzrg.70$Th7.51@trnddc05:
><Ap******@gmail.comwrote in message
news:11**********************@p79g2000cwp.googlegr oups.com...
>This problem seems to be the result of the user resizing the
ApplicationWindow. When
the Window is expanded, it causes the botton scroll bar to
descend below the "Start Bar"
at the bottom. I'm now working on figuring out how to stop
Re-sizing of the AppWindow!

That's not the "Windows way," which is to let the user have
control over his/her own desktop, and is guaranteed to irritate
some users*. Better to let the users know that they will lose
report scrolling if they resize the window, and let it be the
user's choice.
Well, I've never understood why my users accidentally end up running
their apps in non-full-screen mode. All my apps are designed to run
full-screen at the clients' default resolutions. When they run them
at less than full-screen, they lose access to features.

And my experience is that they don't do it on purpose. They
accidentally click on something and end up non-full screen.

So, to me, preventing them from running in anything but full-screen
mode seems like not a terribly bad thing.
* some of us have been known to discard apps where the developer
decided
he knew better than we did how our screen ought to be arranged.
<G>
I can see that, but an Access app that's custom-designed ought to
have this kind of thing negotiated with the users. In that case, I
can't see it as a problem to override their ability to run in
anything but full-screen mode.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jul 7 '06 #11
"David W. Fenton" wrote
I can see that, but an Access app
that's custom-designed ought to
have this kind of thing negotiated
with the users. In that case, I can't
see it as a problem to override their
ability to run in anything but
full-screen mode.
First, I have never had the opportunity to "negotiate with the users" but
(officially) only with a client's representative, who often neither knows
nor finds out what the majority of the users want. It's difficult in cases
where there are tens or hundreds of users, even if you know who the user
audience is.

Second, of course, if your application is not a "bespoke application," you
have to _guess_ what most users want (and my experience, unofficially, with
users is they do want to have control over their own desktop).

Third, since it is so simple for users to handle their own desktop, who am I
to force them to "do it my way," Frank Sinatra?

Fourth, if the users choose to size the Forms/Reports so that something has
to be scrolled, why should I not let them do exactly that?

Larry
Jul 8 '06 #12
"Larry Linson" <bo*****@localhost.notwrote in
news:9RHrg.1279$pB.936@trnddc06:
"David W. Fenton" wrote
I can see that, but an Access app
that's custom-designed ought to
have this kind of thing negotiated
with the users. In that case, I can't
see it as a problem to override their
ability to run in anything but
full-screen mode.

First, I have never had the opportunity to "negotiate with the
users" but (officially) only with a client's representative, . . .
Well, that's actually what I meant by "users."
. . . who often neither knows
nor finds out what the majority of the users want. . . .
I've never had the misfortune of lacking contact with at least some
representative end users.
. . . It's difficult in cases
where there are tens or hundreds of users, even if you know who
the user audience is.
Er, how many Access apps have hundreds of users?
Second, of course, if your application is not a "bespoke
application," you have to _guess_ what most users want (and my
experience, unofficially, with users is they do want to have
control over their own desktop).
Um, I don't think there is such a thing as a "shrink-wrap" Access
application.
Third, since it is so simple for users to handle their own
desktop, who am I to force them to "do it my way," Frank Sinatra?
In my experience, users who end up not running at full-screen
resolution in apps that are hampered by that (which would be any
Access app designed to run full-screen) don't know how to get back
to full-screen.
Fourth, if the users choose to size the Forms/Reports so that
something has to be scrolled, why should I not let them do exactly
that?
Perhaps a compromise is to always start the app full-screen and let
them do what they want from then on. The problem I've seen is that
users get into non-full-screen mode and then that is retained each
time they restart their Access app. Setting the app to full-screen
when it starts up would help out those users while not terribly
inconveniencing the user who wants to run with only part of the
screen used by the app.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jul 8 '06 #13
Perhaps a compromise is to always start the app full-screen and let
them do what they want from then on.
Hear! Hear!

Greg

David W. Fenton wrote:
"Larry Linson" <bo*****@localhost.notwrote in
news:9RHrg.1279$pB.936@trnddc06:
"David W. Fenton" wrote
I can see that, but an Access app
that's custom-designed ought to
have this kind of thing negotiated
with the users. In that case, I can't
see it as a problem to override their
ability to run in anything but
full-screen mode.
First, I have never had the opportunity to "negotiate with the
users" but (officially) only with a client's representative, . . .

Well, that's actually what I meant by "users."
. . . who often neither knows
nor finds out what the majority of the users want. . . .

I've never had the misfortune of lacking contact with at least some
representative end users.
. . . It's difficult in cases
where there are tens or hundreds of users, even if you know who
the user audience is.

Er, how many Access apps have hundreds of users?
Second, of course, if your application is not a "bespoke
application," you have to _guess_ what most users want (and my
experience, unofficially, with users is they do want to have
control over their own desktop).

Um, I don't think there is such a thing as a "shrink-wrap" Access
application.
Third, since it is so simple for users to handle their own
desktop, who am I to force them to "do it my way," Frank Sinatra?

In my experience, users who end up not running at full-screen
resolution in apps that are hampered by that (which would be any
Access app designed to run full-screen) don't know how to get back
to full-screen.
Fourth, if the users choose to size the Forms/Reports so that
something has to be scrolled, why should I not let them do exactly
that?

Perhaps a compromise is to always start the app full-screen and let
them do what they want from then on. The problem I've seen is that
users get into non-full-screen mode and then that is retained each
time they restart their Access app. Setting the app to full-screen
when it starts up would help out those users while not terribly
inconveniencing the user who wants to run with only part of the
screen used by the app.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jul 8 '06 #14
"David W. Fenton" <XX*******@dfenton.com.invalidwrote
>. . . It's difficult in cases
where there are tens or hundreds of users, even if you know who
the user audience is.

Er, how many Access apps have hundreds of users?
At least one, on which I did subcontract work off and on over a five-year
period in the 1990s -- when it began, the customer contract administrator
said, we now have about 35 users, but won't ever have more than 50. But,
when I last worked on it in 2000, it had between 175 and 200 users. It was a
corporate real estate database, an Access 2.0 client to an Informix server
DB. (Yes, they never wanted to pay to upgrade the client app to a newer
version, preferring to spend their development budget on enhancing features
and functions.)

On occasion, the prime contractor would have contact with a real, live user,
but not the subcontractors.
>Second, of course, if your application is not a "bespoke
application," you have to _guess_ what most users want (and my
experience, unofficially, with users is they do want to have
control over their own desktop).

Um, I don't think there is such a thing as a "shrink-wrap" Access
application.
We get questions in the newsgroup about packaging those, fairly frequently.
They aren't general-use things like Word or Excel, but niche applications
(like corporate real-estate... this negotiated a special license to use and
modify an Access-Jet commercial app) but "shrink-wrap" is a likely
stretching it (no pun intended).
>Third, since it is so simple for users to handle their own
desktop, who am I to force them to "do it my way," Frank Sinatra?

In my experience, users who end up not running at full-screen
resolution in apps that are hampered by that (which would be any
Access app designed to run full-screen) don't know how to get back
to full-screen.
The users never seemed to have a problem in databases I've worked on, but
I've been lucky to work, mostly, with apps for users in companies where full
Office Pro was on every (pertinent) desktop. So they were not completely new
to Access/Office. Not necessarily "power users" but not "raw newbies,"
either.

Larry

Jul 9 '06 #15
"Larry Linson" <bo*****@localhost.notwrote in
news:UW0sg.8561$Wh7.826@trnddc07:
"David W. Fenton" <XX*******@dfenton.com.invalidwrote
>In my experience, users who end up not running at full-screen
resolution in apps that are hampered by that (which would be any
Access app designed to run full-screen) don't know how to get
back to full-screen.

The users never seemed to have a problem in databases I've worked
on, but I've been lucky to work, mostly, with apps for users in
companies where full Office Pro was on every (pertinent) desktop.
So they were not completely new to Access/Office. Not necessarily
"power users" but not "raw newbies," either.
I've never ever created or distributed a runtime app, so all of my
users are using full Access in Office Pro. They don't understand the
basics of handling windows because nobody has ever given them any
training, so they get in situations that they don't understand and
just live with them.

At least, that's my experience with the 100s of users I've worked
with in the 12 years I've been a computer consultant. YMMV.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jul 10 '06 #16

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

6
by: Franco Lombardo | last post by:
Hi all, I'm running DB2 8.1.5 on Windows 2000 professional SP4. When I try to start Control Center, I see the splash screen for a while, then it closes and nothing else happens. It happens...
11
by: trinitypete | last post by:
Hi all, I have a user control that uses control literal to build a heading with a link, and a div containing links below. As the link heading is hit, I want to change the style of the div,...
6
by: martin | last post by:
Hi, I am a web page and a web user control. My web user control is placed in my web page using the following directive <%@ Register TagPrefix="uc1" TagName="Header"...
6
by: William Parker | last post by:
I have a web control I made called header.ascx. It has its own properties and methods I defined. But I cannot figure out how to access this control from my code behind page. I can create the...
1
by: Green | last post by:
Hi, I have a question concerning how to manipulate the properties in the user control, and there is an interesting article about this from Microsoft:...
2
by: Nathan Sokalski | last post by:
I would like to change the <title></title> of a page from a user control. I have been unable to find any property in VB that allows me to do this. The only thing I have been able to find that might...
3
by: ivanpais | last post by:
Hi, I have a Web User Control, Lets say "Foo.ascx", that contains a button "btnFoo". I have a Master Page "Bar.master", that has a label "lblBar". This label is exposed by a public property...
3
by: tshad | last post by:
I am trying to put together a user control (.ascx). Can you access an outside control from it? My control: login2.ascx ****************************************************************...
0
by: Paul | last post by:
Hi all, I have a simple custom control with a label and a text box. The text control's value is persisting when I do a post back, so the view state is working, but I cannot access the value in...
4
by: archana | last post by:
Hi all, i am having one user control. what i want is to add javascript which will gets called on button click of user control. but user control is not working if i add javascript in user...
0
by: Charles Arthur | last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
0
by: ryjfgjl | last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
0
by: emmanuelkatto | last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud. Please let me know. Thanks! Emmanuel
0
BarryA
by: BarryA | last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
1
by: nemocccc | last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
0
by: Hystou | last post by:
There are some requirements for setting up RAID: 1. The motherboard and BIOS support RAID configuration. 2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
0
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers,...
0
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
0
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.