I've just bought a new MacBook and am using it as an excuse to force me to organise my HD!
In Mac OS Sierra, documents and desktop are synced (optionally) with iCloud. This feature is obviously handy as it provides an easy way to access files without carrying memory sticks etc around.
My questions are:
1. Is there a danger of a FM file being corrupted if it is on a disk that is being synced with iCloud? (I believe that this is the case with DropBox etc?)
2. Is that danger only present when the file is actually open in FM, or does it apply to backup files / files that aren't open too?
One of the database was corrupted. So we have created clone of that database and performed recovery. We have imported records from this recovered file into new clone file.
This database is connected(relationship) to other database.e.g there are two database Department & employee database.These two table are created via DEPT_ID.I performed recovery on employee database.
Department Employee DEPT_ID EMP_ID DEPT_NAME DEPT_ID EMP_NAME Now When I create new employee for XYZ department.It is assigned to the another department.
How to solve this ?
I checked the recovery logs and did not find any errors but found this line
I'm seeing some very strange behavior with FileMaker 14. I'm using `LayoutObjectNames` for some required functionality. On the development system it's working fine. It returns the list of named objects on the layout.
I close the file, zip it up and send it to the client, and that required functionality isn't working. He sends the file back and I open it and get a data viewer up. The function returns nothing. I go into layout mode and confirm that there are named objects on the layout.
The first time this happened and I tried recovering the file. In the recovered file it worked, so I assumed some corruption had happened on his end. I told him to trash the file I had given him and work with a new version I supplied. The problem came up again.
This morning he sent me the oldest version that the problem manifested in. I confirmed the problem, tried recovering it again, but this time it didn't fix the problem.
I'm at a loss. It works in the version I send him, doesn't on his system. We're both using FileMaker 14, although I'm using Advanced. My next step will be to work from a served file instead of a local one, but I have never seen this type of behavior in FileMaker. Has anyone seen anything similar? Any ideas on a fix? I'm almost ready to just scrap the file and build it again from scratch since we're not too far into the project.
I have taken on a database developed in Filemaker 7 and it is currently running in Filemaker Server 11.
I need to setup a development environment so that I am not working on the live system for obvious reasons. I read an article on the Filemaker website on the ways to do this. I chose the option to copy the files from a backup to a local machine to work on. I copied all of the database files from the backup on the server to my local development machine.
The database does work in a way but most of the files I try to open it tells me "This file was not closed correctly - performing consistency check". I have tried running the "recovery" option on some of the files but even the recovered version of the files still come up with this error, so every time I try to open them it has to perform this consistency check. This isn't ideal as it is slowing the development down a lot due to having to perform the check every time I want to test a change I made.
I saw an article claiming it is possible to disable the consistency check as a last resort but cannot find that option anywhere. Ideally I would like to still use the consistency check if there is a way for me to solve this problem.
What would be my best option to solve these issues?
Thanks for any help you can provide.
By the Otter
We have a script that downloads PDFs from our corporate web site and saves them to our internal server. (Long story; suffice to say it’s a good thing.) We use ScriptMaster’s GetURLasContainer to copy the PDF to a container field, then use FileMaker 11’s own Export Field Contents to save the file to an appropriate path. Unfortunately, we’re having an issue where the PDFs being downloaded to the container are corrupt. When we try to open them, we get the following error message:
The file [insert file name] could not be opened.
It may be damaged or use a file format that Preview doesn’t recognize.
Acrobat could not open [insert file name] because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn’t correctly decoded).
To create an Adobe PDF document, go to the source application. Then print the document to Adobe PDF.
I suspect the error is somehow related to our recent upgrade from ScriptMaster 3.34 to 4.206, but we’d really hate to go back due to a plugin conflict we’re no longer having. Does anyone have any suggestions?