Re: New record numbering system and CALL WORKER

2018-08-26 Thread Chuck Miller via 4D_Tech
OK i have done this many times with a table. You have multiple records in the table, one for each id you need. I usually make that records key name ([table]field). If you have to keep track of released numbers, you can add a blob field. I would not be adding object fields as you can not access

Re: New record numbering system and CALL WORKER

2018-08-26 Thread Tim Nevels via 4D_Tech
On Aug 26, 2018, at 2:00 PM, Keisuke Miyako wrote: > I totally agree with Christian, in fact, > the point (slow, should be avoided if possible) was right there in the Summit > keynote. > > on the point of "slow" > of course it is a relative thing and perhaps not a big deal depending on the >

OPs - my bad

2018-08-26 Thread Jody Bevan via 4D_Tech
I made a comment that has not shown up on the nug yet that the component documentation didn’t explain what the ‘Matrix’ was before using it. After 10 more minutes of frustration I discovered it was located in the Component Overview section - which I missed when I thought I was starting from the

Writing Components

2018-08-26 Thread Jody Bevan via 4D_Tech
I really want to place a bunch of our code / forms into a component. It will make it much easier to install into other systems, and to update that code / forms as into older designed system that use an older version of the component. Of course it also protects what could otherwise be

Re: New record numbering system and CALL WORKER

2018-08-26 Thread John DeSoi via 4D_Tech
Storage is the best option for interprocess communications if you want to use preemptive processes. I have not done any real benchmarking but I have not noticed that anything seems slow. By setting up return values on a per-process basis you can avoid locking contention on storage. For

Re: New record numbering system and CALL WORKER

2018-08-26 Thread Keisuke Miyako via 4D_Tech
I totally agree with Christian, in fact, the point (slow, should be avoided if possible) was right there in the Summit keynote. on the point of "slow" of course it is a relative thing and perhaps not a big deal depending on the context, but you only have to run code with Storage and the speed

Re: New record numbering system and CALL WORKER

2018-08-26 Thread Tim Nevels via 4D_Tech
Humm... interesting comment. Why do you say Storage is slower and can produce deadlocks? Tell us why you believe this. Was my example an example of “not well programmed”? Be honest. Give me real, solid, constructive criticism. This is a forum for exchanging ideas and learning. I’ve been

Re: New record numbering system and CALL WORKER

2018-08-26 Thread Christian Sakowski via 4D_Tech
> But lets explore other possibilities. Hopefully not. You should avoid Storage where you can. They are slower and can produce (if not well programmed) dead locks. -- Grüße/Regards, [heubach-media] | Christian Sakowski christian.sakow...@heubach-media.de iChat/AIM: SakowskiF Tel: +49/(0)40/52