Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help me choose between Filemaker and Access

Status
Not open for further replies.

Vandelay

Programmer
Jun 22, 2003
95
US
Hi,

I currently administer a MS Access database and there are a lot of things I don't like about it. From the website info, Filemaker Pro seems more friendly to the integration of video / audio files, etc. Plus... I would like to run the same database on both a Windows / MacIntosh simultaneously if possible. I downloaded the trial version of FMP 7.0. I can see it'll take some time getting use to it.

Can anyone tell me if I should make the move or should I stay with access.

My database runs at 2 different work sites (currently the db is completely independent... two separate db's). It is mostly information logging for a daily activity log.. but I want to add video clips, etc. I work for a surveillance type company.

PLEASE HELP... and advice is greatly appreciated.

Vandy
 
but I want to add video clips, etc"
this can be done with access as well....depends on your personal preference and current Access skils.
If u consider yourself a beginer then I say switch for the ease of use. FM's GUI is more "user friendly" so it will be easier to "design" the DB. You loose on SQL part that is also user over many SQL-based DBs.....If you are looking to vernture into DB design in general than Access is closer to most "SQL based DBs".....while programming language used in FM is geared towards Mac users and AppleSript in general.
HTH
All the best!

> need more info?
:: don't click HERE ::
 
If you require any kind of object interface with Office documents (Word, Excel), stick with Access. If your application requires any sort of object-based interaction with other applications, stick with Access. If you require any kind of cross-database connectivity, stick with Access. If you need a low-end file-based datasource for a web site, stick with Access.

If you're mesmerized by all the nifty-looking screens you can create with FM, and don't need any of the above, by all means use FM.

Phil Hegedusich
Senior Web Developer
IIMAK
-----------
Boy howdy, my Liberal Studies degree really prepared me for this....
-----------
A skeleton walks into a bar, and says "I'll have a beer and a mop.
 
All this:
"If you require any kind of cross-database connectivity, stick with Access. If you need a low-end file-based datasource for a web site, stick with Access."

is also true for FileMaker.....and the new v 7 is out that brings whole another world to it.....but above I see no reason to WHY u want to change is u are already familiar with Access.... FM is also cross platform unlike Access that can be a pain for mac users.
If ur into Design and Video/Audio production then most likely ur using Macs and for the "ease of use" I would say go with FM. Access is the choice if ur in mostlty MS environtment and need connection to other SQL based DBs...
But we are all giving you "what we like about A or B"...what you need to do is write down what is the final goal of this information storage?
Web use?
workgroups?
remote access?
how many concurrent users?
PDAs?
how soon you need it done....etc

that will probably lead to better choice than just that fact that
"more friendly to the integration of video / audio files"

u can stikc anthing into any DB....anyhow
write some more about the "ultimate goal" of your project!
Take care!

> need more info?
:: don't click HERE ::
 
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.
FM 7 has this technique now...

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
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top