Re: CALL WORKER questions

there is a "poor man's interprocess messaging" technique, that works without workers or preemptive processes. on your form, you have objects. the data source can be form local (a.k.a.) variables. you get pointers to the objects (OBJECT Get pointer). you pass those objects to New process. the

CALL WORKER questions

I am looking into using CALL WORKER / CALL FORM for an interface where certain actions will query a service, which could take up to a few seconds. Using CALL WORKER and CALL FORM would allow me to split the long-running part to the worker without having to roll my own IP messaging and the On

Roy (Suzi) McGregor Paterson R.I.P

Hi, This was submitted to 4D Today (which I rarely update anymore) a few days ago. I've decided to post it here. As far as I can tell Roy/Suzi last posted in 2007 to the iNUG. Sad news to report from the UK Roy McGregor Paterson Roy (a.k.a. Suzi) who worked with 4D from the early days

RE: How to tie 4D to barcode readers?

Kirk & Tony, We do lots of bar coding systems every year using wedge-readers (keyboard input), RS-232 wireless, and IP-based wireless. Going forward we are no longer doing RS-232 scanners as it is simply too much work for both us and our clients. If a wedge-reader is the right tool, we use

Re: Team Developer - Do all developers need to be on same minor version?

that is one of the beauties of components; they can have object notation activated independent of the host's status. same for unicode mode. as for the version being different, and not requiring recompilation, see documentation:

Re: How to tie 4D to barcode readers?

Tony, How are you handling programming the barcode reader to include information about what the barcode belongs to? Or are you using it as an extended keyboard input? On Tue, Aug 28, 2018 at 4:19 PM Tony Pollard via 4D_Tech < 4d_tech@lists.4d.com> wrote: > If you want the bar code scanning to be

Re: How to tie 4D to barcode readers?

If you want the bar code scanning to be independent of where the user is on the UI, then there is usually a serial port emulation available on USB. GET SERIAL PORT MAPPING is useful for this on Mac. You can then run serial comms in a separate process, which is handy if (for instance) the bar

Re: Team Developer - Do all developers need to be on same minor version?

Jeffrey Kain jeffrey.k...@gmail.com writes: >Nope... >If 4D makes a major change to the protocol they'll block it. For deployment >we try to have matching versions always. > >> On Aug 28, 2018, at 2:24 PM, Dave Nasralla via 4D_Tech >> <4d_tech@lists.4d.com>

Re: Team Developer - Do all developers need to be on same minor version?

Thanks, Tim. We use the "Current version:" setting to for all the clients to update to the same version as the server. What do you do about components? 4D POP is a good example. Those are not distributed as source code, but rather compiled .4DC files. As far as I can tell there are no v17

Re: Team Developer - Do all developers need to be on same minor version?

Hardly ever. Only if we make changes to it. > On Aug 28, 2018, at 3:01 PM, Dave Nasralla via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Do you recompile each component with each > deploy for minors? > I've noticed 4D often does not complain if the component is even from > a different major

RE: Team Developer - Do all developers need to be on same minor version?

Keep in mind that 4D QA does not test mixing and matching different versions of client and server - there are way too many permutations... QA only tests the same build of the client with the same build of the server. It is typically the expectation that the version of 4D Client will match 4D

Re: Team Developer - Do all developers need to be on same minor version?

Thanks Jeff. For the Deployment, we use the server machine, so the clients will always have matching versions (Windows and Mac). What about the components? Do you recompile each component with each deploy for minors? I've noticed 4D often does not complain if the component is even from a different

Re: Team Developer - Do all developers need to be on same minor version?

Nope... If 4D makes a major change to the protocol they'll block it. For deployment we try to have matching versions always. > On Aug 28, 2018, at 2:24 PM, Dave Nasralla via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > One of our systems is developed with 4D Server (Team Developer) with >

Team Developer - Do all developers need to be on same minor version?

Hi all, One of our systems is developed with 4D Server (Team Developer) with several coders connecting to make changes. If I move the Server from, say v17.0 to v17.0 HF1 or a nightly build, do all the other developers need to update their versions? 4D does not complain when you connect, as long

Re: New record numbering system and CALL WORKER

I use longings as relational keys because it is easier to track down when the user(s) come to me as ask why some related(?) data is not where it should be. [table]ID = 1234 is a lot easier to work with then [table]ID = B83F47092A384821A9FABA5379C3CCC0 when try to track data. I don't use

Re: New record numbering system and CALL WORKER

Kirk Brooks: > scanning back over it a key point is that all of these > contortions and workarounds to preserve a number sequence are based on the > single design decision to use an invoice (in this case) number as a key > field. Nope, the invoice number has never been a key field over here.

Re: New record numbering system and CALL WORKER

Kirk Brooks writes: >I am surprised this thread has drawn so much discussion. It's good >discussion but scanning back over it a key point is that all of these >contortions and workarounds to preserve a number sequence are based on the >single design decision to use an invoice (in this case)

Re: New record numbering system and CALL WORKER

I am surprised this thread has drawn so much discussion. It's good discussion but scanning back over it a key point is that all of these contortions and workarounds to preserve a number sequence are based on the single design decision to use an invoice (in this case) number as a key field. I'm not

Re: New record numbering system and CALL WORKER

It allows you to work with related records as if they were subrecords. For example, you open an Invoice and start a transaction so that changes to line items can be rolled back if the Invoice is cancelled (something that automatically happened with subrecords). But then you want to drill down

Re: New record numbering system and CALL WORKER

Dave, That's fine as long as the id number isn't being used for something else ... in our case, the id numbers are used as the key field for relating data from other tables, so this needs to be assigned when the record is created ): Pat On Tue, 28 Aug 2018 at 15:32, Dave Nasralla via 4D_Tech <

Re: New record numbering system and CALL WORKER

Hi Bernd, I ran into a similar situation with Proposal and Project numbers. My decision was to not give the number out until they saved the record. This prevented people from using the number elsewhere (say for purchasing, etc) without a saved record in the system. dave On Tue, Aug 28, 2018 at

Re: New record numbering system and CALL WORKER

Thanks. As I said I was not sure. Regards Chuck Chuck Miller Voice: (617) 739-0306 Informed Solutions, Inc. Fax: (617) 232-1064 mailto:cjmillerinformed-solutions.com Brookline, MA 02446

Re: New record numbering system and CALL WORKER

Good point, Bernd. I will implement that also. Pat On Tue, 28 Aug 2018 at 07:46, Bernd Fröhlich via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Pat Bensky: > > > The important thing is that all record cancellations go through a > > *CancelRecord* method. > > I created a [SpareRecordNumbers] table

Re: New record numbering system and CALL WORKER

Pat Bensky: > The important thing is that all record cancellations go through a > *CancelRecord* method. > I created a [SpareRecordNumbers] table which contains 3 fields: unique id, > table number, and spare record number > As I said, it hasn't been thoroughly tested yet. So please feel free to