|
|
Parent-Child Relationship
I have an access backend with a 1:M parent-child relationship. I need
to find a way to create a new record in Infopath.
Currently, I can only create a new record by "saving" the parent table,
then "query" for that record saved, which then populates back into the
parent table, so that I can finally enter data into my children tables.
My primary key is not bouncing back into the parent table.
I want to be able to enter data in the parent and children tables, then
press "submit" to save (all in one step).
|
|
0
|
|
|
|
Reply
|
kvc1234 (3)
|
6/17/2005 12:53:17 PM |
|
kvc wrote:
> I have an access backend with a 1:M parent-child relationship. I need
> to find a way to create a new record in Infopath.
>
> Currently, I can only create a new record by "saving" the parent table,
> then "query" for that record saved, which then populates back into the
> parent table, so that I can finally enter data into my children tables.
>
> My primary key is not bouncing back into the parent table.
>
> I want to be able to enter data in the parent and children tables, then
> press "submit" to save (all in one step).
>
Parent and child processes have their own data spaces. A feature called
"copy on write" will move anything inherited from the parent to a
separate place in memory. If you wish to share data, you will need
to either use shared memory, or communicate changes between the
processes using a pipe.
WARNING - If you elect to use shared memory, you have all of the
same problems that you would if you had multiple threads accessing
a common data area.
--
Fletcher Glenn
|
|
0
|
|
|
|
Reply
|
Fletcher
|
6/17/2005 11:07:51 PM
|
|
In article <bJIse.3606$NU5.2026@newssvr13.news.prodigy.com>,
Fletcher Glenn <fletcher@removethisfoglight.com> wrote:
> kvc wrote:
> > I have an access backend with a 1:M parent-child relationship. I need
> > to find a way to create a new record in Infopath.
> >
> > Currently, I can only create a new record by "saving" the parent table,
> > then "query" for that record saved, which then populates back into the
> > parent table, so that I can finally enter data into my children tables.
> >
> > My primary key is not bouncing back into the parent table.
> >
> > I want to be able to enter data in the parent and children tables, then
> > press "submit" to save (all in one step).
> >
> Parent and child processes have their own data spaces.
I don't think he's talking about parent and child processes, he seems to
be talking about data in a hierarchical database.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
|
|
0
|
|
|
|
Reply
|
Barry
|
6/18/2005 12:22:17 AM
|
|
In article <barmar-9A18BA.20221717062005@comcast.dca.giganews.com>,
Barry Margolin <barmar@alum.mit.edu> wrote:
....
>I don't think he's talking about parent and child processes, he seems to
>be talking about data in a hierarchical database.
And all this time I thought he was talking about the relationships between
people and their offspring.
|
|
0
|
|
|
|
Reply
|
gazelle
|
6/18/2005 3:48:51 AM
|
|
|
3 Replies
390 Views
(page loaded in 0.147 seconds)
|
|
|
|
|
|
|
|
|