Well-designed, well-implemented multiuser Access databases are no more
subject to "crashing on a regular basis" than any other "file-server" type
of database. If the POS system you are considering _does_, then the problem
is in the design or implementation of that application software, or in the
network or system hardware environment of the users who are having the
problem.
You will definitely NOT, in my not-so-humble opinion, be better off to have
a POS system done in FileMaker. I've seen only a few professional FileMaker
developers, but a great many highly professional Access developers. If you
create your database in Access and security, corruption and/or backup,
logging, and recovery turn out to be real issues, then you can use Access to
create a client application to a server database (MS SQL Server, or any
other ODBC-compliant DB, or any DB with an ADO DataProvider)... and it isn't
nearly as much time and effort to make the conversion as you might think.
But, before you leap into the effort, be sure you've had a knowledgeable
Access developer analyze the situation and problems.
Obviously, if it is a "canned application" that you've licensed, and you
don't get the source, then you won't be able to change the application
itself, nor convert it to client-server! Some Access applications, however,
are available with source (for an additional cost) so you _can_ customize or
enhance them.
Larry Linson
Microsoft Access MVP