Existing users, 
 FileMaker Pro - 10.0v3Database software to manage people, projects, assets and more. |
|
||||||||||||||||
|
|||||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
Amazing evolution this version 
- Version: 10.0.1, 3/14/2009 11:34AM PST
(1 of 2 users found this comment useful)
umg
the newly added script triggers of this version 10 are a new dimension to FileMaker - this update is a major step towards the right direction. You can program in all kind of programming styles - event based - procedural - functional - almost object oriented. in the right hands it is an amazing development environment and i love to run it on the mac - where i can have more then one client running accessing the same served database. not to mention it is an amazing calculator as well -
it got it almost all - it calculates better then Excel or Numbers - the speed got improved - about 40 % faster then in FMP 9. It scales up pretty nicely - still things left for improvement though: custom functions recursion limit should be adapted - we got faster hardware now to cope with and more integration of all formating parameters in custom functions - as well as status feedback of script triggers evoking scripts - for better abstraction. it is fun to rethink old filemaker habits and a lot of
clumsy or even elegant workarounds are not necessary anymore ..
again - it is only as good as its programmers - so if you find a solution with some frustration it might
not be filemaker to be blamed for. the filemaker certification program provides some measures ..
it got it almost all - it calculates better then Excel or Numbers - the speed got improved - about 40 % faster then in FMP 9. It scales up pretty nicely - still things left for improvement though: custom functions recursion limit should be adapted - we got faster hardware now to cope with and more integration of all formating parameters in custom functions - as well as status feedback of script triggers evoking scripts - for better abstraction. it is fun to rethink old filemaker habits and a lot of
clumsy or even elegant workarounds are not necessary anymore ..
again - it is only as good as its programmers - so if you find a solution with some frustration it might
not be filemaker to be blamed for. the filemaker certification program provides some measures ..
The mySQL fallacy 
- Version: 10.0.1, 3/4/2009 10:22AM PST
(3 of 4 users found this comment useful)
lveillette
In the documentation, it says that FM now opens mySQL and other external sources databases as if they were FileMaker database.
Don't be misled. You still can't just go in the open menu and select a mySQL database.
You'd think that after 10 versions, Filemaker would figure that people love mySQL and need to integrate with their FM solutions... Not so.
To be sure the solution involves dealing with OSX abysmal and unstable ODBC manager, or buying a third party solution from Actual technologies...
I can't wait to see that...
But all I know is that all this braging about mySQL compatibilty in Filemaker ads is just chit-chat, like that of a politician or such... It translates in "you and me speak" to "someday, maybe... if... then... else..."
Don't be misled. You still can't just go in the open menu and select a mySQL database.
You'd think that after 10 versions, Filemaker would figure that people love mySQL and need to integrate with their FM solutions... Not so.
To be sure the solution involves dealing with OSX abysmal and unstable ODBC manager, or buying a third party solution from Actual technologies...
I can't wait to see that...
But all I know is that all this braging about mySQL compatibilty in Filemaker ads is just chit-chat, like that of a politician or such... It translates in "you and me speak" to "someday, maybe... if... then... else..."
And it would be wonderful if the Export Records option would export field names. The Import option logically offers it, but if I want to manually attempt to move my data to the iPhone through a third party iPhone app, or Excel, I have to manually recreate all the field names as records when I export my databases.