Miyako,
Yes, the expression is correctly evaluated and displayed; if it wasn’t, I would
have used a rather stronger word than “infelicity”! Thanks for the explanation
of what’s happening (wrapping).
> On 14 May 2019, at 20:43, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> th
I agree with Pat. Orda is a massive change and JPR really does make it quite
clear where the future is. Plus the resources included are great value for
money.
Paul
--
Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html
The issue with the design windows all closing was fixed in one R version
but it seems to have reappeared. I'm on R5 and it SOMETIMES (randomly) does
this.
I've submitted a bug report (99591).
PB
On Wed, 15 May 2019 at 08:37, Jeremy Roussak via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Miyako,
>
>
John:
"And "$wpDoc:=WP New” generates the same error.”
OK, understood. That’s an error because it should be returning a 4DWP
object.
My question about passing an empty BLOB stems from the docs which indicate
that you can’t pass a parameter that doesn’t have content. I suspect that
would give an e
Hi Doug,
The License manager clearly shows 4D Developer Professional v17 - Partner
Program … which includes 1 (unlimited)4D Write - 4D Write Pro license.
So I’m not sure what I am doing wrong?
In edition to why 4D Write Pro is returning the license error I’m a little
confused about 4D Write P
Hi All,
There’s an implied assumption that Migrating 4d-write documents stored in
picture fields will work using the v17 component. I didn't see any caveats as
to preparing 4D Wrote docs in earlier versions.
So, as Randy offered, maybe that’s the correct path. Maybe I should change the
docs in
Hi John,
Video Tip: Converting 4D Write documents to 4D Write Pro
https://kb.4d.com/assetid=77703
Here is the section about converting 4D Write documents stored in Picture
fields.
https://youtu.be/nc6JMNanv58?t=120
Here is the process you need to follow:
https://youtu.be/nc6JMNanv58?t=163
-Ti
Hey Tim,
Thanks helpful!
OK, so I need to get the Write docs into v7 format before migrating to 4D Write
Pro object format.
Based upon these v16 videos can I migrate from within 4D v17?
Or do I need to convert in an earlier version?
And if I can convert in 4D v17 (windows or Mac) then it appe
You will need to use 32 bit. Are you using 32 bit?
-Tim
-Original Message-
From: John J Foster
Sent: Wednesday, May 15, 2019 9:00 AM
To: Timothy Penner
Cc: 4D iNug Technical <4d_tech@lists.4d.com>
Subject: Re: Migrating 4D Write Pictures to 4D Write Pro Objects
Hey Tim,
Thanks help
Well said Pat
Having been a 4D developer for 30 odd years I've been to several of JPRs
training sessions and always come away having learnt something valuable.
Well wort the cost.
On the train home from the London World Tour I re-designed our old record
change auditing system.
Entities and ORDA
John,
Do you have the old 4DWrite plugin installed? If so, try removing that,
restart 4D, and see if it makes any difference.
PB
On Wed, 15 May 2019 at 16:20, John J Foster via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Hi Doug,
>
> The License manager clearly shows 4D Developer Professional v17 -
Hi Tim,
I’m guessing not since I went back on the downed site and relaxed that the
first download is 64bit and that you have to search and click into another link
which then opens the ftp download page to find the 32bit versions.
I am presently doing this and will try this again …
BTW, the vid
On May 15, 2019, at 11:04 AM, Pat Bensky wrote:
> The issue with the design windows all closing was fixed in one R version
> but it seems to have reappeared. I'm on R5 and it SOMETIMES (randomly) does
> this.
> I've submitted a bug report (99591).
I’ve never used this preference. I drop in and ou
Hi All,
I am testing on a MAC OSX 10.12.6. When I run 64 bit version of 17.1 it crashes
immediately. When I run 32 bit version, it runs. Any ideas as to why this is
happening
Regards
Chuck
Chuck M
Hi Chuck,
I would suggest looking at the Crash Report (dot crash file) that is created by
the MacOS Operation System. This usually provides additional clues. It can be
found within the Console application.
If it is crashing when creating brand new structure than you could contact 4D
Tech Suppo
could there be a non 64 bit compliant plugin or component?
On Wed, 15 May 2019 12:27:35 -0400, Chuck Miller via 4D_Tech wrote:
> Hi All,
>
> I am testing on a MAC OSX 10.12.6. When I run 64 bit version of 17.1
> it crashes immediately. When I run 32 bit version, it runs. Any ideas
> as to why t
On May 14, 2019, at 4:40 PM, Chris Belanger via 4D_Tech <4d_tech@lists.4d.com>
wrote:
> So my main question is:
> Is it possible to COPY Interface Elements and then PASTE them into 4D’s FORM
> EDITOR?
>
> My idea is to:
> 1) have a subform on the FORM DESIGN TOOL that uses FORM DATA (i.e.
> in
4D Tech mailing list wrote
> Hi All,
>
> 4D v17R4 Windows and Macintosh Stand alone and 4D Server
> I do not have an old 4D Write plugin only the new 4D Write Pro
> App upgraded from 4D 2012 to 4D V17
>
> I am working on the final v17 conversion piece migrating older 4D Write
> saved in picture f
Aloha,
Super weird issue. I’m trying to do a simple $ format in a variable on a
dialog. Choosing a number format of "$###,##0.00” doesn’t display properly. I
enter “50”, I get $0.50. Even when using this:
OBJECT SET FORMAT(*;"ShippingCost";"$###,##0.00”)
But in the same dialog, if I do the same
did you check:
Use period and comma as placeholders in numeric formats:
?
https://doc.4d.com/4Dv15/4D/15.6/Compatibility-page.300-3836777.en.html
**
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.htm
how did you decide that the variable is numeric?
did you use C_REAL or C_LONGINT?
what does the debugger/runtime explorer say?
the value type in property list does not set the variable type except for form
local variables.
https://doc.4d.com/4Dv17/4D/17.1/Variables.300-4179325.en.html
2019/05
21 matches
Mail list logo
