accdb vs adp

  • Thread starter Thread starter briank
  • Start date Start date
re: new features in ADP for every
version for the past 5 versions." Past 5 versions of WHAT?


Access 2000 - First version
Access 2002 - better UDF / SQL Server support
Access 2003 - pivotTables
Access 2007 - SQL 2005, half dozen other features
Access 2010 - SQL 2008 support

There you are-- new ADP funcitonality in each of the past 5 versions
 
look at the code dude

making your users wait an extra 5 seconds while you copy over lookup
tables, queries? what a joke dude

'the worst software ever written' because it's more efficient to keep
all your tables in one place- where they belong- a database server
that supports SMP, X64, etc

-Aaron
 
Access 2000 - First version
Access 2002 - pivotTables, better UDF / SQL Server support, more
powerful table designer
Access 2003 - XML (because SQL Server is VERY powerful with XML, this
is important), OWC performance improvements
Access 2007 - SQL 2005, half dozen other features (form wizards, etc)
Access 2010 - SQL 2008 support
 
I would say that as a rule, I still prefer using sql server with
access, but the ease with which users can now use SharePoint and
now that SharePoint supports RI between tables, this means a good
number of "lesser" skilled access users will likely prefer
SharePoint over that of sql server.
Click to expand...

For me, it means the end of Jet replication is in sight. The
addition of RI and triggers means that Sharepoint 2010 is sufficient
for maintaining data integrity (it was not before), and vastly
easier ot set up for sharing data between locations with
disconnected users.

I'm still supporting Jet replication as long as folks need it, but
if someone came to me with a new project contemplating using it, I'd
recommend holding off and using A2010 and Sharepoint 2010 instead.
 
"a a r o n . k e m p f @ g m a i l . c o m" <[email protected]>
wrote in
:
Stalking / Harrassment.. uh, what are you talking about?

Legally, it never happened.
Click to expand...

And that's irrelevant to the real world. It *did* happen, and we all
know it, and we're not going to let you forget it as long as you
continue behaving like an idiot, posting garbage, as you are wont to
do.
Thanks for your concern though!
Click to expand...

My concern is that you're back and are going to be making the
newsgroups less useful again. Please stalk someone again so you get
thrown in jail or put back on probation and end up, once again,
prohibited from post in the newsgroups.

That would be good for EVERYBODY.
 
I did try to explain it to you, but obviously your emotional problems are
getting in the way of your ability to comprehend. I guess the medicine
you're taking isn't working. That's a shame. Sorry, but there are people
here that really could use some solutions, and I have limited time, so I
will not bother continuing this discussion with you.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com


message
Jet has no benefit, it causes slower performance and bigger table
scans.

Sprocs, Views, Functions are thousands of times more powerful.

SQL Server - out of the box- allows every user to have a different
copy of the same object if you want.

It's just completely false to claim that Jet has any benefit over SQL
Server.

-Aaron
 
Confusion still reigns.

I suppose your claim that introducing ADPs in Access 2000 can be construed
as a "new" feature for ADPs is valid. You get a point there, and it is
actually kind of clever;
ADPs are in themselves a "new feature". Quite clever indeed. A new feature
by virtue of being new.

Let's say that "better support for UDFs and SQL Server" counts as a "new
feature" and give you that one as well, although I was REALLY hoping you'd
be able to identify an actual "feature",
and not just "better support" for existing functions.

Now we get to some interesting things. "Pivot Tables" were a new ADP
feature in 2003? I won't bet money on it, but I am pretty sure pivot table
support for ADPs was present in 2002.
Maybe you can pull a real citation from a recognized source indicating that
they didn't appear in ADP's until the 2003 version? This is not a big deal,
but the point of this exercise was to
demonstrate your lack of attention to detail, and your inability to be
accurate. On that point, you didn't do so good here, did you?

The last two claimed features are, shall we say, marginal at best. Saying
that "SQL 2005, half dozen other features", and "SQL 2008 support" are
"new features"
in ADP's is really a stretch, is it not? Unless I have been seriously
misled, support for SQL Server is kind of the whole POINT for ADPs! As a
matter of fact, and you may not recall this,
just over a year ago, you, yourself, actually submitted a comment in the
Access Team Blog in which you complained about the lack of full support for
SQL Server 2008 in Access 2007!

That's right, you criticized MS Access development team on this very point.
Your words in that post included the following:

"... How do you guys get away with this?
Do you not communicate between departments?
Do you not have _ANYONE_ that knows anything about SQL Server?
It's time to take ADP seriously--"

Hm, sounds like you were somewhat less than enthusiastic about the way MS
was decreasing its support for ADPs in the Access 2007 version, doesn't it?

If you Bing yourself, you might find the actual Blog post where you said
that. You might also find this statement from the Access Team,
"Access 2007 ADP's will run against SQL Server 2008 but do not support
designing server objects (tables, views, stored procedures, functions and
relationships)."

That, sir, is NOT what I think of as a "new feature". And judging from your
comments at the time, I think YOU didn't consider it that way either.

And, finally, rather than another unsubstantiated claim, wouldn't you have
been better served if you had submitted an actual list
of those "new features" for ADPs that first appeared in Access 2007? Just
one would be okay.

You see, the point is that you were called out on an unsubstantiated claim,
and you responded with yet another one. Sorry, that does NOT fly. You can do
better. If you want to be taken
seriously, you must do better.

In any event, I think the point has been made: you can't really offer any
substantial citations to support your claims, and those things you do offer
are largely marginal.
So, let's not waste any more time on this topic.


George



message
 
Good grief, Aaron, this is not good news for you, man. You are not even
consistent between two posts made minutes apart!

In this one you actually contradict your previous assertion that Pivot
tables were new in 2003. Okay, better late than never.

And I see that you are now listing "form wizards" for ADPs as a new feature
in Access 2007. Do you REALLY want to make that claim?
Maybe you should back off on that one before someone posts the actual
citation showing it to be false.

Again, I assume you would like to be taken seriously, but that is
increasingly difficult to do. It might be smarter of you to just find
another way to release your angst.
Posting in the PNG's seems not to be a good strategy for you. There are, for
example, classes in Yoga and meditation where you might learn to release
some of that stress in a healthier way.
It's just a thought. Best of luck with it in any event.


George

message
news:[email protected]...
 
"a a r o n . k e m p f @ g m a i l . c o m" <[email protected]>
wrote in
m:
Access 2000 - First version
Access 2002 - better UDF / SQL Server support
Access 2003 - pivotTables
Access 2007 - SQL 2005, half dozen other features
Click to expand...

Name 3 of them.
Access 2010 - SQL 2008 support
Click to expand...

That's not an ADP feature at all. It constitutes no change to the
way ADPs work, just integration with the current version of SQL
Server. And, of course, the next version of SQL Server will negate
it (not that it even matters that much.

You neglect to mention in the first three versions of ADPs how many
things were broken, and then fixed, and then reverted. Steve
Jorgensen tried really hard to use ADPs, but as a moving target, and
with flaws with no real workarounds, he gave up. If somebody as
smart as Steve can't make them work, I *know* that *you* can't.
 
have you seen the form wizards in Access 2007?

is it not a new feature?

what are you talking about dude!??!!??!!!

you chastise me for describing the features in every version of
Access.. but the fact of the matter is that you're just pissed off
because the facts contradict some of the BS that the MVPs claim.
 
Perhaps you should shut up and learn how powerful it is-- instead of
making excuses?

Have you ever built a SQL Server UDF?

re: Let's say that "better support for UDFs and SQL Server" counts as
a "new
feature" and give you that one as well, although I was REALLY hoping
you'd
be able to identify an actual "feature",
and not just "better support" for existing functions.
 
David;

Just because you don't respect the new features in SQL Server, doesn't
mean it's not a few feature

Stuff like pivot keyword, stuff like being able to pass around table
variables-- it's priceless, kid!

-Aaron
 
David;

why don't you stop harrassing me, and focus instead on shaking your
fist at the sky because they removed your precious Jet Replication

-Aaron
 
Thanks, Aaron.


"Working with an Access project is very similar to working with an Access
database. The process of creating forms, reports, data access pages, macros,
and modules is virtually the same as that used to create an Access database.

Once you connect to an SQL Server database, you can view, create, modify,
and delete tables, views, stored procedures, user-defined functions, and
database diagrams by using the Database Designer, Table Designer, Query
Designer, Query Builder, and SQL Text Editor. Although the user interface
for working with these database objects is different from the equivalent
database objects in an Access database, it is just as user-friendly. An
Access project also contains many of the same wizards as an Access database,
such as the Form Wizard, the Report Wizard, the Page Wizard, and the Input
Mask Wizard. These Wizards help you to quickly create a prototype or simple
application, and also make it easier to create an advanced application."

If anyone wants to know which version of Access that statement refers to,
you can use this link. (Hint, it is NOT Access 2007.)

http://office.microsoft.com/en-us/access/HP052731031033.aspx





message
 
Dude. **** yourself.

If you're trying to tell me that Access 2007 doesn't have new features
for ADP? Then you're just plain delusional.

Access Data Projects have gotten new features in every editon.

If you don't know the differences between SQL 6.5, 7.0, 2000, 2005,
2008, 2008 R2 and 2010.. Then I can't help you.

But yes, ADP have ten times the features it had 10 years ago.
 
What features did Access 2007 introduce for jet retards?
What features did Access 2003 introduce for jet retards?
What features did Access 2002 introduce for jet retards?
What features did Access 2000 introduce for jet retards?
 
Back
Top