Stuart McLachlan
stuart at lexacorp.com.pg
Sun Feb 27 17:45:52 CST 2011
If a user is accessing the data in a table in an Access database, you can't modify that table - you get a dialog saying: "You can't open the table 'tblSomething' for modification. A query or form bound to the table is open...." -- Stuart On 27 Feb 2011 at 17:17, Dan Waters wrote: > The reason I asked about data changes was because I wanted to be sure > I surrounded your statement, since I didn't understand it. > > I can make same design changes in an MDB BE as you described for SQL > Server, as long as the BE is in a client-server configuration. What > would prevent you from making design changes in a working MDB BE file? > > Dan > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart > McLachlan Sent: Sunday, February 27, 2011 4:38 PM To: Access > Developers discussion and problem solving Subject: Re: [AccessD] > Access and SQL Server > > Design changes. If you can't make data changes without kicking > everyone out, you must be using the wrong DBMS. > > -- > Stuart > > > On 27 Feb 2011 at 15:43, Dan Waters wrote: > > > Rusty, > > > > Do you mean data changes, design changes, or both? > > > > Dan > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rusty > > Hammond Sent: Sunday, February 27, 2011 3:25 PM To: Access > > Developers discussion and problem solving Subject: Re: [AccessD] > > Access and SQL Server > > > > I would add: Ability to make changes to the backend tables without > > kicking everyone out of the database. > > > > Rusty > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl > > Collins Sent: Sunday, February 27, 2011 3:14 PM To: Access > > Developers discussion and problem solving Subject: Re: [AccessD] > > Access and SQL Server > > > > > > ____________________________________________________________________ > > __ __ _______________ > > > > Note: This e-mail is subject to the disclaimer contained at the > > bottom of this message. > > ____________________________________________________________________ > > __ __ _______________ > > > > > > Tony, > > > > Why I like a SQL server BE. > > > > 1: Performance. It is faster and much more stable, especially if > > set up correctly and over a WAN / LAN. 2: Security of access and the > > actual data itself. 3: Audit: It is dead easy to set up triggers to > > show who changed what, when and from where. 4: Backup and restore is > > better > > cheers > > darryl > > > > > > > > ________________________________________ > > From: accessd-bounces at databaseadvisors.com > > [accessd-bounces at databaseadvisors.com] On Behalf Of Tony Septav > > [iggy at nanaimo.ark.com] Sent: Monday, 28 February 2011 12:43 AM To: > > Access Developers discussion and problem solving Subject: [AccessD] > > Access and SQL Server > > > > Hey All > > Well I have spent a couple of weeks now fooling around with ACCESS > > and SQL Server. Using fairly complex pass through queries, ADO > > connections with stored procedures and Views, I have still to buy > > Susan's book to answer some of my under lying questions. Other than > > being prepared for a client's request to use SQL Server, I keep > > asking myself when would I need to use this. Only a few of my > > applications I have out there are dealing with records greater than > > a million. Because the apps are user specific I don't usually have > > more than 10 users on a network. I don't think any of my clients > > (including the big companies) know what SQL Server is. In fact I > > have produced only one app for a client that linked into an Oracle > > database (that is the flavour in my area not SQL). Yes I know SQL > > Server has hundreds of nifty little features that ACCESS doesn't, > > many activities use a SQL Server link (Web Pages), so it begs the > > question "Should I be learning how to develop a SQL Server app from > > the bottom up?" > > > > What I am finding is that an ACCESS/SQL Server app becomes very code > > intensive (forms, queries, etc) much more so than just using ACCESS. > > > > My question to those of you proficient in using ACCESS and SQL > > Server, how exactly are you applying it? Are you producing major > > apps dealing with millions of records? Are you producing major apps > > dealing with hundreds of users? How do you go about distributing > > changes to an ACCESS/SQL Server app? > > > > > > > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > ____________________________________________________________________ > > __ __ _______________ > > > > The information transmitted in this message and its attachments (if > > any) is intended only for the person or entity to which it is > > addressed. The message may contain confidential and/or privileged > > material. Any review, retransmission, dissemination or other use of, > > or taking of any action in reliance upon this information, by > > persons or entities other than the intended recipient is prohibited. > > > > If you have received this in error, please contact the sender and > > delete this e-mail and associated material from any computer. > > > > The intended recipient of this e-mail may only use, reproduce, > > disclose or distribute the information contained in this e-mail and > > any attached files, with the permission of the sender. > > > > This message has been scanned for viruses. > > ____________________________________________________________________ > > __ __ _______________ > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > ******************************************************************** > > ** WARNING: All e-mail sent to and from this address will be > > received, scanned or otherwise recorded by the CPI Qualified Plan > > Consultants, Inc. corporate e-mail system and is subject to > > archival, monitoring or review by, and/or disclosure to, someone > > other than the recipient. > > ******************************************************************** > > ** > > > > -- > > 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 > > > > > > -- > 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 >