RE: Access limitations/suitablity

Klatuu,

Thanks for your reply. The other hard limit I'm aware of is 255 (or 256)
simultaneous users.

Your advice applies for existing applications. But what about a new
application where you "think" it "might" work in Access, and you expect it to
be well short of 2 GB and 255 users? Anyone have experience where due to
performance they had to convert to something like SQL Server? If so, what
were the issues? Size? Users?

Regards,
Leif

"Klatuu" wrote:

If your application is running smoothly and user response time is acceptable,
the only walls would be if your back end databaes starts to get to the 2Gb
maximum size or if you add additional users and response begins to suffer.

Converting the SQL is not too hard, but not a breeze, either. The upsizing
wizard give you a start, but I have found you have to do some clean up work
afterwards.
--
Dave Hargis, Microsoft Access MVP


"Leif" wrote:

I know this is a difficult question to answer, since there are many factors
that come into play. Things such as amount of data, speed of
server/network/user systems, how well designed, complexity of application,
etc. come into play. However, as a rule of thumb, how do you determine if an
application is suitable to Access?

I've seen that MS recommends at maximum of about 5 users at once for Access.
I think this is well below a reasonable capability. I'm running a
department database that is about 60 MB with about 20 users at one time. It
is running smoothly. However, some are wondering when we might "hit the
wall".

What has been your experience, and if wrong what did you do? Convert to SQL
Server as a backend? If you converted was it difficult?

Regards,
Leif
.

Relevant Pages

  • Re: Should I worry that my Access to SQL conversion has gone so well?
    ... converting a typical Access application to use SQL Server ... Jet attempts to send all queries to the server ...
    (microsoft.public.access.conversion)
  • Re: convert access crosstab to sqlview?
    ... Just understand that your query uses several issues when converted to SQL ... Some are already mentioned such as SQL Server doesn't support ... >> MS Access MVP ... >>> I am converting a number of things from access qry's to sql views. ...
    (microsoft.public.access.queries)
  • Re: How can I Improve query speed?
    ... soundneedle@hotmail.com (John) wrote ... ... > and play around with. ... I'll need to go from Access to SQL ... > Server. ...
    (microsoft.public.excel.programming)
  • Re: Migrate Windows Sharepoint Services 3.0 to SQL Server 2005
    ... the same server, not converting to SQL 2005. ... for migrating Windows Sharepoint Services 3.0 running on SSEE to SQL ...
    (microsoft.public.sharepoint.windowsservices)
  • Converting from Access to MS SQL Server
    ... What sort of issues arise when converting a database from Access to MS SQL ... because the company wants to take some legacy Access databases and move them to ... the MS SQL Server system. ...
    (microsoft.public.access.formscoding)