Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / General 2 / June 2007

Tip: Looking for answers? Try searching our database.

Creating a good database in Access 2003 for a business...

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
m12345679@googlemail.com - 26 Jun 2007 20:54 GMT
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!
SteveM - 26 Jun 2007 21:20 GMT
Access will be ideal for the scenario you describe.

The Access 2003 file format is documented to have:
'Provision for unknown properties and objects that might exist in future
versions of Access' and an 'Improved storage format'.

People that have been developing with Access for many years will probably
tell you that Access 97 was the most stable...but I have been using 2003 for
a few years now without problems.

Steve

> Hello all!
>
[quoted text clipped - 15 lines]
>
> Thanks!
aaron.kempf@gmail.com - 27 Jun 2007 07:02 GMT
SQL Server will be ideal for the scenario you describe.

SQL Server 2000 aka MSDE SP4-- these are great database engines.

just don't try to run them on vista

and use Access Data Projects-- these are-- long term-- worth an extra
hour or two in research and development
I mean-- do you want a reliable database; or something that acts up
once a week?

> Access will be ideal for the scenario you describe.
>
[quoted text clipped - 30 lines]
>
> - Show quoted text -
m - 27 Jun 2007 15:49 GMT
On 27 Jun, 07:02, "aaron.ke...@gmail.com" <aaron.ke...@gmail.com>
wrote:
> SQL Server will be ideal for the scenario you describe.
>
[quoted text clipped - 43 lines]
>
> - Show quoted text -

Thanks for your replies. I will probably use Access 2003 for now and
see how it goes in Beta testing. I would like to have other options
but I still have not learnt enough of them yet.

btw I think usenet is brill!!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.