Hi Allan, I've seen a similar issue when opening a 4D database which resides on a mounted disk (macOS, both structure and data on the remote). This is a confirmed bug (ACI0099881) in 4D which started from v17R4 (and R5+R6). Unfortunately this bug will not get fixed in v17. But I can confirm it is fixed in the v18 beta versions.
So, either go back to 4D v17.3 (not R-version) or v17R3 (but miss a few new features) or move forward to v18 beta. Kind regards, Koen > Op 4 jan. 2020, om 04:25 heeft Allan Udy via 4D_Tech <[email protected]> > het volgende geschreven: > > We use a couple of very small databases in-house, where the datafile is > stored on a file server (MacOS), and various people will periodically access > the system and then quit. > > Just upgraded one of these to v17R6 64-bit (from v17R4 32-bit) .... at > startup a record is written into the datafile and this action immediately > throws a -9999 error: "No more room to save the record." > > If we copy the datafile off the file server onto a local hard disk, the 4D > v17R6 64-bit version of the app opens the datafile perfectly fine, with no > error. > > It appears that this is a 64-bit problem, as the earlier v17R4 32-bit version > works fine, where-as R4 and R5 64-bit also display the same error. > > I've tried with two different client machines (both Macs), and two different > file server -- same result. > > Anyone have any suggestions as to what may be going on here? What am I > missing? -------------------- Compass bvba Koen Van Hooreweghe Kloosterstraat 65 9910 Aalter Belgium tel +32 495 511.653 ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
