EDI(FACT) format

Hello. does anyone have any experience with this format, or even suitable 4D code? Example: UNA:+.? ' UNB+UNOC:3+:+xx4711xx:+181017:1124+8741+' UNH+1+INVOIC:D:96A:HE' PCD+12:2' BGM+380+7410268+9' DTM+137:20181016:102' RFF+VN:11775607' CUX+2:EUR' NAD+II+:91++sangro medical service

Sets and the twinned process (Execute on server)

I haven't looked at this in a long time but I'm revisiting some code that uses sets. This happens to be v15 and we are talking about client/server. The docs are pretty clear about the scope of sets with the only unusual thing being a

Re: Sets and the twinned process (Execute on server)

Thanks Arnaud, That's what I suspected. On Wed, Oct 17, 2018 at 9:21 AM Arnaud de Montard via 4D_Tech < 4d_tech@lists.4d.com> wrote: > > > Le 17 oct. 2018 à 17:58, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> > a écrit : > > > > [...] a process set created on the > > client side is available

Re: Sets and the twinned process (Execute on server)

> Le 17 oct. 2018 à 17:58, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > [...] a process set created on the > client side is available to a trigger method which runs on the server. > > I have an EOS method that does some queries and creates a set. I notice > that set is

Re: Built Server—Best Practices...

Robert, don’t know it this is relevant to your situation but many years ago, to get around the problem of losing the backup settings when installing a new built application version, I setup a system where, on quit, I stored the backups xml file in the data folder (or a record in the data - too

Help->v11 to v17 Upgrade or New?

I have an old v11 database running on Windows that’s not particularly well-designed and where there are more than a few subtables to deal with. Assuming that there is no additional budget for writing a new clean app, would you likely upgrade or re-write in v17 with the old v11 structure as

RE: Help->v11 to v17 Upgrade or New?

The main conversion of subtables took place when upgrading to v11, this was automatic. ^ This only applied to sincle-level subtables as anything beyond the first level was lost: http://kb.4d.com/assetid=49513 The rest of the conversion needs to be done by the developer and consists of

Scroll keys

Hi I have a forn, on which there are two pictures, which scroll in sync using a single horizontal scroll bar. How do I get the left/right arrow keys to operate the scroll bar. The language ref says Scroll keys are automatically available for users when a picture type object has a scroll bar. but

Re: Help->v11 to v17 Upgrade or New?

I would go and using v 11 create new tables using key from main table move data and then upgrade. I would lastly delete the old sub table and mark the link as unused Sent from my iPhone > On Oct 17, 2018, at 4:36 PM, Timothy Penner via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > The main

Re: Help->v11 to v17 Upgrade or New?

This is a very hard question to give any advice on. There are a lot of factors that could affect the decision. Things to consider: - Complexity of the structure (# of tables, forms, methods, etc) - Are there any old style 4D extensions used? - Are there any plugins that are no longer supported?

Re: EDI(FACT) format

I have experience with the EDI formats regarding medicaid submissions. This doc might help you. Seems to relate to the format of the message you have in the email. https://www.editeur.org/files/EDIfact%20eancom%20pdfs/EDIfact%20Serials/S2%20EDIFACT%20Transmission%20v1.3%20(serials).pdf Dani

Re: Help->v11 to v17 Upgrade or New?

4D automatically converts Subtables. This should not be a problem. > On Oct 17, 2018, at 12:45 PM, Robert ListMail via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > I have an old v11 database running on Windows that’s not particularly > well-designed and where there are more than a few

RE: Help->v11 to v17 Upgrade or New?

> The rest of the conversion needs to be done by the developer and consists of > replacing the subtable commands and redrawing the relationship line. This is > not automatic. See more here: http://livedoc.4d.com/4Dv17/help/Title/en/page3607.html#1693868 What we mean by “change the code

Re: Help->v11 to v17 Upgrade or New?

At some point, v18(?), 4D will completely drop support for subtables. as I understand: a simple conversion to the current version will allow all the functions of existing subtables to continue working -- without -- any change to code. As noted by Tim Penner, but typo-ed :), this applies to a

Re: Structure to TEXT files... GitHub

As I know, not yet for the moment, may be later V18 or V17R3 give us, for the moment, the capability to manage sources with a Version control system, like Hithub does. - Patrick EMANUEL Administrator

Re: Built Server—Best Practices...

I only rebuild the entire client and server if there has been a 4D version change ie moving from 16.3 to 16.4 etc. Otherwise I build the server and just copy across the new .DC file from the Server Database folder. You need to make sure compiling on same version as deploying. Never had a problem

RE: Structure to TEXT files... GitHub

> So, could this structure data not be used to create a new 4D database? Can > it be > imported back into 4D…? This question hits the nail on the head. So you can export all your code and the forms into text files and commit them into a source code revision system like git or hg. But this