Do you think Access can do it ?!

[Mr.Access]

Hi all ,
I’m going to create a DB that deals with the personnel payroll and administration . the DB will be shared in the server by many employees with an account for some ones for modifying and updating .
Do you think that I can create it efficiently with MS_Access 2003 ?

Best Regards ..

 

[Dennisk]

depends on how many users. I'me sure the experienced posters will come up with different numbers but if you need more than 7-8 users then SQL server would be a better option for the Back end. You now have a number of options.

A) Front end in Access.MDB - Non Client Server to Partial Client Server
B) Front end in Access.ADP - Client Server - Efficient
C) Front in .NET - Client Server.

Client Server basically means that queries are run on the SQL server and ONLY the results are returned.
Non Client Server means all the tables in a query are downloaded to the Client machine before the query is processed.

 

[The_Doc_Man]

Mr. Access, one thing worries me. You don't show your origin.

In the USA, payroll systems must be certified if they deal with payrolls of 15 or more employees. Other countries have similar laws with different size limits and specific regulations on certification methods. Access applications can be certified, but you need to very carefully secure it the MDB before you go for that certification.

On the other hand, to your direct question, Access can surely handle small business needs along this line. Up to several thousand employees would be within reach if you are careful. Beyond this level, SQL Server is preferred.

 

[Mr.Access]

Many thanks for the replies ..

In fact, It’s an administration system rather that a payroll . What I’m worried about is , when I split the mdb to (data file) in the server and an (application file) in the authorized employees’ computers for modifying or just reading ,could there be a problem with the increasing number of the authorized ones synchronizing the shared source in the data file (MS.Acees Database) ?