On Mon, 2008-06-02 at 16:29 -0400, Drew Jensen wrote: > Howdy, > > > Thought some might find this little tidbit of a blog interesting: > > http://blogs.ittoolbox.com/pm/career/archives/microsoft-office-and-microsoft-access-integration-where-does-it-fit-in-your-organization-25091 >
That's a good summary of the situation with Access. I've built some quite complex Access applications for my own use. I've used it as a quick-and-dirty tool to populate some databases where it was easier for me to Just Do It than to ask someone else to write an 'official' program. But I've also seen what can happen when someone writes a small application that somehow becomes business critical. If they leave the company the IT department gets called in and handed an application that they know nothing about and get told that they have to fix or amend it instantly without help from any documentation. We should be considering whether it is possible to deliver the benefits of an Access equivalent without also delivering its weaknesses. As an IT Manager and DBA I would like to see a way of making Base safe for a 'power-user' to use unsupervised. This is not going to be an easy thing to do, if it was Microsoft would already have done it. Here are a few ideas: - When accessing a remote database restrict access to just allow the use of stored-procedures. No hand-written SQL allowed. - Force internal code documentation rules - Integrate Base with a CASE tool so that applications can be generated from the tool, leaving the CASE model as documentation --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
