Do you need a data base or a spreadsheet?
I think you should research Database Design and Normalization, before making a decision.
Access is software, as is FileMaker Pro, and neither will do the design for you.
You need to identify requirements for input, outputs; design the appropriate tables and relationships.
Why does FileMaker Pro not work? What is the real reason you think you should move away from FileMaker Pro?
Places to start:
http://forums.aspfree.com/attachment...2&d=1201055452
http://www.rogersaccesslibrary.com/T...lationship.zip
Good luck.
From Wikipedia:
"Filemaker Pro is a Relational Database app that... integrates a database engine with a GUI-based interface, allowing users to modify the database by dragging new elements into layouts, screens, or forms..."
Since a description of MS Access is pretty much identical to this, I think Access would be the obvious choice! There's nothing that Filemaker Pro can do that Access cannot, but I'm pretty sure that the opposite is not true!
I also suspect that the number of online support groups for Access far outstrips those for Filemaker.
Linq ;0)>
The main reason we want to migrate is that our version of Filemaker Pro is quite old and no hope of getting it updated. The schools keep MS Office relatively updated; therefore, we have Access 2007 atm.
We currently run it as a database, taking information about incoming students etc. We can then search the records, sort etc.
Another reason we want to migrate is that only 2 computers at our school have Filemaker Pro while all of the others have MS Office.
I like the ability to go into design mode of Filemaker, make the form, and the use that as our template for the records.
My searches on google have not revealed what we need, none show or give directions on how to replicate what we currently use.
Basically, I have very little knowledge about Access but will learn if this program can indeed serve our needs.
Thank you so much for your responses thus far.
Matt
Buying software is a little bit like buying a very expensive engine diagnostic tool. If you have no idea how an engine works, or no experience in engine tuning or diagnostics, you'll have to learn that before the tool has real meaning to you. Similarly with Access. If you do not know how identify your requirements, or how to normalize your tables, or build your relationships, you'll have to learn that before the software is useful to you.
That's a little extreme, but hopefully you get the message that you have to tell Access what to do. It can help, but it only knows what you tell it.