Access Good or Bad 3

[nszczepanski]

Hello all,

I just took on a new job with a new company and they seem to use MS Access for a variety of functions. I am not an Access expert by any stretch but I need to know the negatives of using Access. If we upgrade windows can this cause Access to crash? Also, does Access have the ability to run a normalized DB that enforces referential integrity? Can an Access DB be backed up easily? My plan is to migrate off Access to something more stable. I guess I don’t trust Access and Microsoft. If anyone has any suggestions or any information with your experiences with Access it would be appreciated.

Thanks….

 

[nszczepanski]

Thanks all for the response. We use MS Access and it keeps causing problems by crashing, and sometimes the password protection does not work. I am assuming the file get corrupt somehow. I have been dealing with AS400 and Oracle applications for years and have never had these types of problems/instability issues. I have also implements a system using SQL Server 2000 which I think might be the best back end solution I have ever used. I wanted to get your "takes" because people who have experience using Access are the SMEs. However I don't think Access's intended purpose was derived by Microsoft as an "enterprise" solution that is the reason for SQL Server.

We have 450k PAR for this project and I think I am going with SQL Server. If any of you are SQL server experts let me know I will be hiring some job shoppers for this.

Thanks again all.

 

[jrbarnett]

nszczepanski,

I understand your reasons now. For SQL Server specialists, there are several SQL Server forums on Tek-Tips which are worth visiting who know far more about it than I do.

You should be aware that Tek-Tips does not allow professional recruitment on its site.

John

 

[Pampers]

Hi nszczepanski (MIS),
If your Access-application keeps giving trouble, it is either not well programmed or the environment it is working in is not suitable (to many concurrent users for example). As an in between solutions you can split your database and move your tables (and create maybe some views and stored procedures) to an MsSqlServer2000/2005 backend. Doing this you can already start using the security system of SqlServer and maybe you database will not corrupt so easily.

However I don't think Access's intended purpose was derived by Microsoft as an "enterprise" solution...

. That maybe true, but the ADO Object Model is. And since you can use this model within Access you can also build powerfull business solutions within Access. Especially when you start building unbound applications and distributed n-tier applications.

Of course Visual Studio 2005 will take a lot of coding burding from you if you want to make n-tier applications.

Pampers
Keeping it simple can be very difficult

 

[nszczepanski]

Thanks all you have all been a huge help! I respect all of you and your vast knowledge of Access. I appreciate your kind comments and advice.