[AccessD] Push Data

Joe Hecht jmhecht at earthlink.net
Wed Jan 11 14:05:20 CST 2006


You are not confused, I may be. 

Seen my last post about A2k & A2k3

Joe Hecht
jmhecht at earthlink.net
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Charlotte Foust
Sent: Wednesday, January 11, 2006 11:27 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Push Data

No, the child form is bound to the table and linked to the
parent form
on the EmployeeID.  Unless I totally misunderstand what
you're trying to
do.

Charlotte Foust


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Joe Hecht
Sent: Wednesday, January 11, 2006 9:57 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Push Data


Doesn't the table need to be open? That's why I was going to
push pull
from the cbo query?

Joe Hecht
jmhecht at earthlink.net

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Charlotte
Foust
Sent: Wednesday, January 11, 2006 9:44 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Push Data

You actually don't need to do either.  If that info is in a
table
already, all you need is a subform linked to EmployeeID to
display the
values for those fields.  If the employee ID  combo is and
unbound
control on the parent form, the employee subform can be
linked to the
value selected and nothing needs to be pushed anywhere
because the child
form will fill in automatically.

Charlotte Foust


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Joe Hecht
Sent: Wednesday, January 11, 2006 9:26 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Push Data


The form records workplace accidents.

Much of the information about the employee exists in the
employee
tables. When a new incident is added I want the user to
select the
employee name and then automatically fill in fields like
DOB, Hire Date,
and license info.

I thought it would be better to push data out in after
update of cboemployee select. You seem to be recommending
that I pull instead.

Do I understand you correctly? 

Joe Hecht
jmhecht at earthlink.net
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Charlotte
Foust
Sent: Wednesday, January 11, 2006 8:51 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Push Data

Joe,

If the subforms are linked to the parent form, the related
records
should show up automatically ... Or are you talking about
something
else?  Is this on existing or new records in the parent and
child forms?
You can use code to fill in values, but it's generally a
better idea to
let the child form retrieve the values rather than having it
manipulated
from outside.  I'm not clear on the scenario you envision,
so I may just
be confusing you.

Charlotte Foust


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Joe Hecht
Sent: Wednesday, January 11, 2006 8:41 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Push Data


I want the user to select an employee and then it will in
various fields
in the parent and child forms.

Joe Hecht
jmhecht at earthlink.net
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Charlotte
Foust
Sent: Wednesday, January 11, 2006 8:34 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Push Data

What do you mean by "push data"?  Ordinarily, you pull data
from the
parent from into the child form.  In code, it's simply
Parent!controlname to reference a value.  You can set the
default value
of a textbox on a child form to "=[Parent]![EmployeeID]"
(without the
quotes), for instance.  Does that help?

Charlotte Foust


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Joe Hecht
Sent: Tuesday, January 10, 2006 8:23 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Push Data


My head still hurts from the DateDiff fight I had over the
weekend.

 

I am going to have a master form and many sub forms on a tab
control.

 

What issues do I want to look out for in trying to push data
from the
parent to various sub forms.

 

I want to not duplicate data in other tables. Selecting one
employee, I
want to fill in various information.

 

Thanks in Advance.

 

Joe Hecht

jmhecht at earthlink.net

 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list