Advice On A Project Please

Gethzerion

Registered User.
Local time
Today, 17:24
Joined
Feb 25, 2005
Messages
31
Hi,

Have been asked to "update" an archaic database for a consultancy firm. The existing database is approx 20+ years old and appears to use .DBF files for storing the records.

Now, the DB itself I can do, but I've normally only written DB's for one or two users. So before even considering doing this work, I would be greatful for any advice on the following.

They use a central server linked to 8 user pc's. I assume I will therefore need a FE/BE database. Would it be useful to determine what version of MS Server Client they're using?

Using Standard Access 2000 or above, (i've still to confirm what version they require it written in) can a FE/BE database be created, that will be useable (speed / reliability etc)?, I'm told that they will have ~4 users using the system at any one time. Do I need to consider using SQL Server (and if so what level / version)?

From initial emails, the 4 main .dbf files are 50Mb each. I seem to recall that without using SQL Server, once a standard Access Database starts to exceed 200Mb it starts to cause operational issues. Is this correct?

Lastly, if anyone can point me to a good book / website that discusses the standard coding changes that need to be made when establishing connections etc in VBA for multiple user databases I would be extremely grateful.

Thanks in Advance
 
This should be quite straight forward. Access db can grow to 2GB, so size will not be an issue. You can link to the dbase dbf database then import. Tables in backend and a front for each user should be fine. You could certainly use SQL Server 2005 Express (free) if you wish, but such a small db should run OK on Access.

Chris B
 
Thanks for your quick response. So I can go up to 2GB using a BE of JET/MDB?

If I did decide to use the free version of ACCESS 2005 SQL Server, aren't these freebies only free until used for business???
 
If the FE will be on 8 PCs and quote "(i've still to confirm what version they require it written in)"
then you may want to consider writing it in Access 2007 as the Developer extentions are free to download. This will allow you to install the FE on as many PC as you like without the cost of buying access for each PC.
I use Access 2003 and had to buy visual studio 2005 for this privilage.

Garry
 
Concur with the advice you are getting. For even AC97, 8 users 4 at a time is a piece of cake. On newer machines with newer versions of Access, you are well within the range of an all-Access solution. Yes, I would do a split, FE/BE, to make the system more robust and easier to work with.
 

Users who are viewing this thread

Back
Top Bottom