Re: Form designer rules?

2021-05-26 Thread Alan Bourke
On Mon, 24 May 2021, at 3:54 PM, Eric Selje wrote:

> I know you're all probably tired of hearing this drumbeat, but having SQL
> statements in UI controls is a bad idea. Do what you can to separate that
> out.

I agree.

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: 
https://leafe.com/archives/byMID/24b7400d-109b-470b-8ece-451144d8b...@www.fastmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.


RE: Form designer rules?

2021-05-26 Thread Tracy Pearson
I admit, I prefer to not use the UI controls that way. 
I also admit that I'm an enabler, and if people want to use the controls
that way I help. 
I should probably start adding something like: You could do it that way,
though it may not be as maintainable if you did X.

Tracy

-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Alan
Bourke
Sent: Wednesday, May 26, 2021 8:42 AM
To: profoxt...@leafe.com
Subject: Re: Form designer rules?

On Mon, 24 May 2021, at 3:54 PM, Eric Selje wrote:

> I know you're all probably tired of hearing this drumbeat, but having SQL
> statements in UI controls is a bad idea. Do what you can to separate that
> out.

I agree.

[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: 
https://leafe.com/archives/byMID/000301d75241$8b42ed50$a1c8c7f0$@powerchurch.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.


Re: Form designer rules?

2021-05-26 Thread Jean Laeremans
You're forgiven.

On Wed, May 26, 2021 at 5:13 PM Tracy Pearson  wrote:

> I admit, I prefer to not use the UI controls that way.
> I also admit that I'm an enabler, and if people want to use the controls
> that way I help.
> I should probably start adding something like: You could do it that way,
> though it may not be as maintainable if you did X.
>
> Tracy
>
> -Original Message-
> From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Alan
> Bourke
> Sent: Wednesday, May 26, 2021 8:42 AM
> To: profoxt...@leafe.com
> Subject: Re: Form designer rules?
>
> On Mon, 24 May 2021, at 3:54 PM, Eric Selje wrote:
>
> > I know you're all probably tired of hearing this drumbeat, but having SQL
> > statements in UI controls is a bad idea. Do what you can to separate that
> > out.
>
> I agree.
>
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: 
https://leafe.com/archives/byMID/CAPqLOBwWZEBPvs6A1FsO=SNVkUkrsV91O=yqfjzmjovhr6+...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.


Formset goofy

2021-05-26 Thread Joe Yoder
I have been working with two forms in a formset for the first time.  All
has worked out well as the two forms are simply two perspectives on the
underlying data. I switch between them by turning visible on and off.

One of the forms somehow got set to max width in the development
environment.  This is a nuisance to work with but I didn't bother to fix it
until this morning.  My fix was to scroll to the right bound of the screen
and drag the right side of the screen to the left as far as I could and
then repeat.  This made it much easier to switch between the forms.

In the same session I deleted a series of controls from form2 and replaced
them with new ones.  When I built the formset form 1 no longer has any
controls showing up either in the form designer or when running the form.

I Investigated and at least some of the form1 controls are still in the
,SCX.

Actually I checked details in the Properties of the Formset for the missing
form and discovered the Left setting was -1946 while the same setting for
the present form was 8.  Setting the negative value to 8 restored the
missing controls.  I'm quessing I inadvertently garbed the whole form
rather than the right bound when I was making the screen narrower.

Now my question is - is there a one click solution in the UI to correct
this situation or is manual editing of the properties the best approach?

Thanks in advance,

Joe


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: 
https://leafe.com/archives/byMID/cabqednudlaa-ajhqout_9okaut0d1abnbhxn7ws030nbbbf...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.


RE: Formset goofy

2021-05-26 Thread Tracy Pearson
My work with formsets never got past the "learning" stage. Meaning I never
put one into a production application.

There are some bits that one really needs to understand to work with them.
Like common code between them with thisformset.
It's a big learning curve to use them. And most people are advised to not
use them.

The notion of having a scrollable area on one form by using the scrollbar
setting on a second form set on top of the first form was the latest
tinkering I did. Someone made a container class that emulates that
functionality though.

If one form is the main form, it can start the secondary form. The main form
would be set to a Private Datasession. The secondary form would not be a
private datasession. This will allow the secondary form to see and use the
main forms tables and views. 

Why are you wanting to use a formset? I'm sure there are valid reasons to
use them. 

Tracy

-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Joe
Yoder
Sent: Wednesday, May 26, 2021 5:29 PM
To: profoxt...@leafe.com
Subject: Formset goofy

I have been working with two forms in a formset for the first time.  All
has worked out well as the two forms are simply two perspectives on the
underlying data. I switch between them by turning visible on and off.

One of the forms somehow got set to max width in the development
environment.  This is a nuisance to work with but I didn't bother to fix it
until this morning.  My fix was to scroll to the right bound of the screen
and drag the right side of the screen to the left as far as I could and
then repeat.  This made it much easier to switch between the forms.

In the same session I deleted a series of controls from form2 and replaced
them with new ones.  When I built the formset form 1 no longer has any
controls showing up either in the form designer or when running the form.

I Investigated and at least some of the form1 controls are still in the
,SCX.

Actually I checked details in the Properties of the Formset for the missing
form and discovered the Left setting was -1946 while the same setting for
the present form was 8.  Setting the negative value to 8 restored the
missing controls.  I'm quessing I inadvertently garbed the whole form
rather than the right bound when I was making the screen narrower.

Now my question is - is there a one click solution in the UI to correct
this situation or is manual editing of the properties the best approach?

Thanks in advance,

Joe


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: 
https://leafe.com/archives/byMID/001601d7527b$0f7c7a30$2e756e90$@powerchurch.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.


Re: Formset goofy

2021-05-26 Thread Joe Yoder
I came across the possibility and it fit my goal to do a minimum proof of
concept system.  The forms consist of Pick which allows choosing a record
and Detail which then supplies additional info.

I have no intention to use a scrollable form.  Maybe what happened to me
can only occur when there is a formset.  I thought it is a part of the
development environment and I assumed it can happen with any form.

On Wed, May 26, 2021 at 6:04 PM Tracy Pearson  wrote:

> My work with formsets never got past the "learning" stage. Meaning I never
> put one into a production application.
>
> There are some bits that one really needs to understand to work with them.
> Like common code between them with thisformset.
> It's a big learning curve to use them. And most people are advised to not
> use them.
>
> The notion of having a scrollable area on one form by using the scrollbar
> setting on a second form set on top of the first form was the latest
> tinkering I did. Someone made a container class that emulates that
> functionality though.
>
> If one form is the main form, it can start the secondary form. The main
> form
> would be set to a Private Datasession. The secondary form would not be a
> private datasession. This will allow the secondary form to see and use the
> main forms tables and views.
>
> Why are you wanting to use a formset? I'm sure there are valid reasons to
> use them.
>
> Tracy
>
> -Original Message-
> From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Joe
> Yoder
> Sent: Wednesday, May 26, 2021 5:29 PM
> To: profoxt...@leafe.com
> Subject: Formset goofy
>
> I have been working with two forms in a formset for the first time.  All
> has worked out well as the two forms are simply two perspectives on the
> underlying data. I switch between them by turning visible on and off.
>
> One of the forms somehow got set to max width in the development
> environment.  This is a nuisance to work with but I didn't bother to fix it
> until this morning.  My fix was to scroll to the right bound of the screen
> and drag the right side of the screen to the left as far as I could and
> then repeat.  This made it much easier to switch between the forms.
>
> In the same session I deleted a series of controls from form2 and replaced
> them with new ones.  When I built the formset form 1 no longer has any
> controls showing up either in the form designer or when running the form.
>
> I Investigated and at least some of the form1 controls are still in the
> ,SCX.
>
> Actually I checked details in the Properties of the Formset for the missing
> form and discovered the Left setting was -1946 while the same setting for
> the present form was 8.  Setting the negative value to 8 restored the
> missing controls.  I'm quessing I inadvertently garbed the whole form
> rather than the right bound when I was making the screen narrower.
>
> Now my question is - is there a one click solution in the UI to correct
> this situation or is manual editing of the properties the best approach?
>
> Thanks in advance,
>
> Joe
>
>
> --- StripMime Report -- processed MIME parts ---
> multipart/alternative
>   text/plain (text body -- kept)
>   text/html
> ---
>
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: 
https://leafe.com/archives/byMID/cabqednu1lrev8uuxwapkoww_6ettkva8grgzptat1ydpaeq...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.