Access project

  • Thread starter Thread starter Claire
  • Start date Start date
C

Claire

Hi

I am developing what is becoming a rather large (250MB)
database that is installed on a network. Data might not be
input very often but reports could be viewed or printed
fairly frequently.

Do I NEED to convert this database into a project? If so,
does anybody have any recommendations on how to go about
it, or what kind of issues to look out for?

If I don't convert it, is the database going to corrupt
fairly frequently?

I'm not sure if SQL server is available but lets assume it
is.

Thanks a bunch.
Claire
 
Hi

I am developing what is becoming a rather large (250MB)
database that is installed on a network. Data might not be
input very often but reports could be viewed or printed
fairly frequently.

Do I NEED to convert this database into a project? If so,
does anybody have any recommendations on how to go about
it, or what kind of issues to look out for?

No, I'd say you don't. 250MB is largish but it's still less than an
eighth of Access' capacity. If you do convert it, it'll be a fair
piece of work - for instance if you have any table or fieldnames with
blanks you should remove the blanks; you'll want to change all your
Forms to unbound forms; write VBA code to populate them... etc. etc.

It's also perfectly possible (in fact rather common) to use a .mdb as
a frontend to a SQL database, without making it into an ADP project.
If I don't convert it, is the database going to corrupt
fairly frequently?

Not if you're careful. See
http://www.granite.ab.ca/access/corruptmdbs.htm for some guidelines to
minimize corruption.
I'm not sure if SQL server is available but lets assume it
is.

SQL will provide several advantages: rollbacks, journaling, more
flexible security, Stored Procedures and Views. This comes at a cost
in terms of the labor to manage it and (especially) to convert an
existing JET database. Simply switching an Access database to use SQL
tables will probably cause a dramatic SLOWING of performance and
likely other problems as well - you'll need to do a fairly thorough
redesign.
 
Thanks very much for the input John.

I absolutely do not know enough VB to undertake such a
conversion so I will definitely check out the site you
recommended for avoiding corruption.

Cheers,
Claire
 
Back
Top