[AccessD] Could somebody expand on this a little?

Steve,

  Andy doesn't seem to know much about Access.  You should have read his
last Access article, which I and a few others commented on.  Here's the
link:

http://www.sqlservercentral.com/columnists/awarren/diggingintoaccessperforma
nce.asp

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Steve Erbach
Sent: Monday, January 30, 2006 7:53 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Could somebody expand on this a little?


Dear Group,

I read a recent SQL Server Central article by a fellow named Andy
Warren that dealt with connecting to a SQL Server database using an
Access MDB/ODBC connection.  The article very nicely laid out the
step-by-step process -- with screen shots -- to accomplish this.  What
made me curious about the article was that the author never mentioned
ADP's.

So I joined the discussion forum for this topic and read a number of
interesting replies pro and con for MDBs vs. ADPs, some that I'm
unable, from only my own experience, to evaluate.

Here's one of them.  The forum member started his message by saying
that the article was good.  He went on to say:

~~~~~~~~~~~~~~~~~~~~~~~~
"Two problems I've come across:

"1) Nice three table view with calculated fields fully updatable in
SQL server - lots of lovely triggers. Put it in an adp - not a chance.
Put it in an mdb with the primary key set, fully updatable. Hmm!

"2) Same view, all the base tables have audit triggers to check who
changes important fields. T SQL is based on

"IF UPDATE(fieldname)
write to audit table

"This works fine with T SQL, but use Access and every field is marked
as dirty and you get all the relevant fields written to the audit
table. I've had to resort to

"IF (SELECT fieldname from inserted) != (SELECT fieldname from deleted)

"I'd love to use a project if only it worked"
~~~~~~~~~~~~~~~~~~~~~~~~

Can anyone comment on this?

Also, the author chimed in saying that he would do a followup article
in the same vein using ADP's.  He also said:

"I tend to use the mdb over the adp format, just from habit as much as
anything. I could entirely be wrong, but doesnt using the ADP format
remove the use of module code? It does expose procs and triggers,
which the mdb's do not."

I honestly have only used ADP's to allow easier access to table
contents and for making simple data entry forms...no heavy-lifting
code at all.  He can't be correctly, surely, in saying that ADP's
"remove the use of module code," can he?

Regards,

Steve Erbach
Scientific Marketing
Neenah, WI
www.swerbach.com
Security Page: www.swerbach.com/security
http://TheTownCrank.blogspot.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com