Senin, 11 Januari 2016

Re: [MS_AccessPros] Checklist with a twist 1 - different input types

 

Crystal,


I don't understand what you are saying about Option A & B. Or, maybe I didn't explain it properly.


Let's say you have tasks numbered 1-20. Let's say task 6 is a forking step. If the answer is Y, then do 7 & 8; if N, then do 9 & 10.


blChecklistTaskOptions would have the following records:
TaskID, OptionA, OptionB
6,7,9
6,8,10

When initially populating tblChecklistData (ChecklistID, TaskID, Done), I would add tasks 1-6, 11-20. Then, after a choice is made for task 6, I would add either 7&8 or 9&10.

Adam

---In MS_Access_Professionals@yahoogroups.com, <strive4peace2008@...> wrote :

Hi Adam,

I use a table corresponding to the Access data type number (DatTypN) for stuff like this:

a_DataTypes
DatTypNDatTypSDatTypeSDatTypN_
1YNBoolean4
2BytByte4
3IntInteger4
4LngLong4
5CurCurrency5
6SglSingle7
7DblDouble7
8DateDate/Time8
9BinBinary
10TextShortText10
11OleOLE Binary BMP
12MemoLongText10
15GuidGuid
16BigIntBig Integer
17BinVarBinary Variable
18TxtFixFixed Text10
19oNumNumeric ODBC
20oDecDecimal ODBC
21oFloatFloat ODBC
22oTimeTime ODBC
23oDatTimDateTime ODBC
101AttAttachment
102mvBytByte MV
103mvIntInteger MV
104mvLngLong Integer MV
105mvSglSingle MV
106mvDblDouble MV
107mvGuidGUID MV
108mvDecDecimal MV
109mvTxtText MV
a_DataTypes

DatTypN_ is for rolling up data types

I would rethink OptionA and OptionB.  The RecordSource should report all answers in a calculated text field (that can't be edited) so they line up.  Then, an edit button that will turn on the appropriate control (checkbox, combo, textbox, etc) to fill out with the value with validation for the proper data type.  Generally, I store:
- yn (can also use Long to store this)
- long integer
- currency
- text

warm regards,
crystal

~ have an awesome day ~


On 1/11/2016 11:37 AM, runuphillracing@... [MS_Access_Professionals] wrote:

This is the first of two checklist questions, which I'll post in separate topics.


With this topic, the checklist responses may can have different types of input: date, Y-N, short text. Also, some of the responses may determine the next steps. I'm looking for feedback on my approach, and/or advice on a better one.


Assume the standard checklist vertical structure: tblChecklistMaster (key ChecklistID), tblChecklistTasks (TaskID), tblChecklistData (ChecklistID, TaskID). When a new project is added to tblChecklistMaster, the tasks are copied from tblChecklistTasks to tblChecklistData.


For different input types, my idea is to add a field to tblChecklistTasks, let's call it InputType, long integer; e.g., 1=date, 2=Y-N, 3=text). On tblChecklistData, make the field Done as short text. On the subform (based on tblChecklistData, main form based on tblChecklistMaster), have code that will do different things, when the Done text box is clicked, depending on InputType:

  1. Enter today's date
  2. Toggle between Y-N
  3. Allow the input of text.

For next steps, my idea is to add another table, tblChecklistTaskOptions, with 3 fields: TaskID (link to tblChecklistTasks), OptionA, OptionB. TaskID would be the originating ID of the Task that determines the next set of tasks. OptionA would be the TaskIDs if Y is chosen, OptionB if N is chosen. There can be multiple entries of next steps for each originating TaskID. Initially, I wouldn't populate tblChecklistData with any task that is in OptionAorB. When a choice is made on the originating task, I would then populate tblChecklistData with the next step tasks from OptionAorB. If the choice were changed, I could delete one set of next steps and replace it with another. tblChecklistTasks has the field SortOrder, so the next step tasks would go in the right place when the form is refreshed.


I know how to do the coding of this. I'm looking to see if my approach/idea is off base.


Thanks

Adam


__._,_.___

Posted by: runuphillracing@yahoo.com
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (3)

.

__,_._,___

Tidak ada komentar:

Poskan Komentar