help with tables

[LTOSH]

well i'm back. I hope you are still up for helping me. I have studied the
demo you did for me and have used what you have shown me to get pretty far.
There are a couple of things that are different that i have that i need help
with and still not quite sure i understand. I hope i can explain the first
part here to you see where i am. i'm going to use your demo names to try and
explain what i need.

on your demo "frmWorkoutSchedules" you have 7 days (tabs) and an "update
client Info" tab. no matter the number of rotation days picked the "update
client info" tab is always showing. I do not want the client info to show
here for update. what i have are 9 tabs total (6 for days to workout) 3 tabs
that i want to always show for each client, "cardio" "Obliques" "abs". How
do i get them to always show?
it is currently switching the rotation days chosen but i want those 3 tabs
listed to always be seen.

a second issue is that when i choose a client, and the correct number of
days are chosen in rotation, i go to add exercises it won't let me. it will
pull down for me to choose an exercise but it will not insert the exercise
then allow me to input my sets reps etc.

i hope i have begun to explain where i am at this point. i have enjoyed
studying your demo and have learned more than before. still things i don't
know but in time.
i hope you can help me...gosh i'm so close to have this done...exciting!

let me know...thanks so much!!!
Leslie

you're welcome

oh wow thanks so much. i got it downloaded and the extension changed. Now
gonna study it. I look forward to learning what you have done. You are
awesome! Thanks for the instruction and your time. I'm sure I will be back
soon.
Thanks!!!

okay, i've just uploaded the file. it's an A2000 file, named demo.bak.
****make sure you change the file extension from .bak to .mdb BEFORE you try
to open the file.****
to download the file, go to
http://home.att.net/~california.db/instructions.html and click on the "demo"
link near the bottom of the page.

the db opens to a working form. browse it as a user, then close it and open
frmDeveloperComments, and read the notes. study as much of the setup as you
wish, then open frmALTDeveloperComments, read the notes, and then open
frmALTMenu, and continue from there.

hth


okay. keep an eye on this thread; i'll post back again when the demo is
available, should be by Sunday night.


haha as you were typing me i was posting what i have done so far.
if after you read what i just posted and the help at this point is too
lengthy then yes i guess i can wait till weekend and you could set the
"quick
and dirty" demo up as you called it hahaha. i am currently running
access
2000.

so i need to study up on subform/tabcontrol setup stuff then.
just hard for me to wait (hehehe OCD). I feel that once this is set up
then
the rest will be easier, just feel like this part of it is a roadblock
for
me.
Thanks for your help and any other suggestions you might have.

:

well, the setup is not difficult once you understand how tab controls
work,
subforms work, etc - but getting there can be hard. i think i'd have
to
write a bit of a book to walk you through either scenario
step-by-step.
if
you can wait until the weekend, and if you're using any version of
Access
between A97 and A2003, i'll use the tables/fields we've discussed in
this
thread to build a "quick and dirty" demo of the
listbox/subform/tabcontrol
setup, and load it to my website where you can download it and study
it.
if
you'd like me to do this, post back and tell me what version of Access
you're using.

hth


Thank you so much for your help. however i am having trouble
following
the
set up of all this. Before I go on, which of the two suggestions
would be
the easiest for me?? you see what i have suggested below and you
have
responded, again thank you! If you would suggest which would be
easiest
and
walk me through it I would be grateful. I was not able to
understand
and
follow the directions for the "tabbed control" so if that is what
you
think i
should go with then please help me with that.
Thanks for all your help!

:

then i'd go back to the workout table, get rid of the date field,
and
add a
field to store rotation day. and make sure you don't call the
field
"Day",
as that is a Reserved word in Access. i'd probably just call it
RotationDay.
other than that, i still don't see a reason to change the overall
tables/relationships structure. just remember that after you
change
the
field in the workout table, you'll need to change queries and
forms
that
include that field.

other than that, working with rotation days rather than specific
calendar
dates will actually simplify matters. in the listbox proposal you
posted
earlier in the thread, for example, your RotationDays listbox
would
be a
finite list - simply the maximum number of days you want to
include
in
any
single rotation, such as

1
2
3
4
5
6

some clients might be on a 3-day rotation, some on 4-day, some on
6-day,
whatever is appropriate.

as for your last idea of using a tabbed control, that could easily
work
pretty much the same as the above mentioned listbox. since the
pages
index
is zero-based, i'd probably set the subform's LinkMasterFields
property
to
the name of a hidden textbox control (i'll call it txtDay) with
ControlSource as

=[TabCtl0] + 1

replacing TabCtl0 with the correct name of the tab control on your
form,
of
course. so if the first page of the tab control was Rotation Day
1,
the
page
index (and therefore the value of the tab control) would be 0. 0 +
1
=
1. so
clicking on the first tab would show the exercises assigned to Day
1.
and
again, you could set the DefaultValue of the RotationDay control
in
the
subform to

=[Forms]![frmClients]![txtDay]

so new records entered would be assigned to the day of the
currently
selected tab. so, yes, you could have an unbound form, with a
listbox
showing all your clients, with a single subform for the workouts
table,
set
"under" a tab control so it will "show through" on every tab. and
a
hidden
textbox control to convert the page index value of the tab control
to
the
rotation day. then set the LinkMasterFields property of the
subform
to
the
listbox control (as previously discussed) and the hidden textbox
control.
set the LinkChildFields property to the name of the foreign key
field in
the
subform and the rotation day field in the subform.

choosing a client in the listbox will limit the subform records to
that
client, and choosing a page (tab) of the tabcontrol will further
limit
the
subform records to a particular rotation day for that client.

hth


i apologize for being unclear.

your second scenio is what i am thinking. i just haven't been
able to
explain it properly. Yes i want to set up a workout program
with
a
set of
exercises specific to day 1, day 2 etc as you have described but
specific
for
a client...


:

comments inline.

when i say add "new form", i mean when i click on the button
it
opens
a
blank
frmClient...ready for new information....right now when i
click my
command
button and it opens the frmClient it has the information
that
was
previously
entered.

you can add code to frmClients Load event procedure, as

DoCmd.RunCommand acCmdRecordsGoToNew


i have been playing around some waiting for a response on
last
post
and
wondered about adding on the frmClient a tab control
(labeled
Day

 

[tina]

just set the Caption property, of each tab page, to the name you want to see
in Form view. then go to the code the runs from the listbox control's
AfterUpdate event, and modify the code there. see the following example that
uses the names you posted, as

pg.Visible = (pg.PageIndex < Me!lstClients.Column(2) _
Or pg.Caption = "cardio" _
Or pg.Caption = "Obliques" _
Or pg.Caption = "abs")

hth

well i'm back. I hope you are still up for helping me. I have studied the
demo you did for me and have used what you have shown me to get pretty far.
There are a couple of things that are different that i have that i need help
with and still not quite sure i understand. I hope i can explain the first
part here to you see where i am. i'm going to use your demo names to try and
explain what i need.

on your demo "frmWorkoutSchedules" you have 7 days (tabs) and an "update
client Info" tab. no matter the number of rotation days picked the "update
client info" tab is always showing. I do not want the client info to show
here for update. what i have are 9 tabs total (6 for days to workout) 3 tabs
that i want to always show for each client, "cardio" "Obliques" "abs". How
do i get them to always show?
it is currently switching the rotation days chosen but i want those 3 tabs
listed to always be seen.

a second issue is that when i choose a client, and the correct number of
days are chosen in rotation, i go to add exercises it won't let me. it will
pull down for me to choose an exercise but it will not insert the exercise
then allow me to input my sets reps etc.

i hope i have begun to explain where i am at this point. i have enjoyed
studying your demo and have learned more than before. still things i don't
know but in time.
i hope you can help me...gosh i'm so close to have this done...exciting!

let me know...thanks so much!!!
Leslie

you're welcome

oh wow thanks so much. i got it downloaded and the extension

changed.
Now

gonna study it. I look forward to learning what you have done. You are
awesome! Thanks for the instruction and your time. I'm sure I will

be
back

soon.
Thanks!!!

:

okay, i've just uploaded the file. it's an A2000 file, named demo.bak.
****make sure you change the file extension from .bak to .mdb BEFORE

you
try

to open the file.****
to download the file, go to
http://home.att.net/~california.db/instructions.html and click on

the
"demo"

link near the bottom of the page.

the db opens to a working form. browse it as a user, then close it

and
open

frmDeveloperComments, and read the notes. study as much of the setup

as
you

wish, then open frmALTDeveloperComments, read the notes, and then open
frmALTMenu, and continue from there.

hth


okay. keep an eye on this thread; i'll post back again when the

demo
is

available, should be by Sunday night.


haha as you were typing me i was posting what i have done so far.
if after you read what i just posted and the help at this point

is
too

lengthy then yes i guess i can wait till weekend and you could

set
the

"quick
and dirty" demo up as you called it hahaha. i am currently running
access
2000.

so i need to study up on subform/tabcontrol setup stuff then.
just hard for me to wait (hehehe OCD). I feel that once this is

set
up

then
the rest will be easier, just feel like this part of it is a roadblock
for
me.
Thanks for your help and any other suggestions you might have.

:

well, the setup is not difficult once you understand how tab controls
work,
subforms work, etc - but getting there can be hard. i think

i'd
have

to
write a bit of a book to walk you through either scenario
step-by-step.
if
you can wait until the weekend, and if you're using any version of
Access
between A97 and A2003, i'll use the tables/fields we've

discussed
in

this
thread to build a "quick and dirty" demo of the
listbox/subform/tabcontrol
setup, and load it to my website where you can download it and study
it.
if
you'd like me to do this, post back and tell me what version

of
Access

you're using.

hth


Thank you so much for your help. however i am having trouble
following
the
set up of all this. Before I go on, which of the two suggestions
would be
the easiest for me?? you see what i have suggested below and you
have
responded, again thank you! If you would suggest which would be
easiest
and
walk me through it I would be grateful. I was not able to
understand
and
follow the directions for the "tabbed control" so if that is what
you
think i
should go with then please help me with that.
Thanks for all your help!

:

then i'd go back to the workout table, get rid of the date field,
and
add a
field to store rotation day. and make sure you don't call

the

field
"Day",
as that is a Reserved word in Access. i'd probably just

call
it

RotationDay.
other than that, i still don't see a reason to change the overall
tables/relationships structure. just remember that after you
change
the
field in the workout table, you'll need to change queries and
forms
that
include that field.

other than that, working with rotation days rather than specific
calendar
dates will actually simplify matters. in the listbox

proposal
you

posted
earlier in the thread, for example, your RotationDays listbox
would
be a
finite list - simply the maximum number of days you want to
include
in
any
single rotation, such as

1
2
3
4
5
6

some clients might be on a 3-day rotation, some on 4-day,

some
on

6-day,
whatever is appropriate.

as for your last idea of using a tabbed control, that

could
easily

work
pretty much the same as the above mentioned listbox. since the
pages
index
is zero-based, i'd probably set the subform's LinkMasterFields
property
to
the name of a hidden textbox control (i'll call it txtDay) with
ControlSource as

=[TabCtl0] + 1

replacing TabCtl0 with the correct name of the tab control

on
your

form,
of
course. so if the first page of the tab control was

Rotation
Day

1,
the
page
index (and therefore the value of the tab control) would

be 0.
0 +

1
=
1. so
clicking on the first tab would show the exercises

assigned to
Day

1.
and
again, you could set the DefaultValue of the RotationDay control
in
the
subform to

=[Forms]![frmClients]![txtDay]

so new records entered would be assigned to the day of the
currently
selected tab. so, yes, you could have an unbound form, with a
listbox
showing all your clients, with a single subform for the workouts
table,
set
"under" a tab control so it will "show through" on every

tab.
and

a
hidden
textbox control to convert the page index value of the tab control
to
the
rotation day. then set the LinkMasterFields property of the
subform
to
the
listbox control (as previously discussed) and the hidden textbox
control.
set the LinkChildFields property to the name of the

foreign
key

field in
the
subform and the rotation day field in the subform.

choosing a client in the listbox will limit the subform records to
that
client, and choosing a page (tab) of the tabcontrol will further
limit
the
subform records to a particular rotation day for that client.

hth


i apologize for being unclear.

your second scenio is what i am thinking. i just

haven't
been

able to
explain it properly. Yes i want to set up a workout program
with
a
set of
exercises specific to day 1, day 2 etc as you have

described
but

specific
for
a client...


:

comments inline.

when i say add "new form", i mean when i click on

the
button

it
opens
a
blank
frmClient...ready for new information....right now

when
i

click my
command
button and it opens the frmClient it has the information
that
was
previously
entered.

you can add code to frmClients Load event procedure, as

DoCmd.RunCommand acCmdRecordsGoToNew


i have been playing around some waiting for a

response
on

last
post
and
wondered about adding on the frmClient a tab control
(labeled
Day

 

[LTOSH]

Tina...i have tried to make contact with you a couple of times at the end of
our previous contacts but haven't heard from you so i thought i would start
at the top and try contact. if you can't or don't want to help me further
please say that so i can seek other assistance. i was trying to contact you
since you were familiar with what i was doing. Please let me know...if you
can help you can look at the end of our last contact for the problem i am
having.
Thanks!
Ltosh

 

[tina]

the last post you made to this thread (before today) was on 3/15/09, and i
posted a reply the same day.

hth

 

[John W. Vinson]

Tina...i have tried to make contact with you a couple of times at the end of
our previous contacts but haven't heard from you so i thought i would start
at the top and try contact. if you can't or don't want to help me further
please say that so i can seek other assistance.

Tina, like the rest of the folks who answer questions here, is an unpaid
volunteer. I don't think she'll be the least bit offended if you repost a new
thread asking for help; I'm sure she has other demands on her time, and may
not be able to get back to the newsgroups.