Filemaker Pro versus........ 6

[martinbaldock]

I'm in the process of choosing a database application, and I'm probably asking the "already converted", but will Filemaker Pro be easy to use compared to Access?

I want to set up a Competitor Intelligence database with a data entry form on our intranet, and a search capability. I find Access very clunky and unfriendly from both my point of view, and for users.

Your views would be most appreciated, thanks Martin

 

[rspringf]

My opinion is that it's the best:
Filemaker is easy to learn for development.
Does not require additional scripting languages.
Crosses platforms well.
Is limited by the number of simultaneous files that a client can have open at one time. I'd like to see the other small DB come close.
Takes great performance benefit from 100baseT network with switches on one side of the router.
Is in constant evolutionary adjustment toward the positive by the makers.
Has a rabid worldwide bunch of users,developers,educators, and wingnuts allowing for growth and a future.
Is not made by the largest software supplier in the world.
Good Choice!

RSpringf

 

[JeanW]

Easy to use.
I use Access (have to) and Filemaker.
When I make a DB in Access I always convert it to FM.
Use FM to try things out, even if I need it in Access.

For me it's FM first, Access if I need to.

If you want/need flexibility, just go for FM and forget all the rest.

HTH

JW

 

[Kjonnnn]

My companys has been using Filemaker. But I am now trying to convert the so called Databases to Access. The general consensus around here from execs and users is that Filemaker is not good.

Access is a MUCH BETTER program if you're look for a true database. The learning curve maybe steeper, but the benefits of Access are much greater.

The forms are easier to make in Filemaker.

I'd advise you to think of your needs for NOW as well as IN THE FUTURE.

 

[mdwbeex]

I have dealt with both Access and Filemaker. Hands down Filemaker is by far the best choice for both the developer and the user. Access is in a word: painful. Filemaker has an extensive base of plugins and ready made templates as well, alot for free, that make it as versatile a tool as you'll ever need for data management.


Whatever you do though, don't even consider Act! - now that's a nightmare waiting to happen...

 

[murraym49]

I work for a large organisation and have developed databases in both Filemaker and Access. I am a great supporter of Filemaker but, having developed some reasonably complex systems, am aware of its limitations. Which one you use really depends on your needs. We have used both with great success.

If you intend to build a reasonably simple app with low maintenance, relatively small amount of data and relatively small number of users, I would probably prefer Filemaker. Development is easy, maintenance can often be done by the end user and, most importantly, users can easily build their own reports. The ease with which a non-technical user can query the database and build reports is one of Filemaker's best features. It's also really quick and easy to develop a "pretty" frontend. We have populated the database with data from one of our large corporate apps and we use it for stuff the big app doesn't do. We do regular imports to keep the data current and in synch with the big app.

However, one of the drawbacks of Filemaker is that it becomes quite complex to do lots of tricky stuff like checking and comparing data, or lots of calculations. This is because you have a limited number of script steps to use and calculations and summaries require their own fields, so it's a bit tedious. VBA offers more variety and more control. Generally it is possible to do the same things in both apps but the tricky stuff can be done much more easily in Access using VBA. The big drawback with Access is that any modification to the app usually has to be done by a techo. This usually includes things like writing new reports and forms which can be done really easily by the enduser in Filemaker.

 

[JeanW]

FM versus Access,



Access and Filemaker are different enough that you do have to change some of your thinking, and use different techniques.

Platforms
=========
Of course Access is not available for the Macintosh except through Windows emulation software.So for cross-platform development I would recommend a product like Filemaker, which operates just as well on Windows-based platforms as on the Mac.

Web-database development
======================
Filemaker is definitely easier to get a basic web database set-up. However, Access uses some other technologies such as ASP to a greater extent. By the time you start making complex web databases where Access becomes a better choice than Filemaker, Access itself is outclassed by SQL
Server and other industrial-strength databases.
This may change with the better Data Access Pages in Access 2002, but I doubt it.

In terms of bandwidth usage over a network, Filemaker is nice and lean, whereas Access is not ... (other Access developers know what I am talking about)

Relational design, ODBC and SQL
===========================
From a very early stage Access incorporated Relational design, two-way ODBC
connectivity and Structured Query Language statements in Queries. Access makes a great front-end client to other databases such as SQL Server.
On the other hand, Filemaker has added these features in the last few years.
In these areas Filemaker may never catch-up

Table/Form/Report/Layout design
==========================
The two products have different strengths and weaknesses. However, my impression is that Filemaker is a much more elegant database product, with a lot of sensible features. Microsoft could learn a lot from Filemaker.

The only areas in which Access seems to have a better design is with table linking and developing relationships. Filemaker would probably be quicker to develop an application that had only a couple of main tables.

Macros/Scripting/Visual Basic
==========================
Filemaker scripts seem to fall between Access Macros and VBA (Visual Basic
for Applications) in terms of power.

The Filemaker scripts are really easy to set-up - easier than Access macros.
However, they still fall short of a full programming language such as VBA.

Ease for novice
============
Databases always require a higher learning curve than word processors or
spreadsheets.
In terms of ease of use, in my mind I would use the following order:

- Filemaker
- Access
- FoxPro, Paradox
- SQL Server
- Oracle

At the top of this list the databases are easy to use. At the bottom the databases are powerful.

Developer
========
Here I believe Access has a slight edge for an Access expert. There is a developer edition of Office that features integration via programming, OLE,ADO and ODBC and other technologies with other Office products - Word,Excel, Outlook, FrontPage. If you do not already have Access installed (preferably the same version as you have) you can distribute run-time versions of Access. But the new version of FM Developer is really fantastic and easy in use.

Why Access ?
===========

Access is ubiquitous (what a word !!) as it is sold by Microsoft in the Professional version of their Office suite. I can buy Access at just about
any computer shop.

One thing to bear in mind:
It has taken you years to get to your level of expertise with FMP and it would take you just as long (if not longer) to attain a similar level of expertise in Access or visa versa. Your will be making the most use of your talents and skills if you developed the database in Filemaker (unless it uses ODBC).

This is a opinion that I deal with Gregory Scott.

Hope this helps. Feel free to ask if you have more questions.

John

 

[murraym49]

For a really detailed analysis check out the white paper on the Filemaker Pro web site

http://www.filemaker.com/downloads/index.html#whitepapers

titled Filemaker vs Access

An excellent document

 

[karelvanek]

I know, it is difficult to compare FMPro and Access (experienced with both). But is there anybody who could mention the main benefits when converting from FMPro to Lotus Notes?

I mean somebody who is experienced with both this db systems and therefore is able to summarize.

Thanks,

Karel

 

[jimoo]

Have you considered Visual Foxpro? Foxpro free tables are Microsofts fastest data access. Stores unlimited number of records. Completely object-oriented, Intell-a-sense, etc.



Jim Osieczonek
Delta Business Group, LLC

http://www.deltabg.com