What FM can't do ?

[Ugo DI LUCA]

Browsing other Forums, I just ran accross a post that leaded to 51 answers about FM in ArsTecnica.

It seems though that not many FM developpers are frequenting this Forum.

Struggling discussion about an article, leading to some debate about FileMaker vs Access....

link to the post

It seems that the topic, opened in March and which last post was in May, could be reopened by some of you guys.

There is also an active topic about FM and MySQL on this board...

P.S.: I'm not a member of this list, and surely won't be as I see the unfriendly way they chat there. I just found it interresting the way they are arguing and "wrestling" about a simple "article" statuing FM could do things other db couldn't....

Still there are ways to behave on some list I don't catch...Hope this never happens here.

[Anatoli]

RE: FM and MySQL...

I am just involved at BlueWorld Lasso thread about that.

It is very long discussions.

I've found, that:

On PC

Simple flat database with 200k+ records

In simple search FM is 10-40 times faster, than MySQL.

Blasphemy?

Not really. On Mac X MySQL is faster, than on PC.

On PC FM is usually 10 times faster, than on Macs.

On Linux FM server looks like the fastest FM server.

[Guest]

Both FM and Access/Jet are aimed at the same audience and both have supporters who use these tools in multi-user scenarios. I have used both and I prefer FMP as I find it easier to use. The problem with Access that it requires a very stable network environment and does not tolerate a lost connection well, corrupting the database. Most large Access sites compact and repair nightly. The other problem with Access that I have seen posted is a primary key "IDENTITY" bug that sometimes just fails and you are up the creek. That said, Jet is a true relational database as I see it ( a database composed of mathematical sets manipulated with relational algebra). This does not stop me from using parent child relationships in FMP. MySQL, on the other hand, now supports transactions.