Re: 4D v16.2 false record locks

On Oct 6, 2017, at 6:04 PM, David Adams wrote: > Again: > > Start worker > Open file. > Use file > Close file. > Kill worker > > Start worker again > *** FIle lock conflict *** > > 4D's accepted it as a bug as of some months back. I finally now understand the bug you found. Thanks for finally

Re: 4D v16.2 false record locks

Hey John, Thanks again for trying. I kill the worker from *within* the worker *after* closing the file. It *usually* works. But "usually" is worthless when the consequences of it not working are a dead server. 4D has accepted it as a bug in, I think 16.0. they just haven't fixed it. For now,

Re: How do workers die?

> > Perhaps I am misunderstanding your question. Do you mean after a worker > has been killed with KILL WORKER? > Clearly, I asked my question poorly as you and Julio both found my question unclear in the same way. (Or perhaps it's just that it's unclear to people who can speak Portuguese?) In

Re: How do workers die?

Julio, Thanks for taking a stab at it. I should have been more clear, I mean when workers are killed. I do this from within the worker to try and have an orderly shutdown. Your reading of the docs is correct though. Workers are a thread of execution, like any other process, but 4D has its own

Re: What happened to 4D documentation in R releases - found some of them

It turns out you can still get the upgrade manuals for v14R and v15R here: ftp://ftp-public.4d.fr/Documents/Products_Documentation/ But no such luck for v16R. For these, just bug fixes. Please 4D, give us real reference manuals for

Re: 4D v16.2 false record locks

OOOPS! In my last example with the worker killing itself there should only be one line… CALL WORKER(“worker”;”LogSomething”) //worker opens the file/logs something to the file/closes the file/Kills itself Don’t need to kill the process again. John > On Oct 6, 2017, at 12:32 PM, John

Re: What happened to 4D documentation in R releases?

Ad, The blogs are fine and are helpful but they’re no substitute for a proper reference of changes for each version. It’s really important for us to be able to clearly and easily see which changes are in each R version, not just major versions. And you can’t do this from the blog. Jeremy

Re: 4D v16.2 false record locks

Hi David, How/when are you killing the worker. You must give the worker time to close the file. This will not work… CALL WORKER(“worker”;”LogSomething”) //worker opens the file/logs something to the file/closes the file KILL WORKER(“worker”) The worker will be killed before it

Re: What happened to 4D documentation in R releases?

I couldn’t agree more. Each version needs it’s own document that lists it’s changes. I also agree about keeping an archive of documentation for each R release. There’s new stuff in each one, that’s the whole point, and an R release is no different than a major version release - once you get to

Re: What happened to 4D documentation in R releases?

Thanks, Jeremy, that’s a big help. > Date: Fri, 06 Oct 2017 12:20:56 -0400 > From: Jeremy French > > Hi Richard, > > There is a link titled “What’s New”. > > This link appears **only** when you view the Language Reference “Table of > Contents”.That’s the page that

Re: 4D v16.2 false record locks

Again: Start worker Open file. Use file Close file. Kill worker Start worker again *** FIle lock conflict *** 4D's accepted it as a bug as of some months back. ** 4D Internet Users Group (4D iNUG) FAQ:

Re: 4D v16.2 false record locks

Hey Chip, thanks or chiming in. I've always been disciplined about opening and closing files on my own, I have no idea what 4D's defaults are on this...or if there is even a documented (promised) behavior. The traces of old, dead workers I was referring to *might* not actually exist and that

Re: Create multi array

Thank to all /Ferdinando/ Il 06/10/2017 17:48, 4d_tech-requ...@lists.4d.com ha scritto: Message: 1 Date: Fri, 06 Oct 2017 10:16:04 +0100 From: Jeremy Roussak To: 4D iNug Technical<4d_tech@lists.4d.com> Subject: Re: Create multi array

Re: [offish]Volume of mail

> On Oct 06, 2017, at 11:48 AM, 4d_tech-requ...@lists.4d.com wrote: > > From: Peter Jakobsson > > To: 4D iNug Technical <4d_tech@lists.4d.com > > Subject: Re: [offish]Volume of mail > > >> On 5 Oct 2017, at 21:15,

RE: What happened to 4D documentation in R releases?

> From: Michael McCall > > To: 4D iNug Technical <4d_tech@lists.4d.com > > > Hi Richard, > > I think the documentation is available if I understand your question. I find > it for R4 at: > >

Re: What happened to 4D documentation in R releases?

> Le 6 oct. 2017 à 17:48, Michael McCall via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Hi Richard, > > I think the documentation is available if I understand your question. I find > it for R4 at: Michael, I think Richard complains about v16r2 and r3 tabs, they're gone from the main

Re: What happened to 4D documentation in R releases?

Hi everyone, I can understand the confusion. The format on the documentation page is a bit different these days. There are 2 sections you want to look for from the main documentation page. Under Core Documentation section, you’ll find “4D v16 R4 – Upgrade” and “Deprecated and Removed Features”

Re: 4D v16.2 false record locks

you cut out the first part : while doing testing :) I revert to local or process (as appropriate) in final version On Fri, 6 Oct 2017 06:59:30 -1000, John Baughman wrote: >> >> I do this: >> <>Doc_Ref:=Open Document > > > Great idea. That is unless you think global variables are evil ;-)

Re: 4D v16.2 false record locks

> On Oct 6, 2017, at 6:24 AM, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I do this: > <>Doc_Ref:=Open Document Great idea. That is unless you think global variables are evil ;-) As any one working in 4D for any length of time knows, you have to close a document as soon as

Re: What happened to 4D documentation in R releases?

I’m looking for the documentation of new features and other upgrade info. All they have in the doc center for this is a link to their blog which is not the same thing at all. > Date: Fri, 6 Oct 2017 15:48:23 + > From: Michael McCall > > Content-Type:

RE: What happened to 4D documentation in R releases?

Yes, v16 brings a somewhat frustrating "new" approach to documentation. In fact, I postponed looking at v16 until there were PDF docs, which were not released until several _months_ after v16 came out (there were html docs, but no PDF docs). I am also frustrated by how the documentation has

Re: oh sweet

> On 6 Oct 2017, at 17:54, Nigel Greenlee via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > How long have i wanted this…. +1 Nigel ! ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive:

Re: 4D v16.2 false record locks

David, my experience with file locks - not concurrently (in as much as you are trying to do), but generically while trying to read/write/ etc disk files: I do not do this when testing any more $Doc_ref:=Open Document I do this: <>Doc_Ref:=Open Document Why? because when the process that

Re: What happened to 4D documentation in R releases?

Hi Richard, There is a link titled “What’s New”. This link appears **only** when you view the Language Reference “Table of Contents”.That’s the page that appears after choosing Language Reference for a specific version of 4D. Snapshot of Language Reference’s “Table of Contents"

Re: How do workers die?

On Oct 5, 2017, at 11:06 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com> wrote: > > * New process () / Execute on server () When they finish, they're dead. > They're supposed to release file locks, record locks, etc. If you start a > new copy of the process with the same name, it starts off

oh sweet

All How long have i wanted this…. https://blog.4d.com/passing-data-back-and-forth-between-forms/?utm_content=buffer15244_medium=social_source=twitter.com_campaign=buffer joy joy joy of 4D Nigel Greenlee ** 4D Internet

RE: What happened to 4D documentation in R releases?

Hi Richard, I think the documentation is available if I understand your question. I find it for R4 at: http://doc.4d.com/4Dv16R4/index.en.html Hope this helps. Mike ** 4D Internet Users Group (4D iNUG) FAQ:

What happened to 4D documentation in R releases?

I’m trying to get the upgrade documentation for v16 R2-R4. The only thing that I can find in the doc center is a link to their blog for new features in v16R4. It’s really annoying that I seemingly can’t download or even view online a single document for each version that lists what’s new. There

Re: How do workers die?

Well, documentation says Workers don’t die. You have to kill them, or quit 4D. From 4D 16.2 Docs, About Workers page: "Unlike the New process command, a worker process remains alive after the execution of the process method ends.” Web process stay dormant for awhile and then die if no new

Re: [offish]Volume of mail

> Le 5 oct. 2017 à 22:35, Richard Wright via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Perhaps it’s partially due to the fact that some post mysteriously never get > through and also do not bounce back. [...] Apple mail uses the currently selected account (or something like that) and I

Re: [offish]Volume of mail

> On 5 Oct 2017, at 21:15, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > We have a lot of 4D developers working here, but I'm on the only who > participates actively in the list. Also, 4D has a lot fewer "issues" these > days than in the old days. I’m probably in this category

Re: [offish]Volume of mail

I am relatively new to this list so I do not have a perspective on past history but I read the emails every day and have found the list extremely helpful. I have posted a few questions and received helpful advice. I find it much easier to keep up on the mailing list vs. remembering to browse

Re: Create multi array

> Le 6 oct. 2017 à 12:43, Spencer Hinsdale via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > > 1) Use a Two Dimensional Array: Two dimensional array would be my choice too. Using EXECUTE FORMULA to "declare" a variable seems ugly, especially in compiled environment… > The Docs call them

Re: Create multi array

1) Use a Two Dimensional Array: http://doc.4d.com/4Dv16/4D/16.2/Two-dimensional-Arrays.300-3433911.en.html 2) Decide if your arrays are Rows or Columns. The Docs call them Rows. If you decide your arrays are Columns, then you must REMEMBER the Docs need "translation" anytime you refer to

AW: Create multi array

I would not do this unless there is no other solution for the problem I want to solve. Better solutions: - Pre-declare a number of arrays (Array text(MyArray_001 etc.) and use them by get pointer (Get pointer ("MyArray_"+string($lCounter)) - On interface level you can address most elements

Re: Create multi array

EXECUTE FORMULA should do the trick. For ($i;1;17) $s:="ARRAY REAL(aANA_"+String($i)+";0)" EXECUTE FORMULA($s) End for Jeremy Jeremy Roussak j...@mac.com > On 6 Oct 2017, at 09:57, stardata.info via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hi All, > > I need to create

How do workers die?

Does anyone know or can they find out the following? What happens when workers die? 4D has at least two different approaches to this: * HTTP processes wait before dying, but then die if there are no new requests after some time. (Or at least they used to.) Meaning, an HTTP process may or may not

Re: 4D v16.2 false record locks

> Not an anomaly. John & Neil, thanks for the reports, I find them encouraging. We're dealing with somewhat different situations. You're going through US Tech Support, which I have no contact with and you're using the TAOW, which we don't currently have access to in AU/NZ. The business case for

Create multi array

Hi All, I need to create 20 arrays that have a similar name. I can do this using the pointers? I try with this code, but in compiled mode not work. For ($I;1;17) $vPoint:=Get pointer("aAna_"+String($I)) ARRAY REAL("aAna_"+String($I);0) End for Have suggestions? Thanks Ferdinando