One of my deployed 4D server has suddenly started throwing this error (see
below). When the error is being displayed 4D server is not visible. When the ok
button is clicked 4D server becomes visible.
A quick google search finds some discussion about this error independent of 4D
and one
Tim:
Hear hear!
--
Douglas von Roeder
949-336-2902
On Wed, Mar 13, 2019 at 2:03 PM Tim Nevels via 4D_Tech <4d_tech@lists.4d.com>
wrote:
> LinkedIn sent out an email today that Doris Beaulieu has worked for 4D for
> 31 years, since March 1988. I’ve never known a time when she were not at
> 4D.
Congratulations Doris!
--
--
Tom Dillon 375 S Main St #405
DataCraft Moab, UT 84532
tomdil...@datacraft-inc.com
Happy Anniversary Doris!
> On Mar 13, 2019, at 2:02 PM, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> LinkedIn sent out an email today that Doris Beaulieu has worked for 4D for 31
> years, since March 1988. I’ve never known a time when she were not at 4D.
> Always there to greet
I agree. Pretty hard to believe she made it all this way working for so many
along the way. She must have started when she was still a young teenager
Regards and congrats to her
Chuck
Chuck Miller
Hi Everyone,
I’m trying to do some quick and dirty logging to track down an issue at a
customer’s site. As part of that I need to log some information to a file,
always on the server. I figured the simplest would be to call a method each
time I need to log some information and pass the info to
LinkedIn sent out an email today that Doris Beaulieu has worked for 4D for 31
years, since March 1988. I’ve never known a time when she were not at 4D.
Always there to greet developers and 4D Partners at every 4D Summit too.
Congratulations! I hope they give her a party or something at 4D. She
Miyako,
It looks like you just step through all the objects and offset and print
them, so I'm trying that...
Alan
On Wed, Mar 13, 2019 at 1:16 PM Alan Tilson wrote:
> Hello Miyako,
> Ok, I'm back to this project.
> Thanks for the info and I'm working with the Print Object command, trying
> to
Thanks Chuck. I'm not concerned about the Active4D part at this time. It seemed
like in the past there was an issue where you wouldn't be allowed to open the
structure after moving between machines or server -> client. I'll be at their
site tomorrow and will try your suggestion.
Brad
On
I definitely agree that 4D's new internal processes and continuous delivery
model have improved product quality a LOT. There's no way I would have ever
considered putting a .0 release into production, but we did just that with
v17.0.
> On Mar 13, 2019, at 9:02 AM, GI -AJAR via 4D_Tech
Hi,
For me too it is not confusing. Actually to call it V17 beta is not only more
confusing but it is wrong.
Actually you can see v17 as a 16 R7 if you like.
R release make it easier to go through the new features 4D implement by having
them little by little instead to have a full load of
It's really not that hard, nor that unusual.
Is Windows Server 2008R2 a beta of Windows Server 2012? Nope. It's an
incremental release with new features.
> On Mar 13, 2019, at 6:14 AM, Bernd Fröhlich via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> Maybe all the folks at 4D understand how
> On Mar 13, 2019, at 11:14 AM, Bernd Fröhlich via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> Milan Adamov:
>
>> But there not announced as v16 features, that is simply not true, no one
>> ever said that. On the contrary, it is explicitly said and written many
>> times that those features
Milan Adamov:
> But there not announced as v16 features, that is simply not true, no one ever
> said that. On the contrary, it is explicitly said and written many times that
> those features are upcoming features in next major version.
So it IS a V17 beta after all...
Maybe all the folks at
> On Mar 13, 2019, at 10:06 AM, Jim Dorrance via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> On Wed, Mar 13, 2019 at 9:51 AM Milan Adamov via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
>
>>
>> No, it would just add more confusion and it wouldn’t be accurate.
>
>
> I do not agree. The problem
On Wed, Mar 13, 2019 at 9:51 AM Milan Adamov via 4D_Tech <
4d_tech@lists.4d.com> wrote:
>
> No, it would just add more confusion and it wouldn’t be accurate.
I do not agree. The problem is a final client has bought a v16 version but
does not have access to features announced and touted as v16
> On Mar 13, 2019, at 8:22 AM, Bernd Fröhlich via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> Good Idea.
> v16R6 should really be called V17Beta6. That´s what it is after all.
> Would save a lot of confusion.
No, it would just add more confusion and it wouldn’t be accurate. First, v17
means
Hi Doug,
Perhaps a typo, but you actually need the Developer license to be able to go to
design mode. the Unlimited Desktop license is the one you need to include if
you build single user apps.
HTH
Koen
> Op 12 mrt. 2019, om 23:49 heeft Doug Hall via 4D_Tech <4d_tech@lists.4d.com>
> het
Thanks
Ferdinando
Il 12/03/2019 20:00, 4d_tech-requ...@lists.4d.com ha scritto:
Message: 5
Date: Tue, 12 Mar 2019 16:11:11 +0100
From: Jim Dorrance
To: 4D iNug Technical<4d_tech@lists.4d.com>
Subject: Re: 4D V16 R6 Vs 4D V16.5
Message-ID:
Content-Type: text/plain; charset="UTF-8"
Jim Dorrance:
> Wouldn't it be less confusing if 4D called v16 R6 something other
> than v16 , because the v16 R6 new features will never be released in a v16
> upgrade.
Good Idea.
v16R6 should really be called V17Beta6. That´s what it is after all.
Would save a lot of confusion.
Greetings
20 matches
Mail list logo
