Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

Error opening .fp5 file windows -> mac


This topic is 8054 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I am using Filemaker Pro Developer 6.0. When I create a database file

on Windows 2000, I cannot open in on a Mac - error message (This file

could not be translated using the selected file type.) However, when

I create a database file on the Mac, I have no problems opening it on

the Windows machine. I have tried recovering the file - still does

not open on the Mac -

Any ideas how to resolve this? John

Posted

Windows OS uses the extension of the filename to identify the file type, while MacOS uses the Creator Type, which is an attribute of the file itself. Windows OS does not set this attribute.

Just open the Filemaker application, then open your files, the MacOS will then set the Creator Type.

Posted

I've tried that - starting Filemaker on the Mac, then attempting to open the file, but I get the same message.

I am able to use the Developer tool on the *.fp5 files and they seem to be read correctly. It is only when attempting to open them with Filemaker Pro - before using the Developer Tool - that I get the error message. This is not an isolated instance, either. It happens to all (about 20 now so far) files that I try.

John

Posted

Then something is wrong with either your installation of Filemaker or your method of transferring the files.

Reinstall Filemaker on BOTH systems.

How are you moving the files from one system to another?

Posted

OK, I'll try re-installing filemaker developer. I use a zip disk to transfer the files back and forth between machines. I haven't had problems with any other types of files using this method.

John

Posted

You may have to configure the File exchange control panel to recognize PC files with the .fp5 extension as Filemaker files. Otherwise the creator type won't be set properly.

Posted

Installation of Filemaker should do this, also opening the app first, then opening the files should also so this.

Try compressing the files into an .ZIP or .SIT archive first, this will often get around what ever is causing the problem.

This topic is 8054 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.