Many thanks Allan for your quick response! We will just keep on testing but Im suspecting the issue is unrelated to new or old network layer since we have only been running the legacy and the problem started when going from v13 to v17. As you say it might be something 4D fixed in a R release, without knowing it :-)
Best, Rikard > On 30 Jan 2020, at 21:32, Allan Udy <allansn...@gmail.com> wrote: > > Hi Rikard, >> Did you ever find a resolution for this? We started to get the exakt same >> issue you describe a couple of month ago on a customer when upgrading from >> v13 to v17.0 HF2. 4D then told us to update 17.3 HF2, still same problem. > > While we no longer have the issue, I'm afraid wecan't actually pin-point the > exact solution for you. We had a number of different problems at essentially > the same time (for months and months) and we had to try a number of different > things before the issues seemed to stop. > > The system is currently running using 4D v17R6, on a machine running Windows > Server 2012, with the majority of the clients being Windows 10. All in 64-bit > (obviously as we're running R6), and currently using the legacy network layer. > > We 'think' that the problem went away after a version update, so I'm > wondering if there was something that changed in one of the later R releases > (R4) that hasn't been rolled into the Dot releases....? > > Sorry I can't be any more help at the moment. We'll have a chat about it at > this end and if we think of anything else that might help, we'll let you know. > > Cheers > Allan > ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
