FileMaker is an Apple susidiary, yet OS X 10.1 breaks several features in this great program. I am no talking about the absence of the toolbars (a yippee yippee Windows sop I can do without), but something much more essential to developing FileMaker solutions.

I am a FileMaker developer and after updating to OS X 10.1 I can no longer copy and paste when in calculation dialog boxes. FileMaker tech support tells me that the bug is in OS X, not FileMaker. What a pain this is when editing a number of calculations or script steps containing calculations that are similar enough to copy, paste and change the variable necessary. So I am now launching the Classic version to do serious scripting and calc editing. What a pain.

No copy and paste? In FileMaker? Geez, Apple (and FileMaker), I hope you get this fixed ASAP. FileMaker is not OS X ready when essential features break in the OS.

By the way, I have not found this anywhere in either the OS X documents, the Knowledge Base or in FileMaker's support files and KB.

Any help, Apple?

Unbelievable - but true !

How FMI can say it's a fault in OSX is beyond me - Copy/Paste works OK with othe apps, so it looks like this one's down to FMI.

Come on boys - how about a fix, this is embarrassing.

A workaround - use CUT and PASTE.

Mark, thanks for the tip. I don't like to use Cut when I need to copy but use it if necessary. Currently I am using the OS 9 version in Classic when I am doing the calc field copy drill. I posted this problem on the Apple OS X discussion board and got a reply back from a guy who was using 5.5 and OS X 10.1.4, as I am with no ill effects. I should have mentioned before that I am using FM Develolper 5.5. I removed the user version of FileMaker 5.5 when I installed Developer. I am about to reinstall it and try it out, too in 10.1.4. Will post the results.

Anybody else have this problem, or even better, a solution?

Has anybody seen this problem identified in either the Apple or FileMaker knowldedge base? I have hunted all over for it and can find no mention of it, but the FileMaker tech support rep immediately told me about the conflict, so I infer that it is common knowledge at FileMaker, Inc.

Well, so much for accuracy of reporting. The bug I describe appears in my FM DEVELOPER 5.5v1 and in FM 5.5v1, but not in FM 5.5v2. My bitching is misdirected, and I am sorry for my confusion being displayed all over the forum. This thread probably more accurately belongs in the FileMaker Developer forum. However, it still begs the question of why FileMaker, Inc. doesn't disclose this and/or publish a fix.