Darryl Collins
Darryl.Collins at coles.com.au
Thu Jul 3 18:21:47 CDT 2008
I have started working in SQL Server 2000 (enterprise version) and whilst I only have limited rights (The DBA's set it all up etc and they have standard templates and scripts to start with) I am really impressed with it - it is a seriously good setup compared to what I have worked with in the past. I have downloaded the express version at home, but it is finding the time to play with it that is tricky (especially since I have a 9 month old son!). Darryl. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Hadyn Morgan Sent: Friday, 4 July 2008 6:43 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] SQL Server Express WAS Article on stuff broken inAccess 2007 I have to say SQL Server 2005 Express is awesome. I am working on converting a second client to it who use largish tables with multiple users and the improvements using pass-through queries and stored procedures have brought the 2003 frontend back up to the speed it was before they tripled their production. Just as an aside, I use SSMS Express for the maintenance and general testing and VS2008 to debug SP's. What other tools should I be using? I have had a look at the Red Gate software and will probably invest in that but I wondered what other tools people found indespensible. Cheers Hadyn -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Steele Sent: Friday, 4 July 2008 5:19 a.m. To: Access Developers discussion and problem solving Subject: Re: [AccessD] Article on stuff broken in Access 2007 I am being forced to work into Access 2007 by two of my clients. One is a branch of a large corporation which has switched completely to Office 2007 as company policy. At the moment 'my' branch is running several Access 2000 BE/FE databases under Access 2007. There have been minor issues, but no significant problems. We will convert over to full Access 2007 databases gradually. The other client is running a network with mixed Access 2003/Access 2007; the owner is a 'bleeding edge technology' fan who is keen to convert fully to 2007 and is also pressuring me to try using SQL Server Express as the BE. We have had some significant problems (like failed updates and bizarre fatal errors) on the machines running Access 2007, but unfortunately most problems have been intermittent and not reproducible on my Access 2007 development system (running in a virtual machine). FWIW, it doesn't seem to matter whether the Access 2007 machines run the FE as an Access 2003 .mdb or a converted Access 2007 .accdb. Doug Steele On Thu, Jul 3, 2008 at 8:06 AM, Charlotte Foust <cfoust at infostatsystems.com> wrote: > Does anyone in this list actually USE A2007? > > Charlotte Foust > > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.