FORMSET Issues

I am using something new for me, a FORMSET. Problem is, it does not
behave the same on my home development box as it does on my other
boxes.

1. FORM1 in formset, lets a user select the customer, then brings up a
grid on FORM2.

2. User nows selects a customer detail record and presses a button to
make FORM3.visible, which should display information in textbox's
based on the current record.

Two XP Professional/SP2 boxes on INTEL show the correct record on
FORM3.

My new XP Media Center Edition/SP2 on AMD Athlon 64 will not display
the correct record.

This new XP Media Center box is also the same box where Foxpro 9/SP1
will not ask if I want to overwrite the existing .exe when rebuilding.
I even Uninstalled and Reinstalled today, but getting the same
results.

This is really frustrating trying to get this stuff working, when the
behavior is different on different PC's. Anybody got any ideas?????

Thanks for your help

Matthew
Fri Feb 10 18:11:54 CST 2006

I have a great idea. Don't use a formset. It was a bad idea (read: really
really stupid idea omg Microsoft wtf were you thinking?) that should have
never been implemented in VFP. Figure out a way to do what you want without
formsets.

However, if you are determined to keep using formsets (and I suspect your
problem has nothing to do with the fact that you are using formsets)...Make
sure you really are running the same version of the same app with the same
data on both machines. Unless someone here has a better idea, I'd trace the
code that selects the detail record, and see what it is doing when it is not
displaying the correct record.

PS: Uninstalling/reinstalling VFP does not fix things that can break, nor
does it remove registry settings. I've had VFP break several times, and
uninstall/reinstall never fixed anything.

"Jacob" <jStoddard@hotMailCCC.com> wrote in message
news:ke9qu192gnlrgb0k2ft4g19u5h8q77s9lc@4ax.com...
>I am using something new for me, a FORMSET. Problem is, it does not
> behave the same on my home development box as it does on my other
> boxes.
>
> 1. FORM1 in formset, lets a user select the customer, then brings up a
> grid on FORM2.
>
> 2. User nows selects a customer detail record and presses a button to
> make FORM3.visible, which should display information in textbox's
> based on the current record.
>
> Two XP Professional/SP2 boxes on INTEL show the correct record on
> FORM3.
>
> My new XP Media Center Edition/SP2 on AMD Athlon 64 will not display
> the correct record.
>
> This new XP Media Center box is also the same box where Foxpro 9/SP1
> will not ask if I want to overwrite the existing .exe when rebuilding.
> I even Uninstalled and Reinstalled today, but getting the same
> results.
>
> This is really frustrating trying to get this stuff working, when the
> behavior is different on different PC's. Anybody got any ideas?????
>
> Thanks for your help
>

Jacob
Fri Feb 10 18:36:45 CST 2006

So tell me why formsets are not a good idea. Granted I have been
doing Foxpro for a really long time, and have never used them, but
this seemed appropriate.

The app is the same on all boxes. I am storing the record number from
FORM2 to THISFORMSET.recNo and then GO to that record before making
FORM3 visible.

I agree, uninstalling doesn't solve much. I noticed after
reinstalling that all the settings for foxpro were the same.


On Fri, 10 Feb 2006 16:11:54 -0800, "Matthew L Reed" <nousenetspam at
dead ice dot us> wrote:

>I have a great idea. Don't use a formset. It was a bad idea (read: really
>really stupid idea omg Microsoft wtf were you thinking?) that should have
>never been implemented in VFP. Figure out a way to do what you want without
>formsets.
>
>However, if you are determined to keep using formsets (and I suspect your
>problem has nothing to do with the fact that you are using formsets)...Make
>sure you really are running the same version of the same app with the same
>data on both machines. Unless someone here has a better idea, I'd trace the
>code that selects the detail record, and see what it is doing when it is not
>displaying the correct record.
>
>PS: Uninstalling/reinstalling VFP does not fix things that can break, nor
>does it remove registry settings. I've had VFP break several times, and
>uninstall/reinstall never fixed anything.
>
>"Jacob" <jStoddard@hotMailCCC.com> wrote in message
>news:ke9qu192gnlrgb0k2ft4g19u5h8q77s9lc@4ax.com...
>>I am using something new for me, a FORMSET. Problem is, it does not
>> behave the same on my home development box as it does on my other
>> boxes.
>>
>> 1. FORM1 in formset, lets a user select the customer, then brings up a
>> grid on FORM2.
>>
>> 2. User nows selects a customer detail record and presses a button to
>> make FORM3.visible, which should display information in textbox's
>> based on the current record.
>>
>> Two XP Professional/SP2 boxes on INTEL show the correct record on
>> FORM3.
>>
>> My new XP Media Center Edition/SP2 on AMD Athlon 64 will not display
>> the correct record.
>>
>> This new XP Media Center box is also the same box where Foxpro 9/SP1
>> will not ask if I want to overwrite the existing .exe when rebuilding.
>> I even Uninstalled and Reinstalled today, but getting the same
>> results.
>>
>> This is really frustrating trying to get this stuff working, when the
>> behavior is different on different PC's. Anybody got any ideas?????
>>
>> Thanks for your help
>>
>

Josh
Fri Feb 10 20:16:36 CST 2006

>I have a great idea. Don't use a formset. It was a bad idea (read: really
>really stupid idea omg Microsoft wtf were you thinking?) that should have
>never been implemented in VFP. Figure out a way to do what you want without
>formsets.

Formsets were kept as part of "backward compatibility" to FPW...
MS didn't invent it; and they've stuck (pretty much) to "leave existing
functionality".


--- AntiSpam/harvest ---
Remove X's to send email to me.

Jacob
Fri Feb 10 21:05:47 CST 2006

Enough said then. Need to figure out how to do this with a bunch of
forms that talk to one another.

On Fri, 10 Feb 2006 18:16:36 -0800, Josh Assing <XjoshX@jAssing.com>
wrote:

>>I have a great idea. Don't use a formset. It was a bad idea (read: really
>>really stupid idea omg Microsoft wtf were you thinking?) that should have
>>never been implemented in VFP. Figure out a way to do what you want without
>>formsets.
>
>Formsets were kept as part of "backward compatibility" to FPW...
>MS didn't invent it; and they've stuck (pretty much) to "leave existing
>functionality".
>
>
>--- AntiSpam/harvest ---
>Remove X's to send email to me.

Fred
Sat Feb 11 01:00:26 CST 2006

If your forms can only be activated from a parent form, in the Load of the
child form, you could store _SCREEN.ActiveForm into a property of the child
form. This would give you a reference to the parent form and you can then
access all of the parent form's properties and methods as needed.

Say your child form property is oParentForm, then in a child.Load:

thisform.oParentForm = _SCREEN.ActiveForm

and then you could reference properties on the parent form via:

thisform.oParentForm.other_properties

--
Fred
Microsoft Visual FoxPro MVP


"Jacob" <jStoddard@hotMailCCC.com> wrote in message
news:l1lqu1pv0ulnbkeagvneaf4egkaak8q047@4ax.com...
> Enough said then. Need to figure out how to do this with a bunch of
> forms that talk to one another.
>
> On Fri, 10 Feb 2006 18:16:36 -0800, Josh Assing <XjoshX@jAssing.com>
> wrote:
>
>>>I have a great idea. Don't use a formset. It was a bad idea (read: really
>>>really stupid idea omg Microsoft wtf were you thinking?) that should
>>>have
>>>never been implemented in VFP. Figure out a way to do what you want
>>>without
>>>formsets.
>>
>>Formsets were kept as part of "backward compatibility" to FPW...
>>MS didn't invent it; and they've stuck (pretty much) to "leave existing
>>functionality".
>>
>>
>>--- AntiSpam/harvest ---
>>Remove X's to send email to me.

Imaginecorp
Sat Feb 11 13:40:37 CST 2006

Hello Jacob;

Design your child forms

Set their DataSession to 1 - Default Data Session



In the Init event insert the following code



LParameters pWhoCalled,pDatasessionID



You can call them whatever you want

(pdatasessionID, even though not needed, I do it just to be extra safe in
case another form is opened )



With this

.addproperty("oWhoCalled",pWhoCalled)

.datasessionid = pDatasessionID

<<other code>>

Endwith



Now you have Total control over the parentform with Thisform.oWhoCalled.



Your parent form should send these 2 parameters i.e. Do form myform with
thisform,thisform.datasessionID



Now you can acess tables, properties and methods, even controls on the
parentform from the child forms.



Tip: I would create the child form as Modal, to ovoid them being orphaned if
the parent form is closed unless you Link them to the Parent, then they will
also close when the parent is closed. This also prevents the user form
"wandering" to other stuff that might be open



Good luck

Mohammed

www.imaginecorp.com/whatwedo.htm



"Jacob" <jStoddard@hotMailCCC.com> wrote in message
news:l1lqu1pv0ulnbkeagvneaf4egkaak8q047@4ax.com...
> Enough said then. Need to figure out how to do this with a bunch of
> forms that talk to one another.
>
> On Fri, 10 Feb 2006 18:16:36 -0800, Josh Assing <XjoshX@jAssing.com>
> wrote:
>
>>>I have a great idea. Don't use a formset. It was a bad idea (read: really
>>>really stupid idea omg Microsoft wtf were you thinking?) that should
>>>have
>>>never been implemented in VFP. Figure out a way to do what you want
>>>without
>>>formsets.
>>
>>Formsets were kept as part of "backward compatibility" to FPW...
>>MS didn't invent it; and they've stuck (pretty much) to "leave existing
>>functionality".
>>
>>
>>--- AntiSpam/harvest ---
>>Remove X's to send email to me.

Imaginecorp
Sat Feb 11 13:51:00 CST 2006

Sorry about the formatting...

"Imaginecorp" <imaginecorp@msn.com> wrote in message
news:OB8QJM0LGHA.2320@TK2MSFTNGP11.phx.gbl...
> Hello Jacob;
>
> Design your child forms
>
> Set their DataSession to 1 - Default Data Session
>
>
>
> In the Init event insert the following code
>
>
>
> LParameters pWhoCalled,pDatasessionID
>
>
>
> You can call them whatever you want
>
> (pdatasessionID, even though not needed, I do it just to be extra safe in
> case another form is opened )
>
>
>
> With this
>
> .addproperty("oWhoCalled",pWhoCalled)
>
> .datasessionid = pDatasessionID
>
> <<other code>>
>
> Endwith
>
>
>
> Now you have Total control over the parentform with Thisform.oWhoCalled.
>
>
>
> Your parent form should send these 2 parameters i.e. Do form myform with
> thisform,thisform.datasessionID
>
>
>
> Now you can acess tables, properties and methods, even controls on the
> parentform from the child forms.
>
>
>
> Tip: I would create the child form as Modal, to ovoid them being orphaned
> if the parent form is closed unless you Link them to the Parent, then they
> will also close when the parent is closed. This also prevents the user
> form "wandering" to other stuff that might be open
>
>
>
> Good luck
>
> Mohammed
>
> www.imaginecorp.com/whatwedo.htm
>
>
>
> "Jacob" <jStoddard@hotMailCCC.com> wrote in message
> news:l1lqu1pv0ulnbkeagvneaf4egkaak8q047@4ax.com...
>> Enough said then. Need to figure out how to do this with a bunch of
>> forms that talk to one another.
>>
>> On Fri, 10 Feb 2006 18:16:36 -0800, Josh Assing <XjoshX@jAssing.com>
>> wrote:
>>
>>>>I have a great idea. Don't use a formset. It was a bad idea (read:
>>>>really
>>>>really stupid idea omg Microsoft wtf were you thinking?) that should
>>>>have
>>>>never been implemented in VFP. Figure out a way to do what you want
>>>>without
>>>>formsets.
>>>
>>>Formsets were kept as part of "backward compatibility" to FPW...
>>>MS didn't invent it; and they've stuck (pretty much) to "leave existing
>>>functionality".
>>>
>>>
>>>--- AntiSpam/harvest ---
>>>Remove X's to send email to me.
>
>

Paul
Mon Feb 13 13:03:58 CST 2006

I have tried a few times over the years to make use of formsets. Every time
I abandoned them as a huge pia, not nearly worth the trouble. I thought
there was something wrong with me, that I couldn't figure out how to make
them useful.

Just think how many work hours around the world Microsoft would have saved
everyone if they had just put a note in the Help file that formsets were for
backward compatibility only, and were not recommended for new development in
VFP.

Just one simple sentence would have saved many thousands of man-hours! What
were they thinking when they left that out??



"Jacob" <jStoddard@hotMailCCC.com> wrote in message
news:a4cqu1ts6njpb5hpq2l2015s78i2bs05bt@4ax.com...
> So tell me why formsets are not a good idea. Granted I have been
> doing Foxpro for a really long time, and have never used them, but
> this seemed appropriate.
>
> The app is the same on all boxes. I am storing the record number from
> FORM2 to THISFORMSET.recNo and then GO to that record before making
> FORM3 visible.
>
> I agree, uninstalling doesn't solve much. I noticed after
> reinstalling that all the settings for foxpro were the same.
>
>
> On Fri, 10 Feb 2006 16:11:54 -0800, "Matthew L Reed" <nousenetspam at
> dead ice dot us> wrote:
>
>>I have a great idea. Don't use a formset. It was a bad idea (read: really
>>really stupid idea omg Microsoft wtf were you thinking?) that should have
>>never been implemented in VFP. Figure out a way to do what you want
>>without
>>formsets.
>>
>>However, if you are determined to keep using formsets (and I suspect your
>>problem has nothing to do with the fact that you are using
>>formsets)...Make
>>sure you really are running the same version of the same app with the same
>>data on both machines. Unless someone here has a better idea, I'd trace
>>the
>>code that selects the detail record, and see what it is doing when it is
>>not
>>displaying the correct record.
>>
>>PS: Uninstalling/reinstalling VFP does not fix things that can break, nor
>>does it remove registry settings. I've had VFP break several times, and
>>uninstall/reinstall never fixed anything.
>>
>>"Jacob" <jStoddard@hotMailCCC.com> wrote in message
>>news:ke9qu192gnlrgb0k2ft4g19u5h8q77s9lc@4ax.com...
>>>I am using something new for me, a FORMSET. Problem is, it does not
>>> behave the same on my home development box as it does on my other
>>> boxes.
>>>
>>> 1. FORM1 in formset, lets a user select the customer, then brings up a
>>> grid on FORM2.
>>>
>>> 2. User nows selects a customer detail record and presses a button to
>>> make FORM3.visible, which should display information in textbox's
>>> based on the current record.
>>>
>>> Two XP Professional/SP2 boxes on INTEL show the correct record on
>>> FORM3.
>>>
>>> My new XP Media Center Edition/SP2 on AMD Athlon 64 will not display
>>> the correct record.
>>>
>>> This new XP Media Center box is also the same box where Foxpro 9/SP1
>>> will not ask if I want to overwrite the existing .exe when rebuilding.
>>> I even Uninstalled and Reinstalled today, but getting the same
>>> results.
>>>
>>> This is really frustrating trying to get this stuff working, when the
>>> behavior is different on different PC's. Anybody got any ideas?????
>>>
>>> Thanks for your help
>>>
>>

Jacob
Tue Feb 14 18:26:07 CST 2006

I was going to say that I looked at the Help file and didn't see the
reference you mentioned, which is why I contained playing with the
formset.

Oh well...

On Mon, 13 Feb 2006 11:03:58 -0800, "Paul Pedersen"
<no-reply@swen.com> wrote:

>I have tried a few times over the years to make use of formsets. Every time
>I abandoned them as a huge pia, not nearly worth the trouble. I thought
>there was something wrong with me, that I couldn't figure out how to make
>them useful.
>
>Just think how many work hours around the world Microsoft would have saved
>everyone if they had just put a note in the Help file that formsets were for
>backward compatibility only, and were not recommended for new development in
>VFP.
>
>Just one simple sentence would have saved many thousands of man-hours! What
>were they thinking when they left that out??
>
>
>
>"Jacob" <jStoddard@hotMailCCC.com> wrote in message
>news:a4cqu1ts6njpb5hpq2l2015s78i2bs05bt@4ax.com...
>> So tell me why formsets are not a good idea. Granted I have been
>> doing Foxpro for a really long time, and have never used them, but
>> this seemed appropriate.
>>
>> The app is the same on all boxes. I am storing the record number from
>> FORM2 to THISFORMSET.recNo and then GO to that record before making
>> FORM3 visible.
>>
>> I agree, uninstalling doesn't solve much. I noticed after
>> reinstalling that all the settings for foxpro were the same.
>>
>>
>> On Fri, 10 Feb 2006 16:11:54 -0800, "Matthew L Reed" <nousenetspam at
>> dead ice dot us> wrote:
>>
>>>I have a great idea. Don't use a formset. It was a bad idea (read: really
>>>really stupid idea omg Microsoft wtf were you thinking?) that should have
>>>never been implemented in VFP. Figure out a way to do what you want
>>>without
>>>formsets.
>>>
>>>However, if you are determined to keep using formsets (and I suspect your
>>>problem has nothing to do with the fact that you are using
>>>formsets)...Make
>>>sure you really are running the same version of the same app with the same
>>>data on both machines. Unless someone here has a better idea, I'd trace
>>>the
>>>code that selects the detail record, and see what it is doing when it is
>>>not
>>>displaying the correct record.
>>>
>>>PS: Uninstalling/reinstalling VFP does not fix things that can break, nor
>>>does it remove registry settings. I've had VFP break several times, and
>>>uninstall/reinstall never fixed anything.
>>>
>>>"Jacob" <jStoddard@hotMailCCC.com> wrote in message
>>>news:ke9qu192gnlrgb0k2ft4g19u5h8q77s9lc@4ax.com...
>>>>I am using something new for me, a FORMSET. Problem is, it does not
>>>> behave the same on my home development box as it does on my other
>>>> boxes.
>>>>
>>>> 1. FORM1 in formset, lets a user select the customer, then brings up a
>>>> grid on FORM2.
>>>>
>>>> 2. User nows selects a customer detail record and presses a button to
>>>> make FORM3.visible, which should display information in textbox's
>>>> based on the current record.
>>>>
>>>> Two XP Professional/SP2 boxes on INTEL show the correct record on
>>>> FORM3.
>>>>
>>>> My new XP Media Center Edition/SP2 on AMD Athlon 64 will not display
>>>> the correct record.
>>>>
>>>> This new XP Media Center box is also the same box where Foxpro 9/SP1
>>>> will not ask if I want to overwrite the existing .exe when rebuilding.
>>>> I even Uninstalled and Reinstalled today, but getting the same
>>>> results.
>>>>
>>>> This is really frustrating trying to get this stuff working, when the
>>>> behavior is different on different PC's. Anybody got any ideas?????
>>>>
>>>> Thanks for your help
>>>>
>>>
>