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
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 ad
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
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,
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 Messag
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@leaf
6 matches
Mail list logo
