Form Transition Question

[Guest]

What is the best way to handle a transition from one form to another?

I’m creating a database to track the application for various types of
permits. What will happen is when an application first comes in, the common
data (name/address of applicant) will be stored in one table and the record
will be assigned a permit number. Based on evaluation of the application,
the processing can take various paths, for example, an exemption, approval or
denial (with supporting documentation). This data I plan to store in separate
respective tables (table for exemption, approval, denial). All will be tied
together by the permit number field. After the initial form is completed
with the common data and the user clicks on a button to open the Exemption
form, for example, what is the best way to pre-populate the Permit number
into the Exemption form? If the field name is [PerNum] and the initial data
entry form is [frmApp], would the following code work in the PerNum field on
the Exemption form:

=[Forms]![frmApp]![PerNum]

Should I add an if is null code to the above so the PerNum doesn’t get
accidentally overwritten upon opening the Exemption form?

Is there a better way? Any suggestions appreciated.

 

[Jeff Boyce]

Jade

Recommendations will depend on your data situation. Are you saying that
"Exemptions", "Approvals", and "Denials" each have their own unique
attributes (thus justifying separate tables, related 1-to-1 to the main
permit table)? Or do they have nearly all fields/attributes in common, and
you've elected separate tables to "categorize" the action taken?

If the former, another approach would be to use a main form (for the permit
info) and a subform. The source for the subform would be dynamically set
by, say, the choice of the action on the main form. Thus, the same subform
control on the main form could be "fed" by one of three different
(sub)forms.

Or have I misunderstood your situation?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Guest]

I feel that Exemptions, Approvals and Denials would justify separate tables.
Each table would have between 20 to 50 unique, separate fields. Yes, I am
trying to categorize the action taken. Wouldn't including all the fields in
one flat table become cumbersome? The above tables would be related to the
main table in a 1 to 1 relationship.

Jade

Jade

Recommendations will depend on your data situation. Are you saying that
"Exemptions", "Approvals", and "Denials" each have their own unique
attributes (thus justifying separate tables, related 1-to-1 to the main
permit table)? Or do they have nearly all fields/attributes in common, and
you've elected separate tables to "categorize" the action taken?

If the former, another approach would be to use a main form (for the permit
info) and a subform. The source for the subform would be dynamically set
by, say, the choice of the action on the main form. Thus, the same subform
control on the main form could be "fed" by one of three different
(sub)forms.

Or have I misunderstood your situation?

Regards

Jeff Boyce
Microsoft Office/Access MVP

What is the best way to handle a transition from one form to another?

I'm creating a database to track the application for various types of
permits. What will happen is when an application first comes in, the
common
data (name/address of applicant) will be stored in one table and the
record
will be assigned a permit number. Based on evaluation of the application,
the processing can take various paths, for example, an exemption, approval
or
denial (with supporting documentation). This data I plan to store in
separate
respective tables (table for exemption, approval, denial). All will be
tied
together by the permit number field. After the initial form is completed
with the common data and the user clicks on a button to open the Exemption
form, for example, what is the best way to pre-populate the Permit number
into the Exemption form? If the field name is [PerNum] and the initial
data
entry form is [frmApp], would the following code work in the PerNum field
on
the Exemption form:

=[Forms]![frmApp]![PerNum]

Should I add an if is null code to the above so the PerNum doesn't get
accidentally overwritten upon opening the Exemption form?

Is there a better way? Any suggestions appreciated.

 

[Jeff Boyce]

Since you hadn't mentioned these facts before, I had to ask.

If your data is unique to the categories, then yes, it makes sense to have
separate tables.

Regards

Jeff Boyce
Microsoft Office/Access MVP

I feel that Exemptions, Approvals and Denials would justify separate
tables.
Each table would have between 20 to 50 unique, separate fields. Yes, I am
trying to categorize the action taken. Wouldn't including all the fields
in
one flat table become cumbersome? The above tables would be related to
the
main table in a 1 to 1 relationship.

Jade

Jade

Recommendations will depend on your data situation. Are you saying that
"Exemptions", "Approvals", and "Denials" each have their own unique
attributes (thus justifying separate tables, related 1-to-1 to the main
permit table)? Or do they have nearly all fields/attributes in common,
and
you've elected separate tables to "categorize" the action taken?

If the former, another approach would be to use a main form (for the
permit
info) and a subform. The source for the subform would be dynamically set
by, say, the choice of the action on the main form. Thus, the same
subform
control on the main form could be "fed" by one of three different
(sub)forms.

Or have I misunderstood your situation?

Regards

Jeff Boyce
Microsoft Office/Access MVP

What is the best way to handle a transition from one form to another?

I'm creating a database to track the application for various types of
permits. What will happen is when an application first comes in, the
common
data (name/address of applicant) will be stored in one table and the
record
will be assigned a permit number. Based on evaluation of the
application,
the processing can take various paths, for example, an exemption,
approval
or
denial (with supporting documentation). This data I plan to store in
separate
respective tables (table for exemption, approval, denial). All will be
tied
together by the permit number field. After the initial form is
completed
with the common data and the user clicks on a button to open the
Exemption
form, for example, what is the best way to pre-populate the Permit
number
into the Exemption form? If the field name is [PerNum] and the initial
data
entry form is [frmApp], would the following code work in the PerNum
field
on
the Exemption form:

=[Forms]![frmApp]![PerNum]

Should I add an if is null code to the above so the PerNum doesn't
get
accidentally overwritten upon opening the Exemption form?

Is there a better way? Any suggestions appreciated.

 

[Guest]

Jeff,

Do you have any suggestions/recommendations on the best way to to
pre-populate the Permit number into the Exemption/Denied/Approval data entry
forms (if applicable)? I want to have buttons on the initial data entry form
linking to these other forms. If the field name is [PerNum] and the initial
data entry form is [frmApp], would the following code work in the PerNum
field (default value) on the Exemption/Denied/Approval forms:

=[Forms]![frmApp]![PerNum]


I just don't want the user to have to re-key in the number as it is 10
character's long.

Do I need to add any type of "if is null code..." to the
above to ensure this field won't get accidentaly get overwritten?

Thanks.

Jade

Since you hadn't mentioned these facts before, I had to ask.

If your data is unique to the categories, then yes, it makes sense to have
separate tables.

Regards

Jeff Boyce
Microsoft Office/Access MVP

I feel that Exemptions, Approvals and Denials would justify separate
tables.
Each table would have between 20 to 50 unique, separate fields. Yes, I am
trying to categorize the action taken. Wouldn't including all the fields
in
one flat table become cumbersome? The above tables would be related to
the
main table in a 1 to 1 relationship.

Jade

Jade

Recommendations will depend on your data situation. Are you saying that
"Exemptions", "Approvals", and "Denials" each have their own unique
attributes (thus justifying separate tables, related 1-to-1 to the main
permit table)? Or do they have nearly all fields/attributes in common,
and
you've elected separate tables to "categorize" the action taken?

If the former, another approach would be to use a main form (for the
permit
info) and a subform. The source for the subform would be dynamically set
by, say, the choice of the action on the main form. Thus, the same
subform
control on the main form could be "fed" by one of three different
(sub)forms.

Or have I misunderstood your situation?

Regards

Jeff Boyce
Microsoft Office/Access MVP

What is the best way to handle a transition from one form to another?

I'm creating a database to track the application for various types of
permits. What will happen is when an application first comes in, the
common
data (name/address of applicant) will be stored in one table and the
record
will be assigned a permit number. Based on evaluation of the
application,
the processing can take various paths, for example, an exemption,
approval
or
denial (with supporting documentation). This data I plan to store in
separate
respective tables (table for exemption, approval, denial). All will be
tied
together by the permit number field. After the initial form is
completed
with the common data and the user clicks on a button to open the
Exemption
form, for example, what is the best way to pre-populate the Permit
number
into the Exemption form? If the field name is [PerNum] and the initial
data
entry form is [frmApp], would the following code work in the PerNum
field
on
the Exemption form:

=[Forms]![frmApp]![PerNum]

Should I add an if is null code to the above so the PerNum doesn't
get
accidentally overwritten upon opening the Exemption form?

Is there a better way? Any suggestions appreciated.

 

[Jeff Boyce]

Jade

Re-read my earlier response. Look into mainform/subform construction.

Regards

Jeff Boyce
Microsoft Office/Access MVP

Jeff,

Do you have any suggestions/recommendations on the best way to to
pre-populate the Permit number into the Exemption/Denied/Approval data
entry
forms (if applicable)? I want to have buttons on the initial data entry
form
linking to these other forms. If the field name is [PerNum] and the
initial
data entry form is [frmApp], would the following code work in the PerNum
field (default value) on the Exemption/Denied/Approval forms:

=[Forms]![frmApp]![PerNum]


I just don't want the user to have to re-key in the number as it is 10
character's long.

Do I need to add any type of "if is null code..." to
the
above to ensure this field won't get accidentaly get overwritten?

Thanks.

Jade

Since you hadn't mentioned these facts before, I had to ask.

If your data is unique to the categories, then yes, it makes sense to
have
separate tables.

Regards

Jeff Boyce
Microsoft Office/Access MVP

I feel that Exemptions, Approvals and Denials would justify separate
tables.
Each table would have between 20 to 50 unique, separate fields. Yes, I
am
trying to categorize the action taken. Wouldn't including all the
fields
in
one flat table become cumbersome? The above tables would be related to
the
main table in a 1 to 1 relationship.

Jade

:

Jade

Recommendations will depend on your data situation. Are you saying
that
"Exemptions", "Approvals", and "Denials" each have their own unique
attributes (thus justifying separate tables, related 1-to-1 to the
main
permit table)? Or do they have nearly all fields/attributes in
common,
and
you've elected separate tables to "categorize" the action taken?

If the former, another approach would be to use a main form (for the
permit
info) and a subform. The source for the subform would be dynamically
set
by, say, the choice of the action on the main form. Thus, the same
subform
control on the main form could be "fed" by one of three different
(sub)forms.

Or have I misunderstood your situation?

Regards

Jeff Boyce
Microsoft Office/Access MVP

What is the best way to handle a transition from one form to
another?

I'm creating a database to track the application for various types
of
permits. What will happen is when an application first comes in,
the
common
data (name/address of applicant) will be stored in one table and the
record
will be assigned a permit number. Based on evaluation of the
application,
the processing can take various paths, for example, an exemption,
approval
or
denial (with supporting documentation). This data I plan to store in
separate
respective tables (table for exemption, approval, denial). All will
be
tied
together by the permit number field. After the initial form is
completed
with the common data and the user clicks on a button to open the
Exemption
form, for example, what is the best way to pre-populate the Permit
number
into the Exemption form? If the field name is [PerNum] and the
initial
data
entry form is [frmApp], would the following code work in the PerNum
field
on
the Exemption form:

=[Forms]![frmApp]![PerNum]

Should I add an if is null code to the above so the PerNum doesn't
get
accidentally overwritten upon opening the Exemption form?

Is there a better way? Any suggestions appreciated.