[AccessD] Article on upgrading

David McAfee davidmcafee at gmail.com
Fri Jul 29 11:30:55 CDT 2011


1. The ability to write comments in the SQL

2. The ability to do changes to data in the back end, without requiring a FE
change.
I know most will say that you can do this in Access too, but the FE should
be for
presentation of the data and a place to enter the data. Need to change a
view or sproc?
Change it, and as long as input parameters haven't changes, to tweaking is
needed in the FE.

3. Speed

4. Ability to use UDF's

5. Stored Procedures!

6. Triggers, even though I try not to use them. I feel if the system is
designed correctly,
    there is no reason for a trigger. Now if a system, such as an ERP, has
stored procedures
    which are not allowed to be modified, then I can see a reason to use a
trigger for a table
    that gets updated.

7. The ability to run scheduled jobs and back ups each night

8. The ability to email from the BE if certain conditions are found (new
record found during a job ran at midnight)

9.  Case statements in SQL

I'm sure I can think of more reasons to use SQL :)







On Thu, Jul 28, 2011 at 4:40 PM, Darryl Collins <
darryl at whittleconsulting.com.au> wrote:

> Triggers, Hell Yeah
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
> Sent: Friday, 29 July 2011 7:30 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Article on upgrading
>
> I completely agree with Gustav's points, with one addition (that I can
> think of right now), and that would be database driven business logic.
>
> Ie, a record is put into table 1, then a record in table 2 is modified.
> Triggers.
>
> Drew
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
> Sent: Thursday, July 28, 2011 1:29 PM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] Article on upgrading
>
> Hi Susan
>
> Nice to see back doing tech writing!
>
> We've never had a client asking why, they all follow my advice(!)
> So our reasons to suggest and upgrade:
>
> 1. Extreme reliability is requested. I have yet to see an SQL Server
> break down.
> 2. Remote access (across a WAN) is needed.
> 3. Easy, daily, and reliable backup is requested even when clients are
> on-line.
> 4. Database size can be expected to outgrow Access' capability.
> 5. Controlled and secure user access is requested.
>
> Note the non-tech level of these parameters.
>
> /gustav
>
>
> >>> ssharkins at gmail.com 28-07-2011 18:54:58 >>>
> I'll be writing about upgrading to SQL Server and I'd like to include as
> many of you in it as possible -- you'll get credit and a link -- it's a
> nice thing to show the boss and clients.
>
> The angle is -- questions you should ask when deciding whether to
> upgrade an Access database to SQL Server (Express is Okay too) --
> specific to the decision-making process. Anything you think someone
> considering the move should evaluate before doing so -- but I'll be
> writing it from a "questions you should ask" perspective.
>
> It'll be interesting reading for the list too I think, so if nobody
> objects -- I see no reason to ask for these responses off list.
>
> Thanks!
> Susan H.
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> The information contained in this transmission is intended only for the
> person or entity
> to which it is addressed and may contain II-VI Proprietary and/or II-VI
> Business
> Sensitive material. If you are not the intended recipient, please contact
> the sender
> immediately and destroy the material in its entirety, whether electronic or
> hard copy.
> You are notified that any review, retransmission, copying, disclosure,
> 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.
>
>
> --
> 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
>



More information about the AccessD mailing list