Enterprise deploying of MS Access applications

[Poweruser]

I have an MS Access 2007 frontend (with VBA code as business logic), linked to a MSSQL backend database. Currnetly I am using the Access 2007 developer extensions to create an installer (using the package solution wizard).

But I think I have some security problems + I want to update the application more easily.

I hope you have some best-practice solutions to the following problems:

a) If I install the application on a client it creates an *.accdr file. Is this file secure (no change of the layour or the code possible?)

b) How to secure the link to the MSSQL backend. The database password seems to be in the accdr-file as clear text.

c) How to update the application more easily? If i send a new packaged version, users have to uninstall the old version first (by using control panel -> software). I want them to double click on the installer, showing them "update" or "remove" (like office 2007 if you start setup with an older version of office installed). Is there any way to accomplish this?

d) Are there any other secuirty issues I don't see?

What is the best-practice?

Best regards,
D.R.

[Delerna]

Not really on topic but worth considering.

I have a similar development environment as you and it is for the reasons you mention that I have moved away from access to intranet based solutions where multi user access is required. Point C IS the biggest reason that made me change.

I still use access in some situations but I have found I can do anything that I could have done with access and I have enough of a code base now that I can do it just as easily as I could have with access.
Additionally, there is no extra expense for my company because I use nothing but standard html and asp for everything.
I find I can easily control and vary the level of access to a page that any logged in user gets and there is no way they can get access to the asp code.
All they get is the data that asp sends to them.

Updating is a breeze, just change the page and there it is next time they log on
You do have to be careful with caches however.

Anyway, just one persons opinion.

[Poweruser]

Thank you very much, but I don't want to change to ASP.NET at this point. Customers are "used to access", and I think they like it. I know Office 2010 brings a converter, maybe I reconsider my decision then.

But what is the best practice for access 2007 here and now?

Best regards,
D.R.

[GazMathias]

Anyway, just one persons opinion.

Nope, mine too!

Gaz

[Poweruser]

Okay, okay :-)

Please return to topic! Thank you!

Best regards,
D.R.

[Poweruser]

Is there really no "good" way to deploy MS Access applications? I always thought MS Access is enterprise ready ... : (

Best regards,
D.R.

[d4zza]

I've seen a solution being used with a batch file being initiated during startup script for domain users whereby the batch file removes an MDE front-end from the local hard drive, and copies the new MDE front-end to that location.

I'm not too familiar with how the technique works exactly cause server stuff ain't my bag, but if you or someone you know is, then this might be a possible solution.

I've also wondered about having the MDE file on a network location for all users to access, with a shortcut on user's local hard drive, but I've never seen or heard of this so I assume it can't be done.

[Megalog]

I've posted instructions in the past for using batch files to update the local FE file with the latest copy from the network everytime users start the program.
(more info at: FrontEnd on Server or Local?)

As far as having a real nice updateable install file, that lets you Update/Remove, I haven't seen anything that lets you package it like that. Microsoft doesnt really support Access distribution as well as they should (the developer's deployment tool for access is too outdated).