delete unneccesary tabs

R

randrewrussell

here is the problem: I had someone design a database that upon actual
use I discovered contained too many fields, tabs etc. Unfortunately,
this extra garbage resulted in the need for a sub form on the first tab
page. How can I delete the unneccesary tabs and fields, and move the
sub form up into the tab area where it should have been in the first
place? Thanks
 
M

Marshall Barton

here is the problem: I had someone design a database that upon actual
use I discovered contained too many fields, tabs etc. Unfortunately,
this extra garbage resulted in the need for a sub form on the first tab
page. How can I delete the unneccesary tabs and fields, and move the
sub form up into the tab area where it should have been in the first
place?


First, open the form in design view. Once in design view, a
control can be deleted by clicking on it and hitting the
Delete key, using Ctrl+X (Cut), or using the Edit - Delete
menu item.

A control (subform or whatever) can be moved to a tab
control page by clicking on the control and using Ctrl+X,
then click on the page's tab and use Ctrl+V (Paste).

Other than moving things to (or from) tab pages, controls
can be moved around on the form by just dragging it where
ever you want it or by setting its Left and Top properties
in the control's property sheet.
 
R

randrewrussell

Marshall:
Thanks for the advice! I was able to delete the excess tabs(pages)
however my problem with the subform continue. Basically, the designer
incorporated a "button" that he placed on the first page of the form.
He said it was neccesary because there were too many (tabs?)pages to
fit in the first form. By pressing the button, another form (subform)
opens with 4 additional pages. I want to (1) eliminate the button (2)
eliminate 2 of the 4 additional pages in the subform and then have the
2 remaining pages be placed as tabs in the original form and present
when the database first opens. Can I do it? Thanks Rich
 
M

Marshall Barton

Moving things from one form to another (subform is
irrelevant) is a matter of cutting and pasting the pieces
and then hooking up the event procedures again. First, Us a
copy of the forms so you can quickly undo any mistakes you
make. Then create the two new pages on the main form and
start moving the controls on the subform to the new table
pages (you can select all the controls on a page by dragging
a selection box across all the controls on the page). Then
Copy/Paste the VBA procedures behind the controls to the
main form's modules and Check each control's event
properties to make sure that the events with code have
[Event Procedure] in their corresponding ON... property.
After you've move the desired stuff to the main form, delete
the subform. It's all a little tedious, but once you get
the hang of it, it should go fairly quickly.
 
R

randrewrussell

Hey Marsh:
First, I want to thank you for your time and your great advice. I have
followed your instructions and have succeeded in modifying and
preparing (lets call the first form "All info") "All info" for the
receipt of the second form("Defendant info") fields etc. It appears to
me that the designers Dina B. and Bill C. actually built two distinct
forms! One they named "All info" and the other they named "Defendant
info". The second form is not, repeat not, a subform. They then
incorporated a control button into the first tab page of form "All
info" thereby linking, albeit awkwardly, the two forms together. Does
this effect my ability to transfer and really merge the 2 pages that I
want from form 2, "Defendant info" into form 1, "All info". Thanks and
if you need any payment for your time please contact me at the email
address. I also want to say that this is very cool. I finally feel like
I can tweak this thing to match my needs. "Form Follows Function" you
know.
Marshall said:
Moving things from one form to another (subform is
irrelevant) is a matter of cutting and pasting the pieces
and then hooking up the event procedures again. First, Us a
copy of the forms so you can quickly undo any mistakes you
make. Then create the two new pages on the main form and
start moving the controls on the subform to the new table
pages (you can select all the controls on a page by dragging
a selection box across all the controls on the page). Then
Copy/Paste the VBA procedures behind the controls to the
main form's modules and Check each control's event
properties to make sure that the events with code have
[Event Procedure] in their corresponding ON... property.
After you've move the desired stuff to the main form, delete
the subform. It's all a little tedious, but once you get
the hang of it, it should go fairly quickly.
--
Marsh
MVP [MS Access]


Thanks for the advice! I was able to delete the excess tabs(pages)
however my problem with the subform continue. Basically, the designer
incorporated a "button" that he placed on the first page of the form.
He said it was neccesary because there were too many (tabs?)pages to
fit in the first form. By pressing the button, another form (subform)
opens with 4 additional pages. I want to (1) eliminate the button (2)
eliminate 2 of the 4 additional pages in the subform and then have the
2 remaining pages be placed as tabs in the original form and present
when the database first opens. Can I do it? Thanks Rich
 
R

randrewrussell

Hey!
I made further progress with the "task" at hand. I was able to delete
the extra pages from form 2 "Def Info". Then I selected and moved the
entire contents of the 2 pages I wanted to be incorporated into Form 1
"All info". However when I opened the modified form I noticed that all
the fields that had been moved from Form 2 to Form 1 showed a message
"# name" in the field box. I assume this is from my failure to properly
address the VBA code? I have to work on how to get behind the box into
the code and turn on etc. Please advise, I feel I am close to getting
this done. Thanks again.
Hey Marsh:
First, I want to thank you for your time and your great advice. I have
followed your instructions and have succeeded in modifying and
preparing (lets call the first form "All info") "All info" for the
receipt of the second form("Defendant info") fields etc. It appears to
me that the designers Dina B. and Bill C. actually built two distinct
forms! One they named "All info" and the other they named "Defendant
info". The second form is not, repeat not, a subform. They then
incorporated a control button into the first tab page of form "All
info" thereby linking, albeit awkwardly, the two forms together. Does
this effect my ability to transfer and really merge the 2 pages that I
want from form 2, "Defendant info" into form 1, "All info". Thanks and
if you need any payment for your time please contact me at the email
address. I also want to say that this is very cool. I finally feel like
I can tweak this thing to match my needs. "Form Follows Function" you
know.
Marshall said:
Moving things from one form to another (subform is
irrelevant) is a matter of cutting and pasting the pieces
and then hooking up the event procedures again. First, Us a
copy of the forms so you can quickly undo any mistakes you
make. Then create the two new pages on the main form and
start moving the controls on the subform to the new table
pages (you can select all the controls on a page by dragging
a selection box across all the controls on the page). Then
Copy/Paste the VBA procedures behind the controls to the
main form's modules and Check each control's event
properties to make sure that the events with code have
[Event Procedure] in their corresponding ON... property.
After you've move the desired stuff to the main form, delete
the subform. It's all a little tedious, but once you get
the hang of it, it should go fairly quickly.
--
Marsh
MVP [MS Access]


Thanks for the advice! I was able to delete the excess tabs(pages)
however my problem with the subform continue. Basically, the designer
incorporated a "button" that he placed on the first page of the form.
He said it was neccesary because there were too many (tabs?)pages to
fit in the first form. By pressing the button, another form (subform)
opens with 4 additional pages. I want to (1) eliminate the button (2)
eliminate 2 of the 4 additional pages in the subform and then have the
2 remaining pages be placed as tabs in the original form and present
when the database first opens. Can I do it? Thanks Rich

Marshall Barton wrote:
[email protected] wrote:

here is the problem: I had someone design a database that upon actual
use I discovered contained too many fields, tabs etc. Unfortunately,
this extra garbage resulted in the need for a sub form on the first tab
page. How can I delete the unneccesary tabs and fields, and move the
sub form up into the tab area where it should have been in the first
place?


First, open the form in design view. Once in design view, a
control can be deleted by clicking on it and hitting the
Delete key, using Ctrl+X (Cut), or using the Edit - Delete
menu item.

A control (subform or whatever) can be moved to a tab
control page by clicking on the control and using Ctrl+X,
then click on the page's tab and use Ctrl+V (Paste).

Other than moving things to (or from) tab pages, controls
can be moved around on the form by just dragging it where
ever you want it or by setting its Left and Top properties
in the control's property sheet.
 
R

randrewrussell

hey this is the part I am going to have to really study:
"Then
Copy/Paste the VBA procedures behind the controls to the
main form's modules and Check each control's event
properties to make sure that the events with code have
[Event Procedure] in their corresponding ON... property."
Hey!
I made further progress with the "task" at hand. I was able to delete
the extra pages from form 2 "Def Info". Then I selected and moved the
entire contents of the 2 pages I wanted to be incorporated into Form 1
"All info". However when I opened the modified form I noticed that all
the fields that had been moved from Form 2 to Form 1 showed a message
"# name" in the field box. I assume this is from my failure to properly
address the VBA code? I have to work on how to get behind the box into
the code and turn on etc. Please advise, I feel I am close to getting
this done. Thanks again.
Hey Marsh:
First, I want to thank you for your time and your great advice. I have
followed your instructions and have succeeded in modifying and
preparing (lets call the first form "All info") "All info" for the
receipt of the second form("Defendant info") fields etc. It appears to
me that the designers Dina B. and Bill C. actually built two distinct
forms! One they named "All info" and the other they named "Defendant
info". The second form is not, repeat not, a subform. They then
incorporated a control button into the first tab page of form "All
info" thereby linking, albeit awkwardly, the two forms together. Does
this effect my ability to transfer and really merge the 2 pages that I
want from form 2, "Defendant info" into form 1, "All info". Thanks and
if you need any payment for your time please contact me at the email
address. I also want to say that this is very cool. I finally feel like
I can tweak this thing to match my needs. "Form Follows Function" you
know.
Marshall said:
Moving things from one form to another (subform is
irrelevant) is a matter of cutting and pasting the pieces
and then hooking up the event procedures again. First, Us a
copy of the forms so you can quickly undo any mistakes you
make. Then create the two new pages on the main form and
start moving the controls on the subform to the new table
pages (you can select all the controls on a page by dragging
a selection box across all the controls on the page). Then
Copy/Paste the VBA procedures behind the controls to the
main form's modules and Check each control's event
properties to make sure that the events with code have
[Event Procedure] in their corresponding ON... property.
After you've move the desired stuff to the main form, delete
the subform. It's all a little tedious, but once you get
the hang of it, it should go fairly quickly.
--
Marsh
MVP [MS Access]


[email protected] wrote:
Thanks for the advice! I was able to delete the excess tabs(pages)
however my problem with the subform continue. Basically, the designer
incorporated a "button" that he placed on the first page of the form.
He said it was neccesary because there were too many (tabs?)pages to
fit in the first form. By pressing the button, another form (subform)
opens with 4 additional pages. I want to (1) eliminate the button (2)
eliminate 2 of the 4 additional pages in the subform and then have the
2 remaining pages be placed as tabs in the original form and present
when the database first opens. Can I do it? Thanks Rich

Marshall Barton wrote:
[email protected] wrote:

here is the problem: I had someone design a database that upon actual
use I discovered contained too many fields, tabs etc. Unfortunately,
this extra garbage resulted in the need for a sub form on the first tab
page. How can I delete the unneccesary tabs and fields, and move the
sub form up into the tab area where it should have been in the first
place?


First, open the form in design view. Once in design view, a
control can be deleted by clicking on it and hitting the
Delete key, using Ctrl+X (Cut), or using the Edit - Delete
menu item.

A control (subform or whatever) can be moved to a tab
control page by clicking on the control and using Ctrl+X,
then click on the page's tab and use Ctrl+V (Paste).

Other than moving things to (or from) tab pages, controls
can be moved around on the form by just dragging it where
ever you want it or by setting its Left and Top properties
in the control's property sheet.
 
R

randrewrussell

Sorry but the error message reads as follows "#name?"
hey this is the part I am going to have to really study:
"Then
Copy/Paste the VBA procedures behind the controls to the
main form's modules and Check each control's event
properties to make sure that the events with code have
[Event Procedure] in their corresponding ON... property."
Hey!
I made further progress with the "task" at hand. I was able to delete
the extra pages from form 2 "Def Info". Then I selected and moved the
entire contents of the 2 pages I wanted to be incorporated into Form 1
"All info". However when I opened the modified form I noticed that all
the fields that had been moved from Form 2 to Form 1 showed a message
"# name" in the field box. I assume this is from my failure to properly
address the VBA code? I have to work on how to get behind the box into
the code and turn on etc. Please advise, I feel I am close to getting
this done. Thanks again.
Hey Marsh:
First, I want to thank you for your time and your great advice. I have
followed your instructions and have succeeded in modifying and
preparing (lets call the first form "All info") "All info" for the
receipt of the second form("Defendant info") fields etc. It appears to
me that the designers Dina B. and Bill C. actually built two distinct
forms! One they named "All info" and the other they named "Defendant
info". The second form is not, repeat not, a subform. They then
incorporated a control button into the first tab page of form "All
info" thereby linking, albeit awkwardly, the two forms together. Does
this effect my ability to transfer and really merge the 2 pages that I
want from form 2, "Defendant info" into form 1, "All info". Thanks and
if you need any payment for your time please contact me at the email
address. I also want to say that this is very cool. I finally feel like
I can tweak this thing to match my needs. "Form Follows Function" you
know.
Marshall Barton wrote:
Moving things from one form to another (subform is
irrelevant) is a matter of cutting and pasting the pieces
and then hooking up the event procedures again. First, Us a
copy of the forms so you can quickly undo any mistakes you
make. Then create the two new pages on the main form and
start moving the controls on the subform to the new table
pages (you can select all the controls on a page by dragging
a selection box across all the controls on the page). Then
Copy/Paste the VBA procedures behind the controls to the
main form's modules and Check each control's event
properties to make sure that the events with code have
[Event Procedure] in their corresponding ON... property.
After you've move the desired stuff to the main form, delete
the subform. It's all a little tedious, but once you get
the hang of it, it should go fairly quickly.
--
Marsh
MVP [MS Access]


[email protected] wrote:
Thanks for the advice! I was able to delete the excess tabs(pages)
however my problem with the subform continue. Basically, the designer
incorporated a "button" that he placed on the first page of the form.
He said it was neccesary because there were too many (tabs?)pages to
fit in the first form. By pressing the button, another form (subform)
opens with 4 additional pages. I want to (1) eliminate the button (2)
eliminate 2 of the 4 additional pages in the subform and then have the
2 remaining pages be placed as tabs in the original form and present
when the database first opens. Can I do it? Thanks Rich

Marshall Barton wrote:
[email protected] wrote:

here is the problem: I had someone design a database that upon actual
use I discovered contained too many fields, tabs etc. Unfortunately,
this extra garbage resulted in the need for a sub form on the first tab
page. How can I delete the unneccesary tabs and fields, and move the
sub form up into the tab area where it should have been in the first
place?


First, open the form in design view. Once in design view, a
control can be deleted by clicking on it and hitting the
Delete key, using Ctrl+X (Cut), or using the Edit - Delete
menu item.

A control (subform or whatever) can be moved to a tab
control page by clicking on the control and using Ctrl+X,
then click on the page's tab and use Ctrl+V (Paste).

Other than moving things to (or from) tab pages, controls
can be moved around on the form by just dragging it where
ever you want it or by setting its Left and Top properties
in the control's property sheet.
 
M

Marshall Barton

Whoops ;-) If the Defendant form is not a subform, then
you probably want to make it a subform. I hadn't realized
that it was bound to a different table. Somehow I had the
impression both forms were bound to the same table or one of
them was unbound. If there are two tables involved, you
really should use two forms. In this case and assuming that
the defendants form's record source table is related to the
AllInfo record source table in some way, then a subform is
the recommended way to present the data. The one side table
is bound to the main form and the many side table is bound
to the sub form. I think you have said that you want the
subform to be on a tab page, not as a separate form.

OTOH, if the main form is not bound to a table, then a
subform would not be necessary, though possibly desirable.
The unbound controls are probably being used to filter the
data that users want to see from the Defendants table.

Regardless of all that, it should be clear that I need a lot
of specific information before trying to provide detailed
instruction on how to arrange the form and subform (if a
subform is even needed?)

The reason you are getting #Name in some controls is because
they are bound to a field that is not in the form's record
source.

Payment is not appropriate for newsgroup support, we're all
volunteers here. Offline consulting is usually reserved for
regular clients and I would rather not go there.

The easiest way to get to the code behind a control is to
click on the event property of interest and then click in
the builder button in the property's right margin (the one
with three dots). You should then be taken directly to the
corresponding event procedure. You can then edit or
add/paste the appropriate code into the procedure. To
connect the event to the event procedure, the event property
needs to have the text [Event Procedure] (including the
square brackets). It's common for that to be placed into
the event property automatically when you click on the
builder button, just check to make sure it was done.
--
Marsh
MVP [MS Access]


First, I want to thank you for your time and your great advice. I have
followed your instructions and have succeeded in modifying and
preparing (lets call the first form "All info") "All info" for the
receipt of the second form("Defendant info") fields etc. It appears to
me that the designers Dina B. and Bill C. actually built two distinct
forms! One they named "All info" and the other they named "Defendant
info". The second form is not, repeat not, a subform. They then
incorporated a control button into the first tab page of form "All
info" thereby linking, albeit awkwardly, the two forms together. Does
this effect my ability to transfer and really merge the 2 pages that I
want from form 2, "Defendant info" into form 1, "All info". Thanks and
if you need any payment for your time please contact me at the email
address. I also want to say that this is very cool. I finally feel like
I can tweak this thing to match my needs. "Form Follows Function" you
know.
Marshall said:
Moving things from one form to another (subform is
irrelevant) is a matter of cutting and pasting the pieces
and then hooking up the event procedures again. First, Us a
copy of the forms so you can quickly undo any mistakes you
make. Then create the two new pages on the main form and
start moving the controls on the subform to the new table
pages (you can select all the controls on a page by dragging
a selection box across all the controls on the page). Then
Copy/Paste the VBA procedures behind the controls to the
main form's modules and Check each control's event
properties to make sure that the events with code have
[Event Procedure] in their corresponding ON... property.
After you've move the desired stuff to the main form, delete
the subform. It's all a little tedious, but once you get
the hang of it, it should go fairly quickly.


Thanks for the advice! I was able to delete the excess tabs(pages)
however my problem with the subform continue. Basically, the designer
incorporated a "button" that he placed on the first page of the form.
He said it was neccesary because there were too many (tabs?)pages to
fit in the first form. By pressing the button, another form (subform)
opens with 4 additional pages. I want to (1) eliminate the button (2)
eliminate 2 of the 4 additional pages in the subform and then have the
2 remaining pages be placed as tabs in the original form and present
when the database first opens. Can I do it? Thanks Rich

Marshall Barton wrote:
[email protected] wrote:

here is the problem: I had someone design a database that upon actual
use I discovered contained too many fields, tabs etc. Unfortunately,
this extra garbage resulted in the need for a sub form on the first tab
page. How can I delete the unneccesary tabs and fields, and move the
sub form up into the tab area where it should have been in the first
place?


First, open the form in design view. Once in design view, a
control can be deleted by clicking on it and hitting the
Delete key, using Ctrl+X (Cut), or using the Edit - Delete
menu item.

A control (subform or whatever) can be moved to a tab
control page by clicking on the control and using Ctrl+X,
then click on the page's tab and use Ctrl+V (Paste).

Other than moving things to (or from) tab pages, controls
can be moved around on the form by just dragging it where
ever you want it or by setting its Left and Top properties
in the control's property sheet.
 
R

randrewrussell

Hi, I almost could l have guessed that was the problem when I found
that the forms had separate and distinct tables. (separate forms?) They
share a common field (key?) Is this a possible solution: Build a Dbase
to the specs I am looking for and then transfer the data?



Marshall said:
Whoops ;-) If the Defendant form is not a subform, then
you probably want to make it a subform. I hadn't realized
that it was bound to a different table. Somehow I had the
impression both forms were bound to the same table or one of
them was unbound. If there are two tables involved, you
really should use two forms. In this case and assuming that
the defendants form's record source table is related to the
AllInfo record source table in some way, then a subform is
the recommended way to present the data. The one side table
is bound to the main form and the many side table is bound
to the sub form. I think you have said that you want the
subform to be on a tab page, not as a separate form.

OTOH, if the main form is not bound to a table, then a
subform would not be necessary, though possibly desirable.
The unbound controls are probably being used to filter the
data that users want to see from the Defendants table.

Regardless of all that, it should be clear that I need a lot
of specific information before trying to provide detailed
instruction on how to arrange the form and subform (if a
subform is even needed?)

The reason you are getting #Name in some controls is because
they are bound to a field that is not in the form's record
source.

Payment is not appropriate for newsgroup support, we're all
volunteers here. Offline consulting is usually reserved for
regular clients and I would rather not go there.

The easiest way to get to the code behind a control is to
click on the event property of interest and then click in
the builder button in the property's right margin (the one
with three dots). You should then be taken directly to the
corresponding event procedure. You can then edit or
add/paste the appropriate code into the procedure. To
connect the event to the event procedure, the event property
needs to have the text [Event Procedure] (including the
square brackets). It's common for that to be placed into
the event property automatically when you click on the
builder button, just check to make sure it was done.
--
Marsh
MVP [MS Access]


First, I want to thank you for your time and your great advice. I have
followed your instructions and have succeeded in modifying and
preparing (lets call the first form "All info") "All info" for the
receipt of the second form("Defendant info") fields etc. It appears to
me that the designers Dina B. and Bill C. actually built two distinct
forms! One they named "All info" and the other they named "Defendant
info". The second form is not, repeat not, a subform. They then
incorporated a control button into the first tab page of form "All
info" thereby linking, albeit awkwardly, the two forms together. Does
this effect my ability to transfer and really merge the 2 pages that I
want from form 2, "Defendant info" into form 1, "All info". Thanks and
if you need any payment for your time please contact me at the email
address. I also want to say that this is very cool. I finally feel like
I can tweak this thing to match my needs. "Form Follows Function" you
know.
Marshall said:
Moving things from one form to another (subform is
irrelevant) is a matter of cutting and pasting the pieces
and then hooking up the event procedures again. First, Us a
copy of the forms so you can quickly undo any mistakes you
make. Then create the two new pages on the main form and
start moving the controls on the subform to the new table
pages (you can select all the controls on a page by dragging
a selection box across all the controls on the page). Then
Copy/Paste the VBA procedures behind the controls to the
main form's modules and Check each control's event
properties to make sure that the events with code have
[Event Procedure] in their corresponding ON... property.
After you've move the desired stuff to the main form, delete
the subform. It's all a little tedious, but once you get
the hang of it, it should go fairly quickly.


[email protected] wrote:
Thanks for the advice! I was able to delete the excess tabs(pages)
however my problem with the subform continue. Basically, the designer
incorporated a "button" that he placed on the first page of the form.
He said it was neccesary because there were too many (tabs?)pages to
fit in the first form. By pressing the button, another form (subform)
opens with 4 additional pages. I want to (1) eliminate the button (2)
eliminate 2 of the 4 additional pages in the subform and then have the
2 remaining pages be placed as tabs in the original form and present
when the database first opens. Can I do it? Thanks Rich

Marshall Barton wrote:
[email protected] wrote:

here is the problem: I had someone design a database that upon actual
use I discovered contained too many fields, tabs etc. Unfortunately,
this extra garbage resulted in the need for a sub form on the first tab
page. How can I delete the unneccesary tabs and fields, and move the
sub form up into the tab area where it should have been in the first
place?


First, open the form in design view. Once in design view, a
control can be deleted by clicking on it and hitting the
Delete key, using Ctrl+X (Cut), or using the Edit - Delete
menu item.

A control (subform or whatever) can be moved to a tab
control page by clicking on the control and using Ctrl+X,
then click on the page's tab and use Ctrl+V (Paste).

Other than moving things to (or from) tab pages, controls
can be moved around on the form by just dragging it where
ever you want it or by setting its Left and Top properties
in the control's property sheet.
 
M

Marshall Barton

Well you could build a separate mdb file, but why. You
haven't said anything so far that indicates a need for doing
that.

Adding a subform to your tab control is a trivial exercise,
especially since the defendants form has already been
created. Again, working on a copy so you can quickly
retreat form these false starts we've been making. Just
select the tab page you want to contain the subform, then
drag the defendants form object from the Database window and
drop it on the the tab page. Make sure the subform
control's Link Master/Child Fields properties are set to the
common field by clicking on the subform's border and looking
at its property sheet.
--
Marsh
MVP [MS Access]


Hi, I almost could l have guessed that was the problem when I found
that the forms had separate and distinct tables. (separate forms?) They
share a common field (key?) Is this a possible solution: Build a Dbase
to the specs I am looking for and then transfer the data?


Marshall said:
Whoops ;-) If the Defendant form is not a subform, then
you probably want to make it a subform. I hadn't realized
that it was bound to a different table. Somehow I had the
impression both forms were bound to the same table or one of
them was unbound. If there are two tables involved, you
really should use two forms. In this case and assuming that
the defendants form's record source table is related to the
AllInfo record source table in some way, then a subform is
the recommended way to present the data. The one side table
is bound to the main form and the many side table is bound
to the sub form. I think you have said that you want the
subform to be on a tab page, not as a separate form.

OTOH, if the main form is not bound to a table, then a
subform would not be necessary, though possibly desirable.
The unbound controls are probably being used to filter the
data that users want to see from the Defendants table.

Regardless of all that, it should be clear that I need a lot
of specific information before trying to provide detailed
instruction on how to arrange the form and subform (if a
subform is even needed?)

The reason you are getting #Name in some controls is because
they are bound to a field that is not in the form's record
source.

Payment is not appropriate for newsgroup support, we're all
volunteers here. Offline consulting is usually reserved for
regular clients and I would rather not go there.

The easiest way to get to the code behind a control is to
click on the event property of interest and then click in
the builder button in the property's right margin (the one
with three dots). You should then be taken directly to the
corresponding event procedure. You can then edit or
add/paste the appropriate code into the procedure. To
connect the event to the event procedure, the event property
needs to have the text [Event Procedure] (including the
square brackets). It's common for that to be placed into
the event property automatically when you click on the
builder button, just check to make sure it was done.


First, I want to thank you for your time and your great advice. I have
followed your instructions and have succeeded in modifying and
preparing (lets call the first form "All info") "All info" for the
receipt of the second form("Defendant info") fields etc. It appears to
me that the designers Dina B. and Bill C. actually built two distinct
forms! One they named "All info" and the other they named "Defendant
info". The second form is not, repeat not, a subform. They then
incorporated a control button into the first tab page of form "All
info" thereby linking, albeit awkwardly, the two forms together. Does
this effect my ability to transfer and really merge the 2 pages that I
want from form 2, "Defendant info" into form 1, "All info". Thanks and
if you need any payment for your time please contact me at the email
address. I also want to say that this is very cool. I finally feel like
I can tweak this thing to match my needs. "Form Follows Function" you
know.
Marshall Barton wrote:
Moving things from one form to another (subform is
irrelevant) is a matter of cutting and pasting the pieces
and then hooking up the event procedures again. First, Us a
copy of the forms so you can quickly undo any mistakes you
make. Then create the two new pages on the main form and
start moving the controls on the subform to the new table
pages (you can select all the controls on a page by dragging
a selection box across all the controls on the page). Then
Copy/Paste the VBA procedures behind the controls to the
main form's modules and Check each control's event
properties to make sure that the events with code have
[Event Procedure] in their corresponding ON... property.
After you've move the desired stuff to the main form, delete
the subform. It's all a little tedious, but once you get
the hang of it, it should go fairly quickly.


[email protected] wrote:
Thanks for the advice! I was able to delete the excess tabs(pages)
however my problem with the subform continue. Basically, the designer
incorporated a "button" that he placed on the first page of the form.
He said it was neccesary because there were too many (tabs?)pages to
fit in the first form. By pressing the button, another form (subform)
opens with 4 additional pages. I want to (1) eliminate the button (2)
eliminate 2 of the 4 additional pages in the subform and then have the
2 remaining pages be placed as tabs in the original form and present
when the database first opens. Can I do it? Thanks Rich

Marshall Barton wrote:
[email protected] wrote:

here is the problem: I had someone design a database that upon actual
use I discovered contained too many fields, tabs etc. Unfortunately,
this extra garbage resulted in the need for a sub form on the first tab
page. How can I delete the unneccesary tabs and fields, and move the
sub form up into the tab area where it should have been in the first
place?


First, open the form in design view. Once in design view, a
control can be deleted by clicking on it and hitting the
Delete key, using Ctrl+X (Cut), or using the Edit - Delete
menu item.

A control (subform or whatever) can be moved to a tab
control page by clicking on the control and using Ctrl+X,
then click on the page's tab and use Ctrl+V (Paste).

Other than moving things to (or from) tab pages, controls
can be moved around on the form by just dragging it where
ever you want it or by setting its Left and Top properties
in the control's property sheet.
 
Top