RE: Anyone using v16 in WAN

Hi Chuck, > OK what about when I connect from a v11 single user via sql row 64 BIT Mac > server. What network layer does it use. Your v11 SingleUser app is definitely using the legacy network, it does not know about the New Network Layer. Your 64 bit Mac Server is definitely using the new

RE: Anyone using v16 in WAN

> OK what about when I connect from a v11 single user via sql row 64 BIT Mac > server. > What network layer does it use. I have been running tests with v15 latest hot > fix. I have many disparate connection types. If I had to take a guess, you are using the new network layer (as that is all

RE: Anyone using v16 in WAN

Apparently my last post still wasn't clear so let me try again - The new network layer is *required* if you are using: * 4D Server 64 bit on Mac * 4D 64 bit on Mac * 4D 64 bit on Win ^ If you use any of these in your deployment you MUST use the new network layer because these products do not

Re: Anyone using v16 in WAN

On Tue, Apr 4, 2017 at 3:38 PM, Charles Miller wrote: > This is true, you need to use the new network layer with a 64 bit MAC >> server... legacy network doesn't exist. >> >> >> Neil >> >> > Ohm thanks to all. This was not how I understood it. OK what about when I

Re: Anyone using v16 in WAN

On Tue, Apr 4, 2017 at 3:37 PM, Dennis, Neil via 4D_Tech < 4d_tech@lists.4d.com> wrote: > > This is true, you need to use the new network layer with a 64 bit MAC > server... legacy network doesn't exist. > > > Neil > > Ohm thanks to all. This was not how I understood it. Regards Chuck --

RE: Anyone using v16 in WAN

> (Mac and Windows clients) and connect to a MAC server using 64 bit This is true, you need to use the new network layer with a 64 bit MAC server... legacy network doesn't exist. Neil -- Privacy Disclaimer: This message contains confidential information and is intended only for the

Re: Anyone using v16 in WAN

Since you're using a 64-bit Mac server you have to use the new network layer. If you had a 64-bit Windows server with 32-bit clients, you could use the legacy (i.e. reliable) network layer. > On Apr 4, 2017, at 2:13 PM, Charles Miller via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > OK I am a

RE: Anyone using v16 in WAN

> OK I am a little confused. Ifs I build clients using 32 bit volume (Mac and > Windows clients) and > connect to a MAC server using 64 bit server, the new network layer is always > used? or not? > I thought 32 bit volume desktops did > *NOT* support the new network layer That would be 4D 32

RE: Anyone using v16 in WAN

> Yes. You only need the new network layer to support 64-bit 4D on Mac. The new network layer is required (legacy network not supported) if you are using: * 4D Server 64 bit on Mac * 4D 64 bit on Mac * 4D 64 bit on Win The new network layer is not required (legacy network supported) if you are

Re: Anyone using v16 in WAN

Yes. You only need the new network layer to support 64-bit 4D on Mac. > On Apr 4, 2017, at 12:54 PM, Timothy Penner via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > Hi Tim, > >>> I think it is important to investigate whether the instability is specific >>> to application code or not. >>>

Re: Anyone using v16 in WAN

On Apr 4, 2017, at 11:02 AM, Neil Dennis wrote: > I found the new net work layer unusable as well. During heavy loads 4D will > quit responding. I use legacy network and things work great. This was all > done on a LAN not a WAN. > > I let the 4D engineers know about this at the last 4D summit.

RE: Anyone using v16 in WAN

Hi Tim, > > I think it is important to investigate whether the instability is specific > > to application code or not. > > > > for instance, it is possible to create a bare bone copy of you database > > with the export structure command. you can then open a copy of your > > production data

Re: Anyone using v16 in WAN

On Apr 4, 2017, at 11:02 AM,Keisuke Miyako wrote: > I think it is important to investigate whether the instability is specific to > application code or not. > > for instance, it is possible to create a bare bone copy of you database with > the export structure command. you can then open a copy

Re: Anyone using v16 in WAN

Are folks having trouble with the new network layer using it in 32 bit mode or 64 bit mode? Just wondering if 64 bit mode is also problematic. John DeSoi, Ph.D. > On Apr 4, 2017, at 10:56 AM, lists via 4D_Tech <4d_tech@lists.4d.com> wrote: > > Of the sites we are running at, all but the

RE: Anyone using v16 in WAN

to:4d_tech-boun...@lists.4d.com] On Behalf Of Herr Alexander Heintz via 4D_Tech Sent: April 4, 2017 7:50 AM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: Herr Alexander Heintz <listrea...@heintz.net> Subject: Re: Anyone using v16 in WAN Am 04.04.2017 um 14:54 schrieb npdennis via

RE: Anyone using v16 in WAN

to:4d_tech-boun...@lists.4d.com] On Behalf Of Herr Alexander Heintz via 4D_Tech Sent: April 4, 2017 7:50 AM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: Herr Alexander Heintz <listrea...@heintz.net> Subject: Re: Anyone using v16 in WAN Am 04.04.2017 um 14:54 schrieb npdennis via

Re: Anyone using v16 in WAN

Am 04.04.2017 um 14:54 schrieb npdennis via 4D_Tech <4d_tech@lists.4d.com>: > >> if you have no issues using the database in user mode over the same network, >> then perhaps some methods are choking the network in a way that does not >> happen over the legacy layer. > > I found the new net

Re: Anyone using v16 in WAN

> if you have no issues using the database in user mode over the same network, > then perhaps some methods are choking the network in a way that does not > happen over the legacy layer. I found the new net work layer unusable as well. During heavy loads 4D will quit responding. I use legacy

Re: Anyone using v16 in WAN

Doug, I've been running a db over WAN since v2004. I've found v15 to be more stable than any of the others but I'm also running it on the legacy setting. I've changed to the new one a couple of times and it always gets complaints from users about responsiveness or sluggishness. I don't have any

Re: Anyone using v16 in WAN

Hello, I think it is important to investigate whether the instability is specific to application code or not. for instance, it is possible to create a bare bone copy of you database with the export structure command. you can then open a copy of your production data with that structure file.