M
m12345679
Hello all!
I am thinking of creating a database in Access 2003 for a restaurant.
I need it to be able to handle constant use every day and night to
record all orders and bookings (10 or so tables). There should not be
masses of data involved. Security (from unauthorised access) is not
such an issue with this data (it will be backed up every night). The
laptop it will be running on will not be connected to the internet or
used for many other purposes.
All I need is for Access to do this without crashing or slowing down
(after extensive testing of my created UI and data structure of
course). Is this considered sensible or should I look into a safer
option (mySQL, etc.)?
P.S. Will using the new Access 2003 file format give any extra
stability?
Thanks!
I am thinking of creating a database in Access 2003 for a restaurant.
I need it to be able to handle constant use every day and night to
record all orders and bookings (10 or so tables). There should not be
masses of data involved. Security (from unauthorised access) is not
such an issue with this data (it will be backed up every night). The
laptop it will be running on will not be connected to the internet or
used for many other purposes.
All I need is for Access to do this without crashing or slowing down
(after extensive testing of my created UI and data structure of
course). Is this considered sensible or should I look into a safer
option (mySQL, etc.)?
P.S. Will using the new Access 2003 file format give any extra
stability?
Thanks!