Justin's interpretations of my email are correct. For the record, here's
the error handler:
So, yeah, nothing exciting there.
I posted my code because I'm not confidant in it. I don't remember when I
wrote it and I haven't kept up with all of the various permutations on
> On Mon, Jul 17, 2017 at 6:50 AM, Julio Carneiro via 4D_Tech <
> Correct, David, you got the gist of my comment.
> Jim Hays gave a great example where I can see object fields excel. If
> requires user defined fields, then an object field is just perfect for
On 17 Jul 2017, at 5:07 am, Robert Livingston via 4D_Tech
> On Jul 14, 2017, at 5:10 PM, David Adams via 4D_Tech <email@example.com>
>> I was just consolidating some old code and ran across something that I
>> wrote some time back called
Here's a quick tip if you suddenly loose the buttons at the bottom of
your Explorer window, as I did this afternoon -- I couldn't view method
Comments (no Preview/Comments button), nor could I Add [+] or Delete
[-] methods etc -- those options were just not available to me.
the command is called Print form, it can not be more obvious!
> 2017/07/17 6:26、Robert Livingston via 4D_Tech <firstname.lastname@example.org> のメール：
> Is it possible to print a project form?
Is it possible to print a project form?
When I review the "print" functions, they always seem to refer to table forms.
I suppose I can use some table form in some "pseudo table" for what I am trying
to do, but it would be more straight-forward if I could just print a project
Correct, David, you got the gist of my comment.
Jim Hays gave a great example where I can see object fields excel. If your app
requires user defined fields, then an object field is just perfect for that.
I’ve had similar situations in the past and used tab-separated text fields
first, and then
When David writes I generally find it very clear if it is discussing something
that is basic enough for me to have a chance to understand in the first place.
But I found this message a little confusing and yet sets seem to be a fairly
> On Jul 14, 2017, at 5:10 PM, David Adams
We tried using two different Wiki solutions for internal documentation and
external documentation (back in the 90s). We found them to be too loose -
permitted almost anything or nothing. Therefore we could not enforce
completeness (as much as one can) of documentation and very fast finding of
Mail list logo