设计困境 - 连续形式和按钮。 [英] Design Dilemma - ContinuousForms and Buttons.
问题描述
在我的数据库中，我统一处理记录的记录，
在一个包含New / Edit / Del按钮的表单中。因为我一次只处理一个记录，所以我可以轻松管理我的按钮
操作。用户在ViewOnlyMode中输入系统，如果按下EditButton
，字段变为黄色，Me.AllowEdits变为true，并且用户编辑了
。接下来是一个Save / Undo / Quit按钮，显然是明显的
，并且用户返回到ViewMode。
我还在系统中内置了安全性打开或关闭按钮
基于用户权限。
现在，一些未来的表格需要构建为连续表格，并且将会
理想地在屏幕上排列多个记录。为了保持连续性和感觉。我的系统，我需要使用按钮。这个
提出了一个问题，因为按钮通常会管理个人
记录，连续记录概念变成了一个噩梦。
用我的传统管理MultipleRecords按钮。
管理连续表格的任何设计建议，与我原来的设计按钮概念逻辑上符合
将是非常好的
赞赏。此外，任何设计样本或示例链接也将是有用的。这个项目已完成50％。
谢谢你
格雷格
将您的按钮放在Form Footer部分。
即使使用连续表格，也有当前记录。如果您选择
显示记录选择器，则它指向当前记录。您的按钮将根据当前记录中的值启用/禁用
。
-
Allen Browne - 微软MVP。西澳大利亚珀斯
访问用户提示 - http：// allenbrowne .com / tips.html
回复群组，而不是mvps dot org的allenbrowne。
< Ap ***** *@gmail.com在留言中写道
新闻：11 ********************** @ a3g2000cwd.googlegro ups.com ...
在我的数据库中，我统一处理记录的记录，
在一个包含New / Edit / Del的表单中纽扣。因为我一次只处理一个记录，所以我可以轻松管理我的按钮
操作。用户在ViewOnlyMode中输入系统，如果按下EditButton
，字段变为黄色，Me.AllowEdits变为true，并且用户编辑了
。接下来是一个Save / Undo / Quit按钮，显然是明显的
，并且用户返回到ViewMode。
我还在系统中内置了安全性打开或关闭按钮
基于用户权限。
现在，一些未来的表格需要构建为连续表格，并且将会
理想地在屏幕上排列多个记录。为了保持连续性和感觉。我的系统，我需要使用按钮。这个
提出了一个问题，因为按钮通常会管理个人
记录，连续记录概念变成了一个噩梦。
用我的传统管理MultipleRecords按钮。
管理连续表格的任何设计建议，与我原来的设计按钮概念逻辑上符合
将是非常好的
赞赏。此外，任何设计样本或示例链接也将是有用的。这个项目已完成50％。
谢谢你
Greg
Ap ****** @ gmail.com 写道：
在我的数据库中，我在一个包含New / Edit / Del按钮的单个表单中统一处理Record by Record
的记录。因为
我一次只处理一个记录，我可以轻松管理我的按钮
操作。用户在ViewOnlyMode中输入系统，如果按下EditButton
，字段变为黄色，Me.AllowEdits变为true，
并且用户编辑。接下来是一个Save / Undo / Quit按钮，
显而易见，并且用户返回到ViewMode。
我还在系统中内置了安全性打开或关闭按钮
基于用户权限。
现在，一些未来的表格需要构建为连续表格，并且将会
理想地在屏幕上排列多个记录。为了使b
保持连续性和感觉。我的系统，我需要使用
按钮。这就产生了一个问题，因为按钮通常会管理个人记录，连续记录概念变成了用我的传统按钮管理MultipleRecords的梦魇。
>
管理连续表格的任何设计建议，与我的原始设计按钮概念在逻辑上都符合
将非常值得赞赏。此外，任何设计样本或示例链接也将是有用的。该项目已完成50％。
根据您的其他表单的工作方式，我会将连续表单只读为
，每条记录都有一个按钮。按下将打开一个
对话框表单，允许编辑一条记录。那个表单上可以有你的
保存/撤消/退出按钮。
-
Rick Brandt，Microsoft Access MVP
电子邮件（视情况而定）至...
在Hunter dot com的RBrandt
Ap ****** @ gmail.com 写道：
>在我的数据库中，我在一个记录的基础上统一处理记录，
在一个包含New / Edit / Del按钮的表单中。因为我一次只处理一个记录，所以我可以轻松管理我的按钮操作。用户在ViewOnlyMode中进入系统，如果按下EditButton
，字段变为黄色，Me.AllowEdits变为true，并且用户编辑。接下来是一个Save / Undo / Quit按钮，显然是明显的，并且用户返回到ViewMode。
我还在系统中内置了安全性并打开或关闭按钮基于用户权限。
现在，需要将一些未来的表单构建为连续表单，并且希望在屏幕上排列多个记录。为了保持连续性和感觉。我的系统，我需要使用按钮。这会产生一个问题，因为按钮通常会管理个人记录，连续记录概念成为用我的传统按钮管理MultipleRecords的噩梦。
任何设计管理连续表格的建议，与我的原始设计按钮概念逻辑相符，将非常感激。此外，任何设计示例或示例链接也将有所帮助。该项目已完成50％。
我更喜欢把记录操作按钮放在
页脚部分。
为了强调将对哪个记录进行操作，我使用
锁定和禁用文本框来填充详细信息
部分。然后使用条件格式来设置
文本框的BackColor。
-
Marsh
In my database, I uniformly handle records on a Record by Record basis,
in a single form that contains New/Edit/Del buttons. Because I''m
dealing with records one at a time, I can easily manage my button
operations. The user enters the system in ViewOnlyMode, if EditButton
is pressed, the fields turn yellow, and Me.AllowEdits becomes true, and
the user edits. This is followed by a Save/Undo/Quit button, that does
the obvious, and the user is returned to ViewMode.
I also have security built into the system and turn buttons On or OFF
based on user rights.
Now, a few future forms need to be built as Continuous Forms, and will
desirably arrange multiple records on the screen. In order to maintain
the continuity and "feel" of my system, I need to use buttons. This
presents a problem because the buttons typically manage Individual
Records, and the continuous record concept becomes a nightmare to
manage MultipleRecords with my traditional buttons.
Any design suggestions for managing Continuous Forms, that would fit in
logically with my original design button concept would be greatly
appreciated. Also, any design sample or example links would also be
helpful. This project is 50% complete.
ThankYou
Greg
Place your buttons in the Form Footer section.
Even with a Continuous Form, there is a current record. If you choose to
show the record selector, it points to the current record. Your buttons will
be enabled/disabled or whatever based on the values in the current record.
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
<Ap******@gmail.comwrote in message
news:11**********************@a3g2000cwd.googlegro ups.com...In my database, I uniformly handle records on a Record by Record basis,
in a single form that contains New/Edit/Del buttons. Because I''m
dealing with records one at a time, I can easily manage my button
operations. The user enters the system in ViewOnlyMode, if EditButton
is pressed, the fields turn yellow, and Me.AllowEdits becomes true, and
the user edits. This is followed by a Save/Undo/Quit button, that does
the obvious, and the user is returned to ViewMode.
I also have security built into the system and turn buttons On or OFF
based on user rights.
Now, a few future forms need to be built as Continuous Forms, and will
desirably arrange multiple records on the screen. In order to maintain
the continuity and "feel" of my system, I need to use buttons. This
presents a problem because the buttons typically manage Individual
Records, and the continuous record concept becomes a nightmare to
manage MultipleRecords with my traditional buttons.
Any design suggestions for managing Continuous Forms, that would fit in
logically with my original design button concept would be greatly
appreciated. Also, any design sample or example links would also be
helpful. This project is 50% complete.
ThankYou
Greg
Ap******@gmail.com wrote:In my database, I uniformly handle records on a Record by Record
basis, in a single form that contains New/Edit/Del buttons. Because
I''m dealing with records one at a time, I can easily manage my button
operations. The user enters the system in ViewOnlyMode, if EditButton
is pressed, the fields turn yellow, and Me.AllowEdits becomes true,
and the user edits. This is followed by a Save/Undo/Quit button,
that does the obvious, and the user is returned to ViewMode.
I also have security built into the system and turn buttons On or OFF
based on user rights.
Now, a few future forms need to be built as Continuous Forms, and will
desirably arrange multiple records on the screen. In order to
maintain the continuity and "feel" of my system, I need to use
buttons. This presents a problem because the buttons typically
manage Individual Records, and the continuous record concept becomes
a nightmare to manage MultipleRecords with my traditional buttons.
Any design suggestions for managing Continuous Forms, that would fit
in logically with my original design button concept would be greatly
appreciated. Also, any design sample or example links would also be
helpful. This project is 50% complete.Based on how your other forms work I would make the continuous form read
only and have an [Edit] button per record. Pressing that would open a
dialog form that allowed editing that one record. That form could have your
Save/Undo/Quit buttons on it.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Ap******@gmail.com wrote:
>In my database, I uniformly handle records on a Record by Record basis,
in a single form that contains New/Edit/Del buttons. Because I''m
dealing with records one at a time, I can easily manage my button
operations. The user enters the system in ViewOnlyMode, if EditButton
is pressed, the fields turn yellow, and Me.AllowEdits becomes true, and
the user edits. This is followed by a Save/Undo/Quit button, that does
the obvious, and the user is returned to ViewMode.
I also have security built into the system and turn buttons On or OFF
based on user rights.
Now, a few future forms need to be built as Continuous Forms, and will
desirably arrange multiple records on the screen. In order to maintain
the continuity and "feel" of my system, I need to use buttons. This
presents a problem because the buttons typically manage Individual
Records, and the continuous record concept becomes a nightmare to
manage MultipleRecords with my traditional buttons.
Any design suggestions for managing Continuous Forms, that would fit in
logically with my original design button concept would be greatly
appreciated. Also, any design sample or example links would also be
helpful. This project is 50% complete.
I prefer to put the record operation buttons in the form
footer section.
To emphasize which record will be operated on, I use a
locked and disabled text box sized to fill the detail
section. Conditional Formatting is then used to set the
text box''s BackColor.
--
Marsh
这篇关于设计困境 - 连续形式和按钮。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
