These parts have to be cleaned, identified, documented, photographed, inventoried, and priced. Our business is in the used industrial manufacturing equipment space we frequently buy injection molding machinery that's for parts / not working and break it down for parts. I'm going to give it some time to see if some sort of maintenance task kicks in after a given period of inactivity. Verified that there were no other open connections.Created a Container field on the default database.fmp12 filesize reasonable, and I don't want to have to manually intervene. For reasons that are too boring to detail but that are otherwise sound, we want to keep our. What I am concerned about, however, is unchecked file growth without a good system in place to automatically prune things back from time to time. When we take this system live, records are going to be deleted one-at-a-time, not en masse, so I'm not terribly worried about things going wrong during a bulk delete. If FileMaker Server doesn't do this automatically - if I run fmserver restart, does it close the database connections gracefully? I could just run that nightly on the host machine and everything would probably be fine. Filesize did not change appreciably (still read as 40 GB). I imported about 30 GB of photos, one photo per record.I created a table in a local file with a text field for a filename, and a Container field for a photo, with the Container field set to store the photo data in the record (i.e., not as a reference).fmp12 file until I close the application - it may add some sort of soft-delete flag or something, but it doesn't actually reduce the filesize of my database until I close the application.ĭoes FileMaker Server manage this automatically? I've been doing some tests locally, and I've noticed that the FileMaker Pro Advanced application doesn't remove deleted data from the.
0 Comments
Leave a Reply. |