PDA

View Full Version : Example questions



Bob Worsley
22-Jun-2007, 03:06 PM
In the contact management example I've noticed two things that don't seem to
be working.

1) The property pbClearAfterSave is set to false in the .wo yet the screen
still clears after saving.

2) If you make a change to the child file Calls, in the notes field, lower
right, the save does not take - any changes are not saved. Since the
main_dd of the wo is the parent, or contacts file, what is the preferred
method of saving a non-table child record? In this case the notes? I have
a similar layout I'm working on and have the same problem.

Why do these questions always seem to come up on a Friday afternoon when no
one is around to answer them?

Bob

Bob Worsley
22-Jun-2007, 05:18 PM
True to form I answered #1 shortly after asking it. Setting
vdfAutoClearDeoState in the form fixed that problem. However, what is
pbClearAfterSave in the .wo for, just a leftover from the old way of doing
things?

Related to question 2, I've got my child file on a tab (and not a grid), and
for some reason all of the fields are readonly and I can't figure out why.
I can find and display the data, but can't enter or edit the fields, though
date fields will populate from the popup calendar. I've spent some time
trying to find a readonly or displayonly property that might be set but
haven't seen any.
Bob

"Bob Worsley" <bworsley@comcast.net> wrote in message
news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
> In the contact management example I've noticed two things that don't seem
to
> be working.
>
> 1) The property pbClearAfterSave is set to false in the .wo yet the screen
> still clears after saving.
>
> 2) If you make a change to the child file Calls, in the notes field, lower
> right, the save does not take - any changes are not saved. Since the
> main_dd of the wo is the parent, or contacts file, what is the preferred
> method of saving a non-table child record? In this case the notes? I
have
> a similar layout I'm working on and have the same problem.
>
> Why do these questions always seem to come up on a Friday afternoon when
no
> one is around to answer them?
>
> Bob
>
>
>
>

Bob Worsley
24-Jun-2007, 07:51 AM
I did a little more work on this program. As usual I thought this simple
two file form would be a relatively easy exercise but of course it's turned
into a number of frustrations. The layout is:

Customer
|
Invoice

with a single numeric ID relationship between them. As stated above the
customer is on the top, Invoice is on one tab, and customer.notes is on a
second tab. All works except for the invoice, I cannot access any of the
data fields, all except for the ID are readonly. The main_dd in the .wo is
Customer.

So I tried changing the main_DD to the invoice file. Changed the vdfServer
in the asp to invoice. This opened up the invoice file to entry, but did
two things to the customer. a) Both fields that were finding fields then
insisted on a find required when I attempted to add a new record and tab to
another field. b) All non-finding fields were readonly, just like the
invoice fields before.

I put the program back to the original main_dd and as a test I removed the
tab and put both files on the main screen. No difference, still can't
access the invoice fields. I thought maybe I needed a "vdfServerTable"
statement for the invoice file but after trying it in a few places found no
difference.

Very bizarre. Is there any new documentation other than the one "reference"
doc?
Bob


"Bob Worsley" <bworsley@comcast.net> wrote in message
news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
> True to form I answered #1 shortly after asking it. Setting
> vdfAutoClearDeoState in the form fixed that problem. However, what is
> pbClearAfterSave in the .wo for, just a leftover from the old way of doing
> things?
>
> Related to question 2, I've got my child file on a tab (and not a grid),
and
> for some reason all of the fields are readonly and I can't figure out why.
> I can find and display the data, but can't enter or edit the fields,
though
> date fields will populate from the popup calendar. I've spent some time
> trying to find a readonly or displayonly property that might be set but
> haven't seen any.
> Bob
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
> > In the contact management example I've noticed two things that don't
seem
> to
> > be working.
> >
> > 1) The property pbClearAfterSave is set to false in the .wo yet the
screen
> > still clears after saving.
> >
> > 2) If you make a change to the child file Calls, in the notes field,
lower
> > right, the save does not take - any changes are not saved. Since the
> > main_dd of the wo is the parent, or contacts file, what is the preferred
> > method of saving a non-table child record? In this case the notes? I
> have
> > a similar layout I'm working on and have the same problem.
> >
> > Why do these questions always seem to come up on a Friday afternoon when
> no
> > one is around to answer them?
> >
> > Bob
> >
> >
> >
> >
>
>
>
>

Edwin van der Velden
25-Jun-2007, 02:12 AM
I guess it probably is some left over, they're pretty standard properties
which might even have been added automatically.
I guess it might be possible to make settings efault to the properties set
in the WO, on the other hand this would shift control over things from one
place to two places and might cause more confusing then when set on only one
place for the ajax application. I'll throw it in our next library discussion
here just in case though :p

-Edwin

"Bob Worsley" <bworsley@comcast.net> wrote in message
news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
> True to form I answered #1 shortly after asking it. Setting
> vdfAutoClearDeoState in the form fixed that problem. However, what is
> pbClearAfterSave in the .wo for, just a leftover from the old way of doing
> things?
>
> Related to question 2, I've got my child file on a tab (and not a grid),
> and
> for some reason all of the fields are readonly and I can't figure out why.
> I can find and display the data, but can't enter or edit the fields,
> though
> date fields will populate from the popup calendar. I've spent some time
> trying to find a readonly or displayonly property that might be set but
> haven't seen any.
> Bob
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
>> In the contact management example I've noticed two things that don't seem
> to
>> be working.
>>
>> 1) The property pbClearAfterSave is set to false in the .wo yet the
>> screen
>> still clears after saving.
>>
>> 2) If you make a change to the child file Calls, in the notes field,
>> lower
>> right, the save does not take - any changes are not saved. Since the
>> main_dd of the wo is the parent, or contacts file, what is the preferred
>> method of saving a non-table child record? In this case the notes? I
> have
>> a similar layout I'm working on and have the same problem.
>>
>> Why do these questions always seem to come up on a Friday afternoon when
> no
>> one is around to answer them?
>>
>> Bob
>>
>>
>>
>>
>
>
>

Vincent Oorsprong
25-Jun-2007, 02:37 AM
Bob,

Is 22:04 your Friday AFTERNOON? Technically it is of course but you should
be sitting at home, on the terrace or for the fireplace, smiling and knowing
you had a good week.

--
Regards,
Vincent Oorsprong
Data Access Europe B.V.
http://www.dataaccess.nl

Edwin van der Velden
25-Jun-2007, 02:56 AM
The readonly field issue is occuring for other people as well, so I'll be
looking into that soon. If anyone has any ideas why this might occur I'd
gladly hear your opinions :-)

For now you might be able to add the input directly as <input... /> leaving
out the readonly and possible tabindex attributes instead of calling the
DDValue function which generates it as readonly.


-Edwin


"Bob Worsley" <bworsley@comcast.net> wrote in message
news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
>I did a little more work on this program. As usual I thought this simple
> two file form would be a relatively easy exercise but of course it's
> turned
> into a number of frustrations. The layout is:
>
> Customer
> |
> Invoice
>
> with a single numeric ID relationship between them. As stated above the
> customer is on the top, Invoice is on one tab, and customer.notes is on a
> second tab. All works except for the invoice, I cannot access any of the
> data fields, all except for the ID are readonly. The main_dd in the .wo
> is
> Customer.
>
> So I tried changing the main_DD to the invoice file. Changed the
> vdfServer
> in the asp to invoice. This opened up the invoice file to entry, but did
> two things to the customer. a) Both fields that were finding fields then
> insisted on a find required when I attempted to add a new record and tab
> to
> another field. b) All non-finding fields were readonly, just like the
> invoice fields before.
>
> I put the program back to the original main_dd and as a test I removed the
> tab and put both files on the main screen. No difference, still can't
> access the invoice fields. I thought maybe I needed a "vdfServerTable"
> statement for the invoice file but after trying it in a few places found
> no
> difference.
>
> Very bizarre. Is there any new documentation other than the one
> "reference"
> doc?
> Bob
>
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
>> True to form I answered #1 shortly after asking it. Setting
>> vdfAutoClearDeoState in the form fixed that problem. However, what is
>> pbClearAfterSave in the .wo for, just a leftover from the old way of
>> doing
>> things?
>>
>> Related to question 2, I've got my child file on a tab (and not a grid),
> and
>> for some reason all of the fields are readonly and I can't figure out
>> why.
>> I can find and display the data, but can't enter or edit the fields,
> though
>> date fields will populate from the popup calendar. I've spent some time
>> trying to find a readonly or displayonly property that might be set but
>> haven't seen any.
>> Bob
>>
>> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
>> > In the contact management example I've noticed two things that don't
> seem
>> to
>> > be working.
>> >
>> > 1) The property pbClearAfterSave is set to false in the .wo yet the
> screen
>> > still clears after saving.
>> >
>> > 2) If you make a change to the child file Calls, in the notes field,
> lower
>> > right, the save does not take - any changes are not saved. Since the
>> > main_dd of the wo is the parent, or contacts file, what is the
>> > preferred
>> > method of saving a non-table child record? In this case the notes? I
>> have
>> > a similar layout I'm working on and have the same problem.
>> >
>> > Why do these questions always seem to come up on a Friday afternoon
>> > when
>> no
>> > one is around to answer them?
>> >
>> > Bob
>> >
>> >
>> >
>> >
>>
>>
>>
>>
>
>
>

Bob Worsley
25-Jun-2007, 06:21 AM
Those of us that work multiple jobs, a day job and perhaps a side job or two
in order to keep us in the lifestyles to which our wives have become
accustomed, work long hours...
Bob

"Vincent Oorsprong" <vincent.oorsprong@reply.at.newsgroup.nl> wrote in
message news:2paiPvvtHHA.3972@dacmail.dataaccess.com...
> Bob,
>
> Is 22:04 your Friday AFTERNOON? Technically it is of course but you should
> be sitting at home, on the terrace or for the fireplace, smiling and
knowing
> you had a good week.
>
> --
> Regards,
> Vincent Oorsprong
> Data Access Europe B.V.
> http://www.dataaccess.nl
>
>
>

Bob Worsley
25-Jun-2007, 06:56 AM
Changing to input style controls did eliminate the readonly problem, but you
didn't address the question of saving. Where the parent is the main_DD, how
do I get the child to save? Simply having the cursor in one of the child
fields and hitting save doesn't do it. Choices might be to change the
main_DD to the child or write some manual code to do the saving... what's
recommended?
Bob

"Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in message
news:HyI$O5vtHHA.5076@dacmail.dataaccess.com...
> The readonly field issue is occuring for other people as well, so I'll be
> looking into that soon. If anyone has any ideas why this might occur I'd
> gladly hear your opinions :-)
>
> For now you might be able to add the input directly as <input... />
leaving
> out the readonly and possible tabindex attributes instead of calling the
> DDValue function which generates it as readonly.
>
>
> -Edwin
>
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
> >I did a little more work on this program. As usual I thought this simple
> > two file form would be a relatively easy exercise but of course it's
> > turned
> > into a number of frustrations. The layout is:
> >
> > Customer
> > |
> > Invoice
> >
> > with a single numeric ID relationship between them. As stated above the
> > customer is on the top, Invoice is on one tab, and customer.notes is on
a
> > second tab. All works except for the invoice, I cannot access any of
the
> > data fields, all except for the ID are readonly. The main_dd in the .wo
> > is
> > Customer.
> >
> > So I tried changing the main_DD to the invoice file. Changed the
> > vdfServer
> > in the asp to invoice. This opened up the invoice file to entry, but
did
> > two things to the customer. a) Both fields that were finding fields
then
> > insisted on a find required when I attempted to add a new record and tab
> > to
> > another field. b) All non-finding fields were readonly, just like the
> > invoice fields before.
> >
> > I put the program back to the original main_dd and as a test I removed
the
> > tab and put both files on the main screen. No difference, still can't
> > access the invoice fields. I thought maybe I needed a "vdfServerTable"
> > statement for the invoice file but after trying it in a few places found
> > no
> > difference.
> >
> > Very bizarre. Is there any new documentation other than the one
> > "reference"
> > doc?
> > Bob
> >
> >
> > "Bob Worsley" <bworsley@comcast.net> wrote in message
> > news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
> >> True to form I answered #1 shortly after asking it. Setting
> >> vdfAutoClearDeoState in the form fixed that problem. However, what is
> >> pbClearAfterSave in the .wo for, just a leftover from the old way of
> >> doing
> >> things?
> >>
> >> Related to question 2, I've got my child file on a tab (and not a
grid),
> > and
> >> for some reason all of the fields are readonly and I can't figure out
> >> why.
> >> I can find and display the data, but can't enter or edit the fields,
> > though
> >> date fields will populate from the popup calendar. I've spent some
time
> >> trying to find a readonly or displayonly property that might be set but
> >> haven't seen any.
> >> Bob
> >>
> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
> >> > In the contact management example I've noticed two things that don't
> > seem
> >> to
> >> > be working.
> >> >
> >> > 1) The property pbClearAfterSave is set to false in the .wo yet the
> > screen
> >> > still clears after saving.
> >> >
> >> > 2) If you make a change to the child file Calls, in the notes field,
> > lower
> >> > right, the save does not take - any changes are not saved. Since the
> >> > main_dd of the wo is the parent, or contacts file, what is the
> >> > preferred
> >> > method of saving a non-table child record? In this case the notes?
I
> >> have
> >> > a similar layout I'm working on and have the same problem.
> >> >
> >> > Why do these questions always seem to come up on a Friday afternoon
> >> > when
> >> no
> >> > one is around to answer them?
> >> >
> >> > Bob
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >>
> >
> >
> >
>
>
>

Edwin van der Velden
25-Jun-2007, 08:28 AM
My mistake, I read the whole thing as being a problem caused by trying to
get around the readonly thing and that it wasn't a problem if you could just
have non-readonly fields. Guess I misread that.

My suggestion would always be, if possible don't write any manual code. If
changing the main dd to the child is ok for the page, and does not mess up
any of the find actions/etc you should do this imo. If however it is for
some reason not possible there's is little choice but to additional code to
save.

-Edwin


"Bob Worsley" <bworsley@comcast.net> wrote in message
news:dmbWd%23xtHHA.5828@dacmail.dataaccess.com...
> Changing to input style controls did eliminate the readonly problem, but
> you
> didn't address the question of saving. Where the parent is the main_DD,
> how
> do I get the child to save? Simply having the cursor in one of the child
> fields and hitting save doesn't do it. Choices might be to change the
> main_DD to the child or write some manual code to do the saving... what's
> recommended?
> Bob
>
> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> message
> news:HyI$O5vtHHA.5076@dacmail.dataaccess.com...
>> The readonly field issue is occuring for other people as well, so I'll be
>> looking into that soon. If anyone has any ideas why this might occur I'd
>> gladly hear your opinions :-)
>>
>> For now you might be able to add the input directly as <input... />
> leaving
>> out the readonly and possible tabindex attributes instead of calling the
>> DDValue function which generates it as readonly.
>>
>>
>> -Edwin
>>
>>
>> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
>> >I did a little more work on this program. As usual I thought this
>> >simple
>> > two file form would be a relatively easy exercise but of course it's
>> > turned
>> > into a number of frustrations. The layout is:
>> >
>> > Customer
>> > |
>> > Invoice
>> >
>> > with a single numeric ID relationship between them. As stated above
>> > the
>> > customer is on the top, Invoice is on one tab, and customer.notes is on
> a
>> > second tab. All works except for the invoice, I cannot access any of
> the
>> > data fields, all except for the ID are readonly. The main_dd in the
>> > .wo
>> > is
>> > Customer.
>> >
>> > So I tried changing the main_DD to the invoice file. Changed the
>> > vdfServer
>> > in the asp to invoice. This opened up the invoice file to entry, but
> did
>> > two things to the customer. a) Both fields that were finding fields
> then
>> > insisted on a find required when I attempted to add a new record and
>> > tab
>> > to
>> > another field. b) All non-finding fields were readonly, just like the
>> > invoice fields before.
>> >
>> > I put the program back to the original main_dd and as a test I removed
> the
>> > tab and put both files on the main screen. No difference, still can't
>> > access the invoice fields. I thought maybe I needed a "vdfServerTable"
>> > statement for the invoice file but after trying it in a few places
>> > found
>> > no
>> > difference.
>> >
>> > Very bizarre. Is there any new documentation other than the one
>> > "reference"
>> > doc?
>> > Bob
>> >
>> >
>> > "Bob Worsley" <bworsley@comcast.net> wrote in message
>> > news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
>> >> True to form I answered #1 shortly after asking it. Setting
>> >> vdfAutoClearDeoState in the form fixed that problem. However, what is
>> >> pbClearAfterSave in the .wo for, just a leftover from the old way of
>> >> doing
>> >> things?
>> >>
>> >> Related to question 2, I've got my child file on a tab (and not a
> grid),
>> > and
>> >> for some reason all of the fields are readonly and I can't figure out
>> >> why.
>> >> I can find and display the data, but can't enter or edit the fields,
>> > though
>> >> date fields will populate from the popup calendar. I've spent some
> time
>> >> trying to find a readonly or displayonly property that might be set
>> >> but
>> >> haven't seen any.
>> >> Bob
>> >>
>> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
>> >> > In the contact management example I've noticed two things that don't
>> > seem
>> >> to
>> >> > be working.
>> >> >
>> >> > 1) The property pbClearAfterSave is set to false in the .wo yet the
>> > screen
>> >> > still clears after saving.
>> >> >
>> >> > 2) If you make a change to the child file Calls, in the notes field,
>> > lower
>> >> > right, the save does not take - any changes are not saved. Since
>> >> > the
>> >> > main_dd of the wo is the parent, or contacts file, what is the
>> >> > preferred
>> >> > method of saving a non-table child record? In this case the notes?
> I
>> >> have
>> >> > a similar layout I'm working on and have the same problem.
>> >> >
>> >> > Why do these questions always seem to come up on a Friday afternoon
>> >> > when
>> >> no
>> >> > one is around to answer them?
>> >> >
>> >> > Bob
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> >
>>
>>
>>
>
>
>

Bob Worsley
25-Jun-2007, 08:34 AM
Agreed, as little extra code as possible is always good! The only question
is whether making the child the main_DD would mean I'd always have to have a
child record in order to save, and that I haven't determined as yet. The
way the users will use this is to enter either parent, both, or find a
parent and then add a child. In other words all ways. So, it might mean
extra code...
Bob

"Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in message
news:gDDowyytHHA.5076@dacmail.dataaccess.com...
> My mistake, I read the whole thing as being a problem caused by trying to
> get around the readonly thing and that it wasn't a problem if you could
just
> have non-readonly fields. Guess I misread that.
>
> My suggestion would always be, if possible don't write any manual code. If
> changing the main dd to the child is ok for the page, and does not mess up
> any of the find actions/etc you should do this imo. If however it is for
> some reason not possible there's is little choice but to additional code
to
> save.
>
> -Edwin
>
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:dmbWd%23xtHHA.5828@dacmail.dataaccess.com...
> > Changing to input style controls did eliminate the readonly problem, but
> > you
> > didn't address the question of saving. Where the parent is the main_DD,
> > how
> > do I get the child to save? Simply having the cursor in one of the
child
> > fields and hitting save doesn't do it. Choices might be to change the
> > main_DD to the child or write some manual code to do the saving...
what's
> > recommended?
> > Bob
> >
> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> > message
> > news:HyI$O5vtHHA.5076@dacmail.dataaccess.com...
> >> The readonly field issue is occuring for other people as well, so I'll
be
> >> looking into that soon. If anyone has any ideas why this might occur
I'd
> >> gladly hear your opinions :-)
> >>
> >> For now you might be able to add the input directly as <input... />
> > leaving
> >> out the readonly and possible tabindex attributes instead of calling
the
> >> DDValue function which generates it as readonly.
> >>
> >>
> >> -Edwin
> >>
> >>
> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
> >> >I did a little more work on this program. As usual I thought this
> >> >simple
> >> > two file form would be a relatively easy exercise but of course it's
> >> > turned
> >> > into a number of frustrations. The layout is:
> >> >
> >> > Customer
> >> > |
> >> > Invoice
> >> >
> >> > with a single numeric ID relationship between them. As stated above
> >> > the
> >> > customer is on the top, Invoice is on one tab, and customer.notes is
on
> > a
> >> > second tab. All works except for the invoice, I cannot access any of
> > the
> >> > data fields, all except for the ID are readonly. The main_dd in the
> >> > .wo
> >> > is
> >> > Customer.
> >> >
> >> > So I tried changing the main_DD to the invoice file. Changed the
> >> > vdfServer
> >> > in the asp to invoice. This opened up the invoice file to entry, but
> > did
> >> > two things to the customer. a) Both fields that were finding fields
> > then
> >> > insisted on a find required when I attempted to add a new record and
> >> > tab
> >> > to
> >> > another field. b) All non-finding fields were readonly, just like
the
> >> > invoice fields before.
> >> >
> >> > I put the program back to the original main_dd and as a test I
removed
> > the
> >> > tab and put both files on the main screen. No difference, still
can't
> >> > access the invoice fields. I thought maybe I needed a
"vdfServerTable"
> >> > statement for the invoice file but after trying it in a few places
> >> > found
> >> > no
> >> > difference.
> >> >
> >> > Very bizarre. Is there any new documentation other than the one
> >> > "reference"
> >> > doc?
> >> > Bob
> >> >
> >> >
> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> > news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
> >> >> True to form I answered #1 shortly after asking it. Setting
> >> >> vdfAutoClearDeoState in the form fixed that problem. However, what
is
> >> >> pbClearAfterSave in the .wo for, just a leftover from the old way of
> >> >> doing
> >> >> things?
> >> >>
> >> >> Related to question 2, I've got my child file on a tab (and not a
> > grid),
> >> > and
> >> >> for some reason all of the fields are readonly and I can't figure
out
> >> >> why.
> >> >> I can find and display the data, but can't enter or edit the fields,
> >> > though
> >> >> date fields will populate from the popup calendar. I've spent some
> > time
> >> >> trying to find a readonly or displayonly property that might be set
> >> >> but
> >> >> haven't seen any.
> >> >> Bob
> >> >>
> >> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> >> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
> >> >> > In the contact management example I've noticed two things that
don't
> >> > seem
> >> >> to
> >> >> > be working.
> >> >> >
> >> >> > 1) The property pbClearAfterSave is set to false in the .wo yet
the
> >> > screen
> >> >> > still clears after saving.
> >> >> >
> >> >> > 2) If you make a change to the child file Calls, in the notes
field,
> >> > lower
> >> >> > right, the save does not take - any changes are not saved. Since
> >> >> > the
> >> >> > main_dd of the wo is the parent, or contacts file, what is the
> >> >> > preferred
> >> >> > method of saving a non-table child record? In this case the
notes?
> > I
> >> >> have
> >> >> > a similar layout I'm working on and have the same problem.
> >> >> >
> >> >> > Why do these questions always seem to come up on a Friday
afternoon
> >> >> > when
> >> >> no
> >> >> > one is around to answer them?
> >> >> >
> >> >> > Bob
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >
> >
> >
>
>
>

Edwin van der Velden
25-Jun-2007, 09:07 AM
I was thinking how the order entry exxample did that with child records, but
that of course is a child in a grid and grids are obviously handled
differently.
I guess two options that would be possible is to change the data structure
so the child-parent relation is reversed which most likely is not possible,
or to add in in a grid, but by the sound of it it's a 1:1 relation so that
would be a bit overkill.

My guess is that if you leave the child record empty it will either not save
anything at all or create new empty records, depending on you data structure
and validation.

-Edwin



"Bob Worsley" <bworsley@comcast.net> wrote in message
news:CZhlq1ytHHA.5076@dacmail.dataaccess.com...
> Agreed, as little extra code as possible is always good! The only
> question
> is whether making the child the main_DD would mean I'd always have to have
> a
> child record in order to save, and that I haven't determined as yet. The
> way the users will use this is to enter either parent, both, or find a
> parent and then add a child. In other words all ways. So, it might mean
> extra code...
> Bob
>
> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> message
> news:gDDowyytHHA.5076@dacmail.dataaccess.com...
>> My mistake, I read the whole thing as being a problem caused by trying to
>> get around the readonly thing and that it wasn't a problem if you could
> just
>> have non-readonly fields. Guess I misread that.
>>
>> My suggestion would always be, if possible don't write any manual code.
>> If
>> changing the main dd to the child is ok for the page, and does not mess
>> up
>> any of the find actions/etc you should do this imo. If however it is for
>> some reason not possible there's is little choice but to additional code
> to
>> save.
>>
>> -Edwin
>>
>>
>> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> news:dmbWd%23xtHHA.5828@dacmail.dataaccess.com...
>> > Changing to input style controls did eliminate the readonly problem,
>> > but
>> > you
>> > didn't address the question of saving. Where the parent is the
>> > main_DD,
>> > how
>> > do I get the child to save? Simply having the cursor in one of the
> child
>> > fields and hitting save doesn't do it. Choices might be to change the
>> > main_DD to the child or write some manual code to do the saving...
> what's
>> > recommended?
>> > Bob
>> >
>> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
>> > message
>> > news:HyI$O5vtHHA.5076@dacmail.dataaccess.com...
>> >> The readonly field issue is occuring for other people as well, so I'll
> be
>> >> looking into that soon. If anyone has any ideas why this might occur
> I'd
>> >> gladly hear your opinions :-)
>> >>
>> >> For now you might be able to add the input directly as <input... />
>> > leaving
>> >> out the readonly and possible tabindex attributes instead of calling
> the
>> >> DDValue function which generates it as readonly.
>> >>
>> >>
>> >> -Edwin
>> >>
>> >>
>> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >> news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
>> >> >I did a little more work on this program. As usual I thought this
>> >> >simple
>> >> > two file form would be a relatively easy exercise but of course it's
>> >> > turned
>> >> > into a number of frustrations. The layout is:
>> >> >
>> >> > Customer
>> >> > |
>> >> > Invoice
>> >> >
>> >> > with a single numeric ID relationship between them. As stated above
>> >> > the
>> >> > customer is on the top, Invoice is on one tab, and customer.notes is
> on
>> > a
>> >> > second tab. All works except for the invoice, I cannot access any
>> >> > of
>> > the
>> >> > data fields, all except for the ID are readonly. The main_dd in the
>> >> > .wo
>> >> > is
>> >> > Customer.
>> >> >
>> >> > So I tried changing the main_DD to the invoice file. Changed the
>> >> > vdfServer
>> >> > in the asp to invoice. This opened up the invoice file to entry,
>> >> > but
>> > did
>> >> > two things to the customer. a) Both fields that were finding fields
>> > then
>> >> > insisted on a find required when I attempted to add a new record and
>> >> > tab
>> >> > to
>> >> > another field. b) All non-finding fields were readonly, just like
> the
>> >> > invoice fields before.
>> >> >
>> >> > I put the program back to the original main_dd and as a test I
> removed
>> > the
>> >> > tab and put both files on the main screen. No difference, still
> can't
>> >> > access the invoice fields. I thought maybe I needed a
> "vdfServerTable"
>> >> > statement for the invoice file but after trying it in a few places
>> >> > found
>> >> > no
>> >> > difference.
>> >> >
>> >> > Very bizarre. Is there any new documentation other than the one
>> >> > "reference"
>> >> > doc?
>> >> > Bob
>> >> >
>> >> >
>> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >> > news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
>> >> >> True to form I answered #1 shortly after asking it. Setting
>> >> >> vdfAutoClearDeoState in the form fixed that problem. However, what
> is
>> >> >> pbClearAfterSave in the .wo for, just a leftover from the old way
>> >> >> of
>> >> >> doing
>> >> >> things?
>> >> >>
>> >> >> Related to question 2, I've got my child file on a tab (and not a
>> > grid),
>> >> > and
>> >> >> for some reason all of the fields are readonly and I can't figure
> out
>> >> >> why.
>> >> >> I can find and display the data, but can't enter or edit the
>> >> >> fields,
>> >> > though
>> >> >> date fields will populate from the popup calendar. I've spent some
>> > time
>> >> >> trying to find a readonly or displayonly property that might be set
>> >> >> but
>> >> >> haven't seen any.
>> >> >> Bob
>> >> >>
>> >> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >> >> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
>> >> >> > In the contact management example I've noticed two things that
> don't
>> >> > seem
>> >> >> to
>> >> >> > be working.
>> >> >> >
>> >> >> > 1) The property pbClearAfterSave is set to false in the .wo yet
> the
>> >> > screen
>> >> >> > still clears after saving.
>> >> >> >
>> >> >> > 2) If you make a change to the child file Calls, in the notes
> field,
>> >> > lower
>> >> >> > right, the save does not take - any changes are not saved. Since
>> >> >> > the
>> >> >> > main_dd of the wo is the parent, or contacts file, what is the
>> >> >> > preferred
>> >> >> > method of saving a non-table child record? In this case the
> notes?
>> > I
>> >> >> have
>> >> >> > a similar layout I'm working on and have the same problem.
>> >> >> >
>> >> >> > Why do these questions always seem to come up on a Friday
> afternoon
>> >> >> > when
>> >> >> no
>> >> >> > one is around to answer them?
>> >> >> >
>> >> >> > Bob
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >
>> >
>> >
>>
>>
>>
>
>
>

Edwin van der Velden
25-Jun-2007, 09:10 AM
Or not really a 1:1 relation but more a 1:0-1 relation, but a max of 1 child
record for each parent at least which was my point in the grid being a bit
overkill.

-Edwin


"Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in message
news:TgoG7IztHHA.5076@dacmail.dataaccess.com...
>I was thinking how the order entry exxample did that with child records,
>but that of course is a child in a grid and grids are obviously handled
>differently.
> I guess two options that would be possible is to change the data structure
> so the child-parent relation is reversed which most likely is not
> possible, or to add in in a grid, but by the sound of it it's a 1:1
> relation so that would be a bit overkill.
>
> My guess is that if you leave the child record empty it will either not
> save anything at all or create new empty records, depending on you data
> structure and validation.
>
> -Edwin
>
>
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:CZhlq1ytHHA.5076@dacmail.dataaccess.com...
>> Agreed, as little extra code as possible is always good! The only
>> question
>> is whether making the child the main_DD would mean I'd always have to
>> have a
>> child record in order to save, and that I haven't determined as yet. The
>> way the users will use this is to enter either parent, both, or find a
>> parent and then add a child. In other words all ways. So, it might mean
>> extra code...
>> Bob
>>
>> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
>> message
>> news:gDDowyytHHA.5076@dacmail.dataaccess.com...
>>> My mistake, I read the whole thing as being a problem caused by trying
>>> to
>>> get around the readonly thing and that it wasn't a problem if you could
>> just
>>> have non-readonly fields. Guess I misread that.
>>>
>>> My suggestion would always be, if possible don't write any manual code.
>>> If
>>> changing the main dd to the child is ok for the page, and does not mess
>>> up
>>> any of the find actions/etc you should do this imo. If however it is for
>>> some reason not possible there's is little choice but to additional code
>> to
>>> save.
>>>
>>> -Edwin
>>>
>>>
>>> "Bob Worsley" <bworsley@comcast.net> wrote in message
>>> news:dmbWd%23xtHHA.5828@dacmail.dataaccess.com...
>>> > Changing to input style controls did eliminate the readonly problem,
>>> > but
>>> > you
>>> > didn't address the question of saving. Where the parent is the
>>> > main_DD,
>>> > how
>>> > do I get the child to save? Simply having the cursor in one of the
>> child
>>> > fields and hitting save doesn't do it. Choices might be to change the
>>> > main_DD to the child or write some manual code to do the saving...
>> what's
>>> > recommended?
>>> > Bob
>>> >
>>> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
>>> > message
>>> > news:HyI$O5vtHHA.5076@dacmail.dataaccess.com...
>>> >> The readonly field issue is occuring for other people as well, so
>>> >> I'll
>> be
>>> >> looking into that soon. If anyone has any ideas why this might occur
>> I'd
>>> >> gladly hear your opinions :-)
>>> >>
>>> >> For now you might be able to add the input directly as <input... />
>>> > leaving
>>> >> out the readonly and possible tabindex attributes instead of calling
>> the
>>> >> DDValue function which generates it as readonly.
>>> >>
>>> >>
>>> >> -Edwin
>>> >>
>>> >>
>>> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
>>> >> news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
>>> >> >I did a little more work on this program. As usual I thought this
>>> >> >simple
>>> >> > two file form would be a relatively easy exercise but of course
>>> >> > it's
>>> >> > turned
>>> >> > into a number of frustrations. The layout is:
>>> >> >
>>> >> > Customer
>>> >> > |
>>> >> > Invoice
>>> >> >
>>> >> > with a single numeric ID relationship between them. As stated
>>> >> > above
>>> >> > the
>>> >> > customer is on the top, Invoice is on one tab, and customer.notes
>>> >> > is
>> on
>>> > a
>>> >> > second tab. All works except for the invoice, I cannot access any
>>> >> > of
>>> > the
>>> >> > data fields, all except for the ID are readonly. The main_dd in
>>> >> > the
>>> >> > .wo
>>> >> > is
>>> >> > Customer.
>>> >> >
>>> >> > So I tried changing the main_DD to the invoice file. Changed the
>>> >> > vdfServer
>>> >> > in the asp to invoice. This opened up the invoice file to entry,
>>> >> > but
>>> > did
>>> >> > two things to the customer. a) Both fields that were finding
>>> >> > fields
>>> > then
>>> >> > insisted on a find required when I attempted to add a new record
>>> >> > and
>>> >> > tab
>>> >> > to
>>> >> > another field. b) All non-finding fields were readonly, just like
>> the
>>> >> > invoice fields before.
>>> >> >
>>> >> > I put the program back to the original main_dd and as a test I
>> removed
>>> > the
>>> >> > tab and put both files on the main screen. No difference, still
>> can't
>>> >> > access the invoice fields. I thought maybe I needed a
>> "vdfServerTable"
>>> >> > statement for the invoice file but after trying it in a few places
>>> >> > found
>>> >> > no
>>> >> > difference.
>>> >> >
>>> >> > Very bizarre. Is there any new documentation other than the one
>>> >> > "reference"
>>> >> > doc?
>>> >> > Bob
>>> >> >
>>> >> >
>>> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
>>> >> > news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
>>> >> >> True to form I answered #1 shortly after asking it. Setting
>>> >> >> vdfAutoClearDeoState in the form fixed that problem. However,
>>> >> >> what
>> is
>>> >> >> pbClearAfterSave in the .wo for, just a leftover from the old way
>>> >> >> of
>>> >> >> doing
>>> >> >> things?
>>> >> >>
>>> >> >> Related to question 2, I've got my child file on a tab (and not a
>>> > grid),
>>> >> > and
>>> >> >> for some reason all of the fields are readonly and I can't figure
>> out
>>> >> >> why.
>>> >> >> I can find and display the data, but can't enter or edit the
>>> >> >> fields,
>>> >> > though
>>> >> >> date fields will populate from the popup calendar. I've spent
>>> >> >> some
>>> > time
>>> >> >> trying to find a readonly or displayonly property that might be
>>> >> >> set
>>> >> >> but
>>> >> >> haven't seen any.
>>> >> >> Bob
>>> >> >>
>>> >> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
>>> >> >> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
>>> >> >> > In the contact management example I've noticed two things that
>> don't
>>> >> > seem
>>> >> >> to
>>> >> >> > be working.
>>> >> >> >
>>> >> >> > 1) The property pbClearAfterSave is set to false in the .wo yet
>> the
>>> >> > screen
>>> >> >> > still clears after saving.
>>> >> >> >
>>> >> >> > 2) If you make a change to the child file Calls, in the notes
>> field,
>>> >> > lower
>>> >> >> > right, the save does not take - any changes are not saved.
>>> >> >> > Since
>>> >> >> > the
>>> >> >> > main_dd of the wo is the parent, or contacts file, what is the
>>> >> >> > preferred
>>> >> >> > method of saving a non-table child record? In this case the
>> notes?
>>> > I
>>> >> >> have
>>> >> >> > a similar layout I'm working on and have the same problem.
>>> >> >> >
>>> >> >> > Why do these questions always seem to come up on a Friday
>> afternoon
>>> >> >> > when
>>> >> >> no
>>> >> >> > one is around to answer them?
>>> >> >> >
>>> >> >> > Bob
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>
>>
>>
>
>

Bob Worsley
25-Jun-2007, 09:20 AM
Actually this is not a 1:1 situation, and a grid would theoretically work.
The reason I didn't use a grid is that the data record consists of 3 date
fields, 6 text fields, and the image path. They won't all fit on a single
grid line. So unless I'm able to use multiple lines in the grid for one
record, or use a popup for some of the fields, which I've done before, I
have to do it this way -- with single record entry.
Bob

"Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in message
news:UPVahKztHHA.5828@dacmail.dataaccess.com...
> Or not really a 1:1 relation but more a 1:0-1 relation, but a max of 1
child
> record for each parent at least which was my point in the grid being a
bit
> overkill.
>
> -Edwin
>
>
> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
message
> news:TgoG7IztHHA.5076@dacmail.dataaccess.com...
> >I was thinking how the order entry exxample did that with child records,
> >but that of course is a child in a grid and grids are obviously handled
> >differently.
> > I guess two options that would be possible is to change the data
structure
> > so the child-parent relation is reversed which most likely is not
> > possible, or to add in in a grid, but by the sound of it it's a 1:1
> > relation so that would be a bit overkill.
> >
> > My guess is that if you leave the child record empty it will either not
> > save anything at all or create new empty records, depending on you data
> > structure and validation.
> >
> > -Edwin
> >
> >
> >
> > "Bob Worsley" <bworsley@comcast.net> wrote in message
> > news:CZhlq1ytHHA.5076@dacmail.dataaccess.com...
> >> Agreed, as little extra code as possible is always good! The only
> >> question
> >> is whether making the child the main_DD would mean I'd always have to
> >> have a
> >> child record in order to save, and that I haven't determined as yet.
The
> >> way the users will use this is to enter either parent, both, or find a
> >> parent and then add a child. In other words all ways. So, it might
mean
> >> extra code...
> >> Bob
> >>
> >> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> >> message
> >> news:gDDowyytHHA.5076@dacmail.dataaccess.com...
> >>> My mistake, I read the whole thing as being a problem caused by trying
> >>> to
> >>> get around the readonly thing and that it wasn't a problem if you
could
> >> just
> >>> have non-readonly fields. Guess I misread that.
> >>>
> >>> My suggestion would always be, if possible don't write any manual
code.
> >>> If
> >>> changing the main dd to the child is ok for the page, and does not
mess
> >>> up
> >>> any of the find actions/etc you should do this imo. If however it is
for
> >>> some reason not possible there's is little choice but to additional
code
> >> to
> >>> save.
> >>>
> >>> -Edwin
> >>>
> >>>
> >>> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >>> news:dmbWd%23xtHHA.5828@dacmail.dataaccess.com...
> >>> > Changing to input style controls did eliminate the readonly problem,
> >>> > but
> >>> > you
> >>> > didn't address the question of saving. Where the parent is the
> >>> > main_DD,
> >>> > how
> >>> > do I get the child to save? Simply having the cursor in one of the
> >> child
> >>> > fields and hitting save doesn't do it. Choices might be to change
the
> >>> > main_DD to the child or write some manual code to do the saving...
> >> what's
> >>> > recommended?
> >>> > Bob
> >>> >
> >>> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> >>> > message
> >>> > news:HyI$O5vtHHA.5076@dacmail.dataaccess.com...
> >>> >> The readonly field issue is occuring for other people as well, so
> >>> >> I'll
> >> be
> >>> >> looking into that soon. If anyone has any ideas why this might
occur
> >> I'd
> >>> >> gladly hear your opinions :-)
> >>> >>
> >>> >> For now you might be able to add the input directly as <input... />
> >>> > leaving
> >>> >> out the readonly and possible tabindex attributes instead of
calling
> >> the
> >>> >> DDValue function which generates it as readonly.
> >>> >>
> >>> >>
> >>> >> -Edwin
> >>> >>
> >>> >>
> >>> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >>> >> news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
> >>> >> >I did a little more work on this program. As usual I thought this
> >>> >> >simple
> >>> >> > two file form would be a relatively easy exercise but of course
> >>> >> > it's
> >>> >> > turned
> >>> >> > into a number of frustrations. The layout is:
> >>> >> >
> >>> >> > Customer
> >>> >> > |
> >>> >> > Invoice
> >>> >> >
> >>> >> > with a single numeric ID relationship between them. As stated
> >>> >> > above
> >>> >> > the
> >>> >> > customer is on the top, Invoice is on one tab, and customer.notes
> >>> >> > is
> >> on
> >>> > a
> >>> >> > second tab. All works except for the invoice, I cannot access
any
> >>> >> > of
> >>> > the
> >>> >> > data fields, all except for the ID are readonly. The main_dd in
> >>> >> > the
> >>> >> > .wo
> >>> >> > is
> >>> >> > Customer.
> >>> >> >
> >>> >> > So I tried changing the main_DD to the invoice file. Changed the
> >>> >> > vdfServer
> >>> >> > in the asp to invoice. This opened up the invoice file to entry,
> >>> >> > but
> >>> > did
> >>> >> > two things to the customer. a) Both fields that were finding
> >>> >> > fields
> >>> > then
> >>> >> > insisted on a find required when I attempted to add a new record
> >>> >> > and
> >>> >> > tab
> >>> >> > to
> >>> >> > another field. b) All non-finding fields were readonly, just
like
> >> the
> >>> >> > invoice fields before.
> >>> >> >
> >>> >> > I put the program back to the original main_dd and as a test I
> >> removed
> >>> > the
> >>> >> > tab and put both files on the main screen. No difference, still
> >> can't
> >>> >> > access the invoice fields. I thought maybe I needed a
> >> "vdfServerTable"
> >>> >> > statement for the invoice file but after trying it in a few
places
> >>> >> > found
> >>> >> > no
> >>> >> > difference.
> >>> >> >
> >>> >> > Very bizarre. Is there any new documentation other than the one
> >>> >> > "reference"
> >>> >> > doc?
> >>> >> > Bob
> >>> >> >
> >>> >> >
> >>> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
> >>> >> > news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
> >>> >> >> True to form I answered #1 shortly after asking it. Setting
> >>> >> >> vdfAutoClearDeoState in the form fixed that problem. However,
> >>> >> >> what
> >> is
> >>> >> >> pbClearAfterSave in the .wo for, just a leftover from the old
way
> >>> >> >> of
> >>> >> >> doing
> >>> >> >> things?
> >>> >> >>
> >>> >> >> Related to question 2, I've got my child file on a tab (and not
a
> >>> > grid),
> >>> >> > and
> >>> >> >> for some reason all of the fields are readonly and I can't
figure
> >> out
> >>> >> >> why.
> >>> >> >> I can find and display the data, but can't enter or edit the
> >>> >> >> fields,
> >>> >> > though
> >>> >> >> date fields will populate from the popup calendar. I've spent
> >>> >> >> some
> >>> > time
> >>> >> >> trying to find a readonly or displayonly property that might be
> >>> >> >> set
> >>> >> >> but
> >>> >> >> haven't seen any.
> >>> >> >> Bob
> >>> >> >>
> >>> >> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >>> >> >> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
> >>> >> >> > In the contact management example I've noticed two things that
> >> don't
> >>> >> > seem
> >>> >> >> to
> >>> >> >> > be working.
> >>> >> >> >
> >>> >> >> > 1) The property pbClearAfterSave is set to false in the .wo
yet
> >> the
> >>> >> > screen
> >>> >> >> > still clears after saving.
> >>> >> >> >
> >>> >> >> > 2) If you make a change to the child file Calls, in the notes
> >> field,
> >>> >> > lower
> >>> >> >> > right, the save does not take - any changes are not saved.
> >>> >> >> > Since
> >>> >> >> > the
> >>> >> >> > main_dd of the wo is the parent, or contacts file, what is the
> >>> >> >> > preferred
> >>> >> >> > method of saving a non-table child record? In this case the
> >> notes?
> >>> > I
> >>> >> >> have
> >>> >> >> > a similar layout I'm working on and have the same problem.
> >>> >> >> >
> >>> >> >> > Why do these questions always seem to come up on a Friday
> >> afternoon
> >>> >> >> > when
> >>> >> >> no
> >>> >> >> > one is around to answer them?
> >>> >> >> >
> >>> >> >> > Bob
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >
> >>> >> >>
> >>> >> >>
> >>> >> >>
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >>
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>> >
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >
> >
>
>
>

Edwin van der Velden
25-Jun-2007, 09:25 AM
I believe you can simply add a <br /> tag between two fields in a single
column in your grid. This is not actually two rows but it should look pretty
much the same.

Example:

<td><input type="text" size="35" title="Inventory Part Desription"
name="invt__description" value="" /><br />
<input type="text" size="8" readonly="readonly" title="Retail unit price"
name="Invt__unit_price" value="0" /></td>



-Edwin


"Bob Worsley" <bworsley@comcast.net> wrote in message
news:VKcYJPztHHA.5828@dacmail.dataaccess.com...
> Actually this is not a 1:1 situation, and a grid would theoretically work.
> The reason I didn't use a grid is that the data record consists of 3 date
> fields, 6 text fields, and the image path. They won't all fit on a single
> grid line. So unless I'm able to use multiple lines in the grid for one
> record, or use a popup for some of the fields, which I've done before, I
> have to do it this way -- with single record entry.
> Bob
>
> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> message
> news:UPVahKztHHA.5828@dacmail.dataaccess.com...
>> Or not really a 1:1 relation but more a 1:0-1 relation, but a max of 1
> child
>> record for each parent at least which was my point in the grid being a
> bit
>> overkill.
>>
>> -Edwin
>>
>>
>> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> message
>> news:TgoG7IztHHA.5076@dacmail.dataaccess.com...
>> >I was thinking how the order entry exxample did that with child records,
>> >but that of course is a child in a grid and grids are obviously handled
>> >differently.
>> > I guess two options that would be possible is to change the data
> structure
>> > so the child-parent relation is reversed which most likely is not
>> > possible, or to add in in a grid, but by the sound of it it's a 1:1
>> > relation so that would be a bit overkill.
>> >
>> > My guess is that if you leave the child record empty it will either not
>> > save anything at all or create new empty records, depending on you data
>> > structure and validation.
>> >
>> > -Edwin
>> >
>> >
>> >
>> > "Bob Worsley" <bworsley@comcast.net> wrote in message
>> > news:CZhlq1ytHHA.5076@dacmail.dataaccess.com...
>> >> Agreed, as little extra code as possible is always good! The only
>> >> question
>> >> is whether making the child the main_DD would mean I'd always have to
>> >> have a
>> >> child record in order to save, and that I haven't determined as yet.
> The
>> >> way the users will use this is to enter either parent, both, or find a
>> >> parent and then add a child. In other words all ways. So, it might
> mean
>> >> extra code...
>> >> Bob
>> >>
>> >> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
>> >> message
>> >> news:gDDowyytHHA.5076@dacmail.dataaccess.com...
>> >>> My mistake, I read the whole thing as being a problem caused by
>> >>> trying
>> >>> to
>> >>> get around the readonly thing and that it wasn't a problem if you
> could
>> >> just
>> >>> have non-readonly fields. Guess I misread that.
>> >>>
>> >>> My suggestion would always be, if possible don't write any manual
> code.
>> >>> If
>> >>> changing the main dd to the child is ok for the page, and does not
> mess
>> >>> up
>> >>> any of the find actions/etc you should do this imo. If however it is
> for
>> >>> some reason not possible there's is little choice but to additional
> code
>> >> to
>> >>> save.
>> >>>
>> >>> -Edwin
>> >>>
>> >>>
>> >>> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >>> news:dmbWd%23xtHHA.5828@dacmail.dataaccess.com...
>> >>> > Changing to input style controls did eliminate the readonly
>> >>> > problem,
>> >>> > but
>> >>> > you
>> >>> > didn't address the question of saving. Where the parent is the
>> >>> > main_DD,
>> >>> > how
>> >>> > do I get the child to save? Simply having the cursor in one of the
>> >> child
>> >>> > fields and hitting save doesn't do it. Choices might be to change
> the
>> >>> > main_DD to the child or write some manual code to do the saving...
>> >> what's
>> >>> > recommended?
>> >>> > Bob
>> >>> >
>> >>> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote
>> >>> > in
>> >>> > message
>> >>> > news:HyI$O5vtHHA.5076@dacmail.dataaccess.com...
>> >>> >> The readonly field issue is occuring for other people as well, so
>> >>> >> I'll
>> >> be
>> >>> >> looking into that soon. If anyone has any ideas why this might
> occur
>> >> I'd
>> >>> >> gladly hear your opinions :-)
>> >>> >>
>> >>> >> For now you might be able to add the input directly as <input...
>> >>> >> />
>> >>> > leaving
>> >>> >> out the readonly and possible tabindex attributes instead of
> calling
>> >> the
>> >>> >> DDValue function which generates it as readonly.
>> >>> >>
>> >>> >>
>> >>> >> -Edwin
>> >>> >>
>> >>> >>
>> >>> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >>> >> news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
>> >>> >> >I did a little more work on this program. As usual I thought
>> >>> >> >this
>> >>> >> >simple
>> >>> >> > two file form would be a relatively easy exercise but of course
>> >>> >> > it's
>> >>> >> > turned
>> >>> >> > into a number of frustrations. The layout is:
>> >>> >> >
>> >>> >> > Customer
>> >>> >> > |
>> >>> >> > Invoice
>> >>> >> >
>> >>> >> > with a single numeric ID relationship between them. As stated
>> >>> >> > above
>> >>> >> > the
>> >>> >> > customer is on the top, Invoice is on one tab, and
>> >>> >> > customer.notes
>> >>> >> > is
>> >> on
>> >>> > a
>> >>> >> > second tab. All works except for the invoice, I cannot access
> any
>> >>> >> > of
>> >>> > the
>> >>> >> > data fields, all except for the ID are readonly. The main_dd in
>> >>> >> > the
>> >>> >> > .wo
>> >>> >> > is
>> >>> >> > Customer.
>> >>> >> >
>> >>> >> > So I tried changing the main_DD to the invoice file. Changed
>> >>> >> > the
>> >>> >> > vdfServer
>> >>> >> > in the asp to invoice. This opened up the invoice file to
>> >>> >> > entry,
>> >>> >> > but
>> >>> > did
>> >>> >> > two things to the customer. a) Both fields that were finding
>> >>> >> > fields
>> >>> > then
>> >>> >> > insisted on a find required when I attempted to add a new record
>> >>> >> > and
>> >>> >> > tab
>> >>> >> > to
>> >>> >> > another field. b) All non-finding fields were readonly, just
> like
>> >> the
>> >>> >> > invoice fields before.
>> >>> >> >
>> >>> >> > I put the program back to the original main_dd and as a test I
>> >> removed
>> >>> > the
>> >>> >> > tab and put both files on the main screen. No difference, still
>> >> can't
>> >>> >> > access the invoice fields. I thought maybe I needed a
>> >> "vdfServerTable"
>> >>> >> > statement for the invoice file but after trying it in a few
> places
>> >>> >> > found
>> >>> >> > no
>> >>> >> > difference.
>> >>> >> >
>> >>> >> > Very bizarre. Is there any new documentation other than the one
>> >>> >> > "reference"
>> >>> >> > doc?
>> >>> >> > Bob
>> >>> >> >
>> >>> >> >
>> >>> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >>> >> > news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
>> >>> >> >> True to form I answered #1 shortly after asking it. Setting
>> >>> >> >> vdfAutoClearDeoState in the form fixed that problem. However,
>> >>> >> >> what
>> >> is
>> >>> >> >> pbClearAfterSave in the .wo for, just a leftover from the old
> way
>> >>> >> >> of
>> >>> >> >> doing
>> >>> >> >> things?
>> >>> >> >>
>> >>> >> >> Related to question 2, I've got my child file on a tab (and not
> a
>> >>> > grid),
>> >>> >> > and
>> >>> >> >> for some reason all of the fields are readonly and I can't
> figure
>> >> out
>> >>> >> >> why.
>> >>> >> >> I can find and display the data, but can't enter or edit the
>> >>> >> >> fields,
>> >>> >> > though
>> >>> >> >> date fields will populate from the popup calendar. I've spent
>> >>> >> >> some
>> >>> > time
>> >>> >> >> trying to find a readonly or displayonly property that might be
>> >>> >> >> set
>> >>> >> >> but
>> >>> >> >> haven't seen any.
>> >>> >> >> Bob
>> >>> >> >>
>> >>> >> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >>> >> >> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
>> >>> >> >> > In the contact management example I've noticed two things
>> >>> >> >> > that
>> >> don't
>> >>> >> > seem
>> >>> >> >> to
>> >>> >> >> > be working.
>> >>> >> >> >
>> >>> >> >> > 1) The property pbClearAfterSave is set to false in the .wo
> yet
>> >> the
>> >>> >> > screen
>> >>> >> >> > still clears after saving.
>> >>> >> >> >
>> >>> >> >> > 2) If you make a change to the child file Calls, in the notes
>> >> field,
>> >>> >> > lower
>> >>> >> >> > right, the save does not take - any changes are not saved.
>> >>> >> >> > Since
>> >>> >> >> > the
>> >>> >> >> > main_dd of the wo is the parent, or contacts file, what is
>> >>> >> >> > the
>> >>> >> >> > preferred
>> >>> >> >> > method of saving a non-table child record? In this case the
>> >> notes?
>> >>> > I
>> >>> >> >> have
>> >>> >> >> > a similar layout I'm working on and have the same problem.
>> >>> >> >> >
>> >>> >> >> > Why do these questions always seem to come up on a Friday
>> >> afternoon
>> >>> >> >> > when
>> >>> >> >> no
>> >>> >> >> > one is around to answer them?
>> >>> >> >> >
>> >>> >> >> > Bob
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >
>> >>> >
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>>
>
>
>

Bob Worsley
25-Jun-2007, 10:12 AM
That could work, is there some way I could color every other row
differently?
Bob

"Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in message
news:WGI%239SztHHA.5076@dacmail.dataaccess.com...
> I believe you can simply add a <br /> tag between two fields in a single
> column in your grid. This is not actually two rows but it should look
pretty
> much the same.
>
> Example:
>
> <td><input type="text" size="35" title="Inventory Part Desription"
> name="invt__description" value="" /><br />
> <input type="text" size="8" readonly="readonly" title="Retail unit price"
> name="Invt__unit_price" value="0" /></td>
>
>
>
> -Edwin
>
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:VKcYJPztHHA.5828@dacmail.dataaccess.com...
> > Actually this is not a 1:1 situation, and a grid would theoretically
work.
> > The reason I didn't use a grid is that the data record consists of 3
date
> > fields, 6 text fields, and the image path. They won't all fit on a
single
> > grid line. So unless I'm able to use multiple lines in the grid for one
> > record, or use a popup for some of the fields, which I've done before, I
> > have to do it this way -- with single record entry.
> > Bob
> >
> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> > message
> > news:UPVahKztHHA.5828@dacmail.dataaccess.com...
> >> Or not really a 1:1 relation but more a 1:0-1 relation, but a max of 1
> > child
> >> record for each parent at least which was my point in the grid being a
> > bit
> >> overkill.
> >>
> >> -Edwin
> >>
> >>
> >> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> > message
> >> news:TgoG7IztHHA.5076@dacmail.dataaccess.com...
> >> >I was thinking how the order entry exxample did that with child
records,
> >> >but that of course is a child in a grid and grids are obviously
handled
> >> >differently.
> >> > I guess two options that would be possible is to change the data
> > structure
> >> > so the child-parent relation is reversed which most likely is not
> >> > possible, or to add in in a grid, but by the sound of it it's a 1:1
> >> > relation so that would be a bit overkill.
> >> >
> >> > My guess is that if you leave the child record empty it will either
not
> >> > save anything at all or create new empty records, depending on you
data
> >> > structure and validation.
> >> >
> >> > -Edwin
> >> >
> >> >
> >> >
> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> > news:CZhlq1ytHHA.5076@dacmail.dataaccess.com...
> >> >> Agreed, as little extra code as possible is always good! The only
> >> >> question
> >> >> is whether making the child the main_DD would mean I'd always have
to
> >> >> have a
> >> >> child record in order to save, and that I haven't determined as yet.
> > The
> >> >> way the users will use this is to enter either parent, both, or find
a
> >> >> parent and then add a child. In other words all ways. So, it might
> > mean
> >> >> extra code...
> >> >> Bob
> >> >>
> >> >> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> >> >> message
> >> >> news:gDDowyytHHA.5076@dacmail.dataaccess.com...
> >> >>> My mistake, I read the whole thing as being a problem caused by
> >> >>> trying
> >> >>> to
> >> >>> get around the readonly thing and that it wasn't a problem if you
> > could
> >> >> just
> >> >>> have non-readonly fields. Guess I misread that.
> >> >>>
> >> >>> My suggestion would always be, if possible don't write any manual
> > code.
> >> >>> If
> >> >>> changing the main dd to the child is ok for the page, and does not
> > mess
> >> >>> up
> >> >>> any of the find actions/etc you should do this imo. If however it
is
> > for
> >> >>> some reason not possible there's is little choice but to additional
> > code
> >> >> to
> >> >>> save.
> >> >>>
> >> >>> -Edwin
> >> >>>
> >> >>>
> >> >>> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> >>> news:dmbWd%23xtHHA.5828@dacmail.dataaccess.com...
> >> >>> > Changing to input style controls did eliminate the readonly
> >> >>> > problem,
> >> >>> > but
> >> >>> > you
> >> >>> > didn't address the question of saving. Where the parent is the
> >> >>> > main_DD,
> >> >>> > how
> >> >>> > do I get the child to save? Simply having the cursor in one of
the
> >> >> child
> >> >>> > fields and hitting save doesn't do it. Choices might be to
change
> > the
> >> >>> > main_DD to the child or write some manual code to do the
saving...
> >> >> what's
> >> >>> > recommended?
> >> >>> > Bob
> >> >>> >
> >> >>> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote
> >> >>> > in
> >> >>> > message
> >> >>> > news:HyI$O5vtHHA.5076@dacmail.dataaccess.com...
> >> >>> >> The readonly field issue is occuring for other people as well,
so
> >> >>> >> I'll
> >> >> be
> >> >>> >> looking into that soon. If anyone has any ideas why this might
> > occur
> >> >> I'd
> >> >>> >> gladly hear your opinions :-)
> >> >>> >>
> >> >>> >> For now you might be able to add the input directly as <input...
> >> >>> >> />
> >> >>> > leaving
> >> >>> >> out the readonly and possible tabindex attributes instead of
> > calling
> >> >> the
> >> >>> >> DDValue function which generates it as readonly.
> >> >>> >>
> >> >>> >>
> >> >>> >> -Edwin
> >> >>> >>
> >> >>> >>
> >> >>> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> >>> >> news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
> >> >>> >> >I did a little more work on this program. As usual I thought
> >> >>> >> >this
> >> >>> >> >simple
> >> >>> >> > two file form would be a relatively easy exercise but of
course
> >> >>> >> > it's
> >> >>> >> > turned
> >> >>> >> > into a number of frustrations. The layout is:
> >> >>> >> >
> >> >>> >> > Customer
> >> >>> >> > |
> >> >>> >> > Invoice
> >> >>> >> >
> >> >>> >> > with a single numeric ID relationship between them. As stated
> >> >>> >> > above
> >> >>> >> > the
> >> >>> >> > customer is on the top, Invoice is on one tab, and
> >> >>> >> > customer.notes
> >> >>> >> > is
> >> >> on
> >> >>> > a
> >> >>> >> > second tab. All works except for the invoice, I cannot access
> > any
> >> >>> >> > of
> >> >>> > the
> >> >>> >> > data fields, all except for the ID are readonly. The main_dd
in
> >> >>> >> > the
> >> >>> >> > .wo
> >> >>> >> > is
> >> >>> >> > Customer.
> >> >>> >> >
> >> >>> >> > So I tried changing the main_DD to the invoice file. Changed
> >> >>> >> > the
> >> >>> >> > vdfServer
> >> >>> >> > in the asp to invoice. This opened up the invoice file to
> >> >>> >> > entry,
> >> >>> >> > but
> >> >>> > did
> >> >>> >> > two things to the customer. a) Both fields that were finding
> >> >>> >> > fields
> >> >>> > then
> >> >>> >> > insisted on a find required when I attempted to add a new
record
> >> >>> >> > and
> >> >>> >> > tab
> >> >>> >> > to
> >> >>> >> > another field. b) All non-finding fields were readonly, just
> > like
> >> >> the
> >> >>> >> > invoice fields before.
> >> >>> >> >
> >> >>> >> > I put the program back to the original main_dd and as a test I
> >> >> removed
> >> >>> > the
> >> >>> >> > tab and put both files on the main screen. No difference,
still
> >> >> can't
> >> >>> >> > access the invoice fields. I thought maybe I needed a
> >> >> "vdfServerTable"
> >> >>> >> > statement for the invoice file but after trying it in a few
> > places
> >> >>> >> > found
> >> >>> >> > no
> >> >>> >> > difference.
> >> >>> >> >
> >> >>> >> > Very bizarre. Is there any new documentation other than the
one
> >> >>> >> > "reference"
> >> >>> >> > doc?
> >> >>> >> > Bob
> >> >>> >> >
> >> >>> >> >
> >> >>> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> >>> >> > news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
> >> >>> >> >> True to form I answered #1 shortly after asking it. Setting
> >> >>> >> >> vdfAutoClearDeoState in the form fixed that problem.
However,
> >> >>> >> >> what
> >> >> is
> >> >>> >> >> pbClearAfterSave in the .wo for, just a leftover from the old
> > way
> >> >>> >> >> of
> >> >>> >> >> doing
> >> >>> >> >> things?
> >> >>> >> >>
> >> >>> >> >> Related to question 2, I've got my child file on a tab (and
not
> > a
> >> >>> > grid),
> >> >>> >> > and
> >> >>> >> >> for some reason all of the fields are readonly and I can't
> > figure
> >> >> out
> >> >>> >> >> why.
> >> >>> >> >> I can find and display the data, but can't enter or edit the
> >> >>> >> >> fields,
> >> >>> >> > though
> >> >>> >> >> date fields will populate from the popup calendar. I've
spent
> >> >>> >> >> some
> >> >>> > time
> >> >>> >> >> trying to find a readonly or displayonly property that might
be
> >> >>> >> >> set
> >> >>> >> >> but
> >> >>> >> >> haven't seen any.
> >> >>> >> >> Bob
> >> >>> >> >>
> >> >>> >> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> >>> >> >> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
> >> >>> >> >> > In the contact management example I've noticed two things
> >> >>> >> >> > that
> >> >> don't
> >> >>> >> > seem
> >> >>> >> >> to
> >> >>> >> >> > be working.
> >> >>> >> >> >
> >> >>> >> >> > 1) The property pbClearAfterSave is set to false in the .wo
> > yet
> >> >> the
> >> >>> >> > screen
> >> >>> >> >> > still clears after saving.
> >> >>> >> >> >
> >> >>> >> >> > 2) If you make a change to the child file Calls, in the
notes
> >> >> field,
> >> >>> >> > lower
> >> >>> >> >> > right, the save does not take - any changes are not saved.
> >> >>> >> >> > Since
> >> >>> >> >> > the
> >> >>> >> >> > main_dd of the wo is the parent, or contacts file, what is
> >> >>> >> >> > the
> >> >>> >> >> > preferred
> >> >>> >> >> > method of saving a non-table child record? In this case
the
> >> >> notes?
> >> >>> > I
> >> >>> >> >> have
> >> >>> >> >> > a similar layout I'm working on and have the same problem.
> >> >>> >> >> >
> >> >>> >> >> > Why do these questions always seem to come up on a Friday
> >> >> afternoon
> >> >>> >> >> > when
> >> >>> >> >> no
> >> >>> >> >> > one is around to answer them?
> >> >>> >> >> >
> >> >>> >> >> > Bob
> >> >>> >> >> >
> >> >>> >> >> >
> >> >>> >> >> >
> >> >>> >> >> >
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >
> >> >>> >>
> >> >>> >>
> >> >>> >>
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >>
> >
> >
> >
>
>
>

Bob Worsley
25-Jun-2007, 12:38 PM
Something's amiss. I changed the main_dd in the .wo to the child file,
Invoice, and also changed the vdfMainTable in the asp page to "invoice" and
the child table still will not save. I put debugging into each of the DDs
and the only request_save that gets called is the parent one. What a I
missing?
Bob

"Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in message
news:gDDowyytHHA.5076@dacmail.dataaccess.com...
> My mistake, I read the whole thing as being a problem caused by trying to
> get around the readonly thing and that it wasn't a problem if you could
just
> have non-readonly fields. Guess I misread that.
>
> My suggestion would always be, if possible don't write any manual code. If
> changing the main dd to the child is ok for the page, and does not mess up
> any of the find actions/etc you should do this imo. If however it is for
> some reason not possible there's is little choice but to additional code
to
> save.
>
> -Edwin
>
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:dmbWd%23xtHHA.5828@dacmail.dataaccess.com...
> > Changing to input style controls did eliminate the readonly problem, but
> > you
> > didn't address the question of saving. Where the parent is the main_DD,
> > how
> > do I get the child to save? Simply having the cursor in one of the
child
> > fields and hitting save doesn't do it. Choices might be to change the
> > main_DD to the child or write some manual code to do the saving...
what's
> > recommended?
> > Bob
> >
> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> > message
> > news:HyI$O5vtHHA.5076@dacmail.dataaccess.com...
> >> The readonly field issue is occuring for other people as well, so I'll
be
> >> looking into that soon. If anyone has any ideas why this might occur
I'd
> >> gladly hear your opinions :-)
> >>
> >> For now you might be able to add the input directly as <input... />
> > leaving
> >> out the readonly and possible tabindex attributes instead of calling
the
> >> DDValue function which generates it as readonly.
> >>
> >>
> >> -Edwin
> >>
> >>
> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
> >> >I did a little more work on this program. As usual I thought this
> >> >simple
> >> > two file form would be a relatively easy exercise but of course it's
> >> > turned
> >> > into a number of frustrations. The layout is:
> >> >
> >> > Customer
> >> > |
> >> > Invoice
> >> >
> >> > with a single numeric ID relationship between them. As stated above
> >> > the
> >> > customer is on the top, Invoice is on one tab, and customer.notes is
on
> > a
> >> > second tab. All works except for the invoice, I cannot access any of
> > the
> >> > data fields, all except for the ID are readonly. The main_dd in the
> >> > .wo
> >> > is
> >> > Customer.
> >> >
> >> > So I tried changing the main_DD to the invoice file. Changed the
> >> > vdfServer
> >> > in the asp to invoice. This opened up the invoice file to entry, but
> > did
> >> > two things to the customer. a) Both fields that were finding fields
> > then
> >> > insisted on a find required when I attempted to add a new record and
> >> > tab
> >> > to
> >> > another field. b) All non-finding fields were readonly, just like
the
> >> > invoice fields before.
> >> >
> >> > I put the program back to the original main_dd and as a test I
removed
> > the
> >> > tab and put both files on the main screen. No difference, still
can't
> >> > access the invoice fields. I thought maybe I needed a
"vdfServerTable"
> >> > statement for the invoice file but after trying it in a few places
> >> > found
> >> > no
> >> > difference.
> >> >
> >> > Very bizarre. Is there any new documentation other than the one
> >> > "reference"
> >> > doc?
> >> > Bob
> >> >
> >> >
> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> > news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
> >> >> True to form I answered #1 shortly after asking it. Setting
> >> >> vdfAutoClearDeoState in the form fixed that problem. However, what
is
> >> >> pbClearAfterSave in the .wo for, just a leftover from the old way of
> >> >> doing
> >> >> things?
> >> >>
> >> >> Related to question 2, I've got my child file on a tab (and not a
> > grid),
> >> > and
> >> >> for some reason all of the fields are readonly and I can't figure
out
> >> >> why.
> >> >> I can find and display the data, but can't enter or edit the fields,
> >> > though
> >> >> date fields will populate from the popup calendar. I've spent some
> > time
> >> >> trying to find a readonly or displayonly property that might be set
> >> >> but
> >> >> haven't seen any.
> >> >> Bob
> >> >>
> >> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> >> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
> >> >> > In the contact management example I've noticed two things that
don't
> >> > seem
> >> >> to
> >> >> > be working.
> >> >> >
> >> >> > 1) The property pbClearAfterSave is set to false in the .wo yet
the
> >> > screen
> >> >> > still clears after saving.
> >> >> >
> >> >> > 2) If you make a change to the child file Calls, in the notes
field,
> >> > lower
> >> >> > right, the save does not take - any changes are not saved. Since
> >> >> > the
> >> >> > main_dd of the wo is the parent, or contacts file, what is the
> >> >> > preferred
> >> >> > method of saving a non-table child record? In this case the
notes?
> > I
> >> >> have
> >> >> > a similar layout I'm working on and have the same problem.
> >> >> >
> >> >> > Why do these questions always seem to come up on a Friday
afternoon
> >> >> > when
> >> >> no
> >> >> > one is around to answer them?
> >> >> >
> >> >> > Bob
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >
> >
> >
>
>
>

Bob Worsley
25-Jun-2007, 01:47 PM
A further update... When I changed the vdfMainTable to the child file, I
forgot to change vdfServerTable. Once I changed vdfServerTable, I could
save the child file. But... I could no longer edit the parent - fields were
readonly. And all are "input" fields, not DD. If I switch back and forth,
I can alternately get the above effects. I tried adding vdfMainTable to the
invoice controls like we would in a VDF program but nothing helped.
Bob

"Bob Worsley" <bworsley@comcast.net> wrote in message
news:oqNKf90tHHA.5828@dacmail.dataaccess.com...
> Something's amiss. I changed the main_dd in the .wo to the child file,
> Invoice, and also changed the vdfMainTable in the asp page to "invoice"
and
> the child table still will not save. I put debugging into each of the DDs
> and the only request_save that gets called is the parent one. What a I
> missing?
> Bob
>

Edwin van der Velden
26-Jun-2007, 02:19 AM
There's no standard support built in for that as far as I know, it would be
possible. It would be something like using javascript to loop through the
grid rows and change the classname of all even (or uneven whatever you want)
rows.

I'll note down the suggestion.

-Edwin


"Bob Worsley" <bworsley@comcast.net> wrote in message
news:XC9UXsztHHA.5076@dacmail.dataaccess.com...
> That could work, is there some way I could color every other row
> differently?
> Bob
>
> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> message
> news:WGI%239SztHHA.5076@dacmail.dataaccess.com...
>> I believe you can simply add a <br /> tag between two fields in a single
>> column in your grid. This is not actually two rows but it should look
> pretty
>> much the same.
>>
>> Example:
>>
>> <td><input type="text" size="35" title="Inventory Part Desription"
>> name="invt__description" value="" /><br />
>> <input type="text" size="8" readonly="readonly" title="Retail unit price"
>> name="Invt__unit_price" value="0" /></td>
>>
>>
>>
>> -Edwin
>>
>>
>> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> news:VKcYJPztHHA.5828@dacmail.dataaccess.com...
>> > Actually this is not a 1:1 situation, and a grid would theoretically
> work.
>> > The reason I didn't use a grid is that the data record consists of 3
> date
>> > fields, 6 text fields, and the image path. They won't all fit on a
> single
>> > grid line. So unless I'm able to use multiple lines in the grid for
>> > one
>> > record, or use a popup for some of the fields, which I've done before,
>> > I
>> > have to do it this way -- with single record entry.
>> > Bob
>> >
>> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
>> > message
>> > news:UPVahKztHHA.5828@dacmail.dataaccess.com...
>> >> Or not really a 1:1 relation but more a 1:0-1 relation, but a max of 1
>> > child
>> >> record for each parent at least which was my point in the grid being
>> >> a
>> > bit
>> >> overkill.
>> >>
>> >> -Edwin
>> >>
>> >>
>> >> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
>> > message
>> >> news:TgoG7IztHHA.5076@dacmail.dataaccess.com...
>> >> >I was thinking how the order entry exxample did that with child
> records,
>> >> >but that of course is a child in a grid and grids are obviously
> handled
>> >> >differently.
>> >> > I guess two options that would be possible is to change the data
>> > structure
>> >> > so the child-parent relation is reversed which most likely is not
>> >> > possible, or to add in in a grid, but by the sound of it it's a 1:1
>> >> > relation so that would be a bit overkill.
>> >> >
>> >> > My guess is that if you leave the child record empty it will either
> not
>> >> > save anything at all or create new empty records, depending on you
> data
>> >> > structure and validation.
>> >> >
>> >> > -Edwin
>> >> >
>> >> >
>> >> >
>> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >> > news:CZhlq1ytHHA.5076@dacmail.dataaccess.com...
>> >> >> Agreed, as little extra code as possible is always good! The only
>> >> >> question
>> >> >> is whether making the child the main_DD would mean I'd always have
> to
>> >> >> have a
>> >> >> child record in order to save, and that I haven't determined as
>> >> >> yet.
>> > The
>> >> >> way the users will use this is to enter either parent, both, or
>> >> >> find
> a
>> >> >> parent and then add a child. In other words all ways. So, it
>> >> >> might
>> > mean
>> >> >> extra code...
>> >> >> Bob
>> >> >>
>> >> >> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote
>> >> >> in
>> >> >> message
>> >> >> news:gDDowyytHHA.5076@dacmail.dataaccess.com...
>> >> >>> My mistake, I read the whole thing as being a problem caused by
>> >> >>> trying
>> >> >>> to
>> >> >>> get around the readonly thing and that it wasn't a problem if you
>> > could
>> >> >> just
>> >> >>> have non-readonly fields. Guess I misread that.
>> >> >>>
>> >> >>> My suggestion would always be, if possible don't write any manual
>> > code.
>> >> >>> If
>> >> >>> changing the main dd to the child is ok for the page, and does not
>> > mess
>> >> >>> up
>> >> >>> any of the find actions/etc you should do this imo. If however it
> is
>> > for
>> >> >>> some reason not possible there's is little choice but to
>> >> >>> additional
>> > code
>> >> >> to
>> >> >>> save.
>> >> >>>
>> >> >>> -Edwin
>> >> >>>
>> >> >>>
>> >> >>> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >> >>> news:dmbWd%23xtHHA.5828@dacmail.dataaccess.com...
>> >> >>> > Changing to input style controls did eliminate the readonly
>> >> >>> > problem,
>> >> >>> > but
>> >> >>> > you
>> >> >>> > didn't address the question of saving. Where the parent is the
>> >> >>> > main_DD,
>> >> >>> > how
>> >> >>> > do I get the child to save? Simply having the cursor in one of
> the
>> >> >> child
>> >> >>> > fields and hitting save doesn't do it. Choices might be to
> change
>> > the
>> >> >>> > main_DD to the child or write some manual code to do the
> saving...
>> >> >> what's
>> >> >>> > recommended?
>> >> >>> > Bob
>> >> >>> >
>> >> >>> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl>
>> >> >>> > wrote
>> >> >>> > in
>> >> >>> > message
>> >> >>> > news:HyI$O5vtHHA.5076@dacmail.dataaccess.com...
>> >> >>> >> The readonly field issue is occuring for other people as well,
> so
>> >> >>> >> I'll
>> >> >> be
>> >> >>> >> looking into that soon. If anyone has any ideas why this might
>> > occur
>> >> >> I'd
>> >> >>> >> gladly hear your opinions :-)
>> >> >>> >>
>> >> >>> >> For now you might be able to add the input directly as
>> >> >>> >> <input...
>> >> >>> >> />
>> >> >>> > leaving
>> >> >>> >> out the readonly and possible tabindex attributes instead of
>> > calling
>> >> >> the
>> >> >>> >> DDValue function which generates it as readonly.
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> -Edwin
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >> >>> >> news:iFFh24ltHHA.1992@dacmail.dataaccess.com...
>> >> >>> >> >I did a little more work on this program. As usual I thought
>> >> >>> >> >this
>> >> >>> >> >simple
>> >> >>> >> > two file form would be a relatively easy exercise but of
> course
>> >> >>> >> > it's
>> >> >>> >> > turned
>> >> >>> >> > into a number of frustrations. The layout is:
>> >> >>> >> >
>> >> >>> >> > Customer
>> >> >>> >> > |
>> >> >>> >> > Invoice
>> >> >>> >> >
>> >> >>> >> > with a single numeric ID relationship between them. As
>> >> >>> >> > stated
>> >> >>> >> > above
>> >> >>> >> > the
>> >> >>> >> > customer is on the top, Invoice is on one tab, and
>> >> >>> >> > customer.notes
>> >> >>> >> > is
>> >> >> on
>> >> >>> > a
>> >> >>> >> > second tab. All works except for the invoice, I cannot
>> >> >>> >> > access
>> > any
>> >> >>> >> > of
>> >> >>> > the
>> >> >>> >> > data fields, all except for the ID are readonly. The main_dd
> in
>> >> >>> >> > the
>> >> >>> >> > .wo
>> >> >>> >> > is
>> >> >>> >> > Customer.
>> >> >>> >> >
>> >> >>> >> > So I tried changing the main_DD to the invoice file. Changed
>> >> >>> >> > the
>> >> >>> >> > vdfServer
>> >> >>> >> > in the asp to invoice. This opened up the invoice file to
>> >> >>> >> > entry,
>> >> >>> >> > but
>> >> >>> > did
>> >> >>> >> > two things to the customer. a) Both fields that were finding
>> >> >>> >> > fields
>> >> >>> > then
>> >> >>> >> > insisted on a find required when I attempted to add a new
> record
>> >> >>> >> > and
>> >> >>> >> > tab
>> >> >>> >> > to
>> >> >>> >> > another field. b) All non-finding fields were readonly, just
>> > like
>> >> >> the
>> >> >>> >> > invoice fields before.
>> >> >>> >> >
>> >> >>> >> > I put the program back to the original main_dd and as a test
>> >> >>> >> > I
>> >> >> removed
>> >> >>> > the
>> >> >>> >> > tab and put both files on the main screen. No difference,
> still
>> >> >> can't
>> >> >>> >> > access the invoice fields. I thought maybe I needed a
>> >> >> "vdfServerTable"
>> >> >>> >> > statement for the invoice file but after trying it in a few
>> > places
>> >> >>> >> > found
>> >> >>> >> > no
>> >> >>> >> > difference.
>> >> >>> >> >
>> >> >>> >> > Very bizarre. Is there any new documentation other than the
> one
>> >> >>> >> > "reference"
>> >> >>> >> > doc?
>> >> >>> >> > Bob
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >> >>> >> > news:AdSiLsRtHHA.1992@dacmail.dataaccess.com...
>> >> >>> >> >> True to form I answered #1 shortly after asking it. Setting
>> >> >>> >> >> vdfAutoClearDeoState in the form fixed that problem.
> However,
>> >> >>> >> >> what
>> >> >> is
>> >> >>> >> >> pbClearAfterSave in the .wo for, just a leftover from the
>> >> >>> >> >> old
>> > way
>> >> >>> >> >> of
>> >> >>> >> >> doing
>> >> >>> >> >> things?
>> >> >>> >> >>
>> >> >>> >> >> Related to question 2, I've got my child file on a tab (and
> not
>> > a
>> >> >>> > grid),
>> >> >>> >> > and
>> >> >>> >> >> for some reason all of the fields are readonly and I can't
>> > figure
>> >> >> out
>> >> >>> >> >> why.
>> >> >>> >> >> I can find and display the data, but can't enter or edit the
>> >> >>> >> >> fields,
>> >> >>> >> > though
>> >> >>> >> >> date fields will populate from the popup calendar. I've
> spent
>> >> >>> >> >> some
>> >> >>> > time
>> >> >>> >> >> trying to find a readonly or displayonly property that might
> be
>> >> >>> >> >> set
>> >> >>> >> >> but
>> >> >>> >> >> haven't seen any.
>> >> >>> >> >> Bob
>> >> >>> >> >>
>> >> >>> >> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> >> >>> >> >> news:PqBHOiQtHHA.1992@dacmail.dataaccess.com...
>> >> >>> >> >> > In the contact management example I've noticed two things
>> >> >>> >> >> > that
>> >> >> don't
>> >> >>> >> > seem
>> >> >>> >> >> to
>> >> >>> >> >> > be working.
>> >> >>> >> >> >
>> >> >>> >> >> > 1) The property pbClearAfterSave is set to false in the
>> >> >>> >> >> > .wo
>> > yet
>> >> >> the
>> >> >>> >> > screen
>> >> >>> >> >> > still clears after saving.
>> >> >>> >> >> >
>> >> >>> >> >> > 2) If you make a change to the child file Calls, in the
> notes
>> >> >> field,
>> >> >>> >> > lower
>> >> >>> >> >> > right, the save does not take - any changes are not saved.
>> >> >>> >> >> > Since
>> >> >>> >> >> > the
>> >> >>> >> >> > main_dd of the wo is the parent, or contacts file, what is
>> >> >>> >> >> > the
>> >> >>> >> >> > preferred
>> >> >>> >> >> > method of saving a non-table child record? In this case
> the
>> >> >> notes?
>> >> >>> > I
>> >> >>> >> >> have
>> >> >>> >> >> > a similar layout I'm working on and have the same problem.
>> >> >>> >> >> >
>> >> >>> >> >> > Why do these questions always seem to come up on a Friday
>> >> >> afternoon
>> >> >>> >> >> > when
>> >> >>> >> >> no
>> >> >>> >> >> > one is around to answer them?
>> >> >>> >> >> >
>> >> >>> >> >> > Bob
>> >> >>> >> >> >
>> >> >>> >> >> >
>> >> >>> >> >> >
>> >> >>> >> >> >
>> >> >>> >> >>
>> >> >>> >> >>
>> >> >>> >> >>
>> >> >>> >> >>
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >
>> >
>> >
>>
>>
>>
>
>
>

Edwin van der Velden
26-Jun-2007, 02:24 AM
The field are added directly as <input .../> or by calling the DDValue
function? I agree that it should work for both ways but if the DDValue
produces the wrong result you can always add the input fields mannually.


-Edwin


"Bob Worsley" <bworsley@comcast.net> wrote in message
news:Zg5xLk1tHHA.5828@dacmail.dataaccess.com...
>A further update... When I changed the vdfMainTable to the child file, I
> forgot to change vdfServerTable. Once I changed vdfServerTable, I could
> save the child file. But... I could no longer edit the parent - fields
> were
> readonly. And all are "input" fields, not DD. If I switch back and
> forth,
> I can alternately get the above effects. I tried adding vdfMainTable to
> the
> invoice controls like we would in a VDF program but nothing helped.
> Bob
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:oqNKf90tHHA.5828@dacmail.dataaccess.com...
>> Something's amiss. I changed the main_dd in the .wo to the child file,
>> Invoice, and also changed the vdfMainTable in the asp page to "invoice"
> and
>> the child table still will not save. I put debugging into each of the
>> DDs
>> and the only request_save that gets called is the parent one. What a I
>> missing?
>> Bob
>>
>
>
>

Bob Worsley
26-Jun-2007, 06:01 AM
Edwin, I think you missed my point.

A simple header detail setup that does not use a grid for the child simply
does not work with this product! You need to set this up and try it
yourself as it is a common usage.

I give up, thanks for trying.
Bob

"Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in message
news:cOWxHM8tHHA.5736@dacmail.dataaccess.com...
> The field are added directly as <input .../> or by calling the DDValue
> function? I agree that it should work for both ways but if the DDValue
> produces the wrong result you can always add the input fields mannually.
>
>
> -Edwin
>
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:Zg5xLk1tHHA.5828@dacmail.dataaccess.com...
> >A further update... When I changed the vdfMainTable to the child file,
I
> > forgot to change vdfServerTable. Once I changed vdfServerTable, I could
> > save the child file. But... I could no longer edit the parent - fields
> > were
> > readonly. And all are "input" fields, not DD. If I switch back and
> > forth,
> > I can alternately get the above effects. I tried adding vdfMainTable to
> > the
> > invoice controls like we would in a VDF program but nothing helped.
> > Bob
> >
> > "Bob Worsley" <bworsley@comcast.net> wrote in message
> > news:oqNKf90tHHA.5828@dacmail.dataaccess.com...
> >> Something's amiss. I changed the main_dd in the .wo to the child file,
> >> Invoice, and also changed the vdfMainTable in the asp page to "invoice"
> > and
> >> the child table still will not save. I put debugging into each of the
> >> DDs
> >> and the only request_save that gets called is the parent one. What a I
> >> missing?
> >> Bob
> >>
> >
> >
> >
>
>
>

Edwin van der Velden
26-Jun-2007, 06:56 AM
Well, a header detail setup ussually involves one header which has multiple
detail records. In this case it would make sense to use a grid wouldn't it?
Since a parent can have multiple child records and the child record could be
attached to more then one parent.

In case of a really simple header detail setup, a 1:1 relation, you can get
it to work as it does in the ajax order example. There you have a single
orderhea record with a single salesp record. Although in that case the main
dd is orderhea and salesp is a parent of orderhea.

I do agree there are things which don't work yet (as expected) which you
could expect to use and therefore should work in the next release, I'm just
trying to get clear what and how you as user expect it to work exactly.

If you got any example application and/or detailed description of the
problems you can always send me those (if size allows). Application made out
there in the "wild" are often a great source for me to test and fix
bugs/missing features etc. Of course if you don't want or can't send me
anything like that I'll always try to reproduce the problems over here. If
you can at least provide me with a overview of the data strucure (please
indicate clearly which table is child and which a parent) and a description
of what exactly occurs/should occur. I know you did this already in this
thread obviously but just to make sure I understand the whole thing
correctly. You can post it here or mail me directly.

-Edwin



"Bob Worsley" <bworsley@comcast.net> wrote in message
news:uj56aE%23tHHA.5736@dacmail.dataaccess.com...
> Edwin, I think you missed my point.
>
> A simple header detail setup that does not use a grid for the child simply
> does not work with this product! You need to set this up and try it
> yourself as it is a common usage.
>
> I give up, thanks for trying.
> Bob
>
> "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> message
> news:cOWxHM8tHHA.5736@dacmail.dataaccess.com...
>> The field are added directly as <input .../> or by calling the DDValue
>> function? I agree that it should work for both ways but if the DDValue
>> produces the wrong result you can always add the input fields mannually.
>>
>>
>> -Edwin
>>
>>
>> "Bob Worsley" <bworsley@comcast.net> wrote in message
>> news:Zg5xLk1tHHA.5828@dacmail.dataaccess.com...
>> >A further update... When I changed the vdfMainTable to the child file,
> I
>> > forgot to change vdfServerTable. Once I changed vdfServerTable, I
>> > could
>> > save the child file. But... I could no longer edit the parent - fields
>> > were
>> > readonly. And all are "input" fields, not DD. If I switch back and
>> > forth,
>> > I can alternately get the above effects. I tried adding vdfMainTable
>> > to
>> > the
>> > invoice controls like we would in a VDF program but nothing helped.
>> > Bob
>> >
>> > "Bob Worsley" <bworsley@comcast.net> wrote in message
>> > news:oqNKf90tHHA.5828@dacmail.dataaccess.com...
>> >> Something's amiss. I changed the main_dd in the .wo to the child
>> >> file,
>> >> Invoice, and also changed the vdfMainTable in the asp page to
>> >> "invoice"
>> > and
>> >> the child table still will not save. I put debugging into each of the
>> >> DDs
>> >> and the only request_save that gets called is the parent one. What a
>> >> I
>> >> missing?
>> >> Bob
>> >>
>> >
>> >
>> >
>>
>>
>>
>
>
>

Bob Worsley
26-Jun-2007, 07:17 AM
The configuration I am using isn't all that odd. At least I don't think so
as I've used it before in Windows. It's a simple one to many parent child
relationship of two files, but the child doesn't use a grid, it instead uses
a lookup to locate the appropriate child. The reason I did this is as I
said earlier, there are too many large child fields to fit on a grid. We
discussed multiple rows but I think that would be very ugly in this case.

I will zip up my effort and send it though it would be easy to duplicate
with the order.asp by simply changing the grid to single record entry with a
lookup. Let me think about what's easier, my full app might confuse the
issue.
Bob

"Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in message
news:PnN7Tk%23tHHA.5828@dacmail.dataaccess.com...
> Well, a header detail setup ussually involves one header which has
multiple
> detail records. In this case it would make sense to use a grid wouldn't
it?
> Since a parent can have multiple child records and the child record could
be
> attached to more then one parent.
>
> In case of a really simple header detail setup, a 1:1 relation, you can
get
> it to work as it does in the ajax order example. There you have a single
> orderhea record with a single salesp record. Although in that case the
main
> dd is orderhea and salesp is a parent of orderhea.
>
> I do agree there are things which don't work yet (as expected) which you
> could expect to use and therefore should work in the next release, I'm
just
> trying to get clear what and how you as user expect it to work exactly.
>
> If you got any example application and/or detailed description of the
> problems you can always send me those (if size allows). Application made
out
> there in the "wild" are often a great source for me to test and fix
> bugs/missing features etc. Of course if you don't want or can't send me
> anything like that I'll always try to reproduce the problems over here. If
> you can at least provide me with a overview of the data strucure (please
> indicate clearly which table is child and which a parent) and a
description
> of what exactly occurs/should occur. I know you did this already in this
> thread obviously but just to make sure I understand the whole thing
> correctly. You can post it here or mail me directly.
>
> -Edwin
>
>
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:uj56aE%23tHHA.5736@dacmail.dataaccess.com...
> > Edwin, I think you missed my point.
> >
> > A simple header detail setup that does not use a grid for the child
simply
> > does not work with this product! You need to set this up and try it
> > yourself as it is a common usage.
> >
> > I give up, thanks for trying.
> > Bob
> >
> > "Edwin van der Velden" <edwin.van.der.velden@dataaccess.nl> wrote in
> > message
> > news:cOWxHM8tHHA.5736@dacmail.dataaccess.com...
> >> The field are added directly as <input .../> or by calling the DDValue
> >> function? I agree that it should work for both ways but if the DDValue
> >> produces the wrong result you can always add the input fields
mannually.
> >>
> >>
> >> -Edwin
> >>
> >>
> >> "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> news:Zg5xLk1tHHA.5828@dacmail.dataaccess.com...
> >> >A further update... When I changed the vdfMainTable to the child
file,
> > I
> >> > forgot to change vdfServerTable. Once I changed vdfServerTable, I
> >> > could
> >> > save the child file. But... I could no longer edit the parent -
fields
> >> > were
> >> > readonly. And all are "input" fields, not DD. If I switch back and
> >> > forth,
> >> > I can alternately get the above effects. I tried adding vdfMainTable
> >> > to
> >> > the
> >> > invoice controls like we would in a VDF program but nothing helped.
> >> > Bob
> >> >
> >> > "Bob Worsley" <bworsley@comcast.net> wrote in message
> >> > news:oqNKf90tHHA.5828@dacmail.dataaccess.com...
> >> >> Something's amiss. I changed the main_dd in the .wo to the child
> >> >> file,
> >> >> Invoice, and also changed the vdfMainTable in the asp page to
> >> >> "invoice"
> >> > and
> >> >> the child table still will not save. I put debugging into each of
the
> >> >> DDs
> >> >> and the only request_save that gets called is the parent one. What
a
> >> >> I
> >> >> missing?
> >> >> Bob
> >> >>
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >
> >
> >
>
>
>