This morning I opened my macBook pro and found that all - literally all - of my .fp7 files have become FileMaker Runtime Documents and all launch the same, old, runtime solution elsewhere on my drive.
The problem has effected fp7 files, fmp12 files seem to be OK and open correctly. FMp5 files on the other hand simply report that there is no application to open them.
I have the various FileMaker applications on the drive and copies of most also on Parallels on the same internal drive. We have done this over the years and it is only this morning that the problem seems to have occured.
History...for what it's worth...
I have a macBook pro with 4gb RAM running macOS 10.8.2 and all recent solutions are produced in FMp12.0v2 advanced.
Last week my hard disk died and was replaced at an Apple Service Centre. I have spent the time since then carefully moving files from my backup[s] to the new drive. With few exceptions the process has gone well. Last night I restarted TimeMachine and did the first backup of the new drive to a new external drive at 11:02pm last night. That backup shows the same problem. This has been the only major change in the last 24 hours.
Is any of this revelant...I've no idea...but I've never, in 20 years of FileMaker programming an macOS since 1984, seen anything like this.
The 'files' all seem to have the 'correct' sizes,and, if I convert them to FMp12 the problem seems to be 'fixed'. However, after 20 years I have some 10,000 fp7 files...and I would not look forward to converting each one of them to fmp12 even if it was feasible. Like other developers we have files for some clients who have never upgraded to FMp12 and these need to be kept in fp7, or even way earlier, format. The problem seems more like the 'association link' being corrupted rather than the file data itself.
FMp7 files on a USB stick - which has not been connected for a few days all now exhibit the same problem. Does this indicate that the problem is in the Operating System somewhere and, if so, why are files for other programs not affected in some way?.
As a number of these files are client's work in progress the situation is catastrophic! While I can recover the files by converting to FMp12 not all of our clients want, need or will, upgrade to FMp12.
Has anyone seen anything like this before! Is there any 'cure'....can anyone help?
pntech, brisbane australia