Re: Access 2010 with Sharepoint 2010
- From: "Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx>
- Date: Sat, 14 Nov 2009 21:14:45 -0700
"David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns9CC2905F22C6Df99a49ed1d0c49c5bbb2@xxxxxxxxxxxxxxxxx
It would be more compelling if there weren't already a way to make
that separation and maintain consistency, i.e., a stored QueryDef
with the derived field.
Quite true. however, you are then tied into using that querydef.
Furthermore what happens if some other SharePoint services needs
to use that Full Name expression?. What happens if the team down
in the IT for billing or the folks working with the sap system
needs that list of customers? Again you get to define how that
field is displayed, and it stored in the data.
Then it should be defined in a layer *above* the table, where it
belongs.
Sure, a case can be made that this belongs in some other tier.
On the other hand if they come along and build some new service architecture
then I don't have necessary to communicate with that particular layer. As
long as the data is stored and enforced by the engine level, then it don't
matter what tier or service uses that data. In fact, any service can read
that data DIRECT and will have the correct result.
And just to be clear, this *is* something that's both in Sharepoint
and in the new version of ACCDB, right? That is, it's a new column
type in Access?
Yes, correct, this is a new column type in ACE.
No matter how you slice this, you still saving
processing by doing this, you still centralizing the one place
where this expression exists and will be maintained. You don't
have to care or worried how some other system is going to pull
data out. You don't know or care of that other system has some
type of expression builder. You data is just sitting there ready
to be used and consumed by any conceivable type of application.
That's what the middle tier is for.
As I mentioned, sure, but then again this is just a long time debate
as to if certain things belong in the software side, or at the data
side of things.
You might not want to be forced to use that middle tier.
With this system you don't have to care anymore. Any new system you build
can use that new data column. This kind of debate also been a long time sql
server debate and that of some saying one should avoid things like triggers
and stored procedures as they don't belong at engine level as opposed to the
application level.
There is a lot of pro's and con's in this debate, almost
Like those who debate between auto number primary keys, and that of natural
keys, there is a lot of differing opinions on this issue.
However, no matter which way people debate this issue, there is still some
advantages to be had for this approach and there is a chunk of the IT
industry that has adopted this Philosophical approach, especially for cloud
vendors.
I would never recommend to my clients that they host anything
important on such a service.
Unfortunately my opinion here does not really matter here or change what
consumers and business are doing. I not really giving my opinion here as
much as simply making an Observations as to how people are behaving.
Millions and millions of people use Gmail. Millions are now placing most if
not all of their business processes on systems like eBay. That means
pricing, inventory, sales, payment processing = everything they have is on
eBay, but they don't complain that it not on their own computer.
People are not listing to the recommends not to use cloud systems.
L.A. votes to "Go Google"; pressure shifts to Google and the cloud
http://blogs.zdnet.com/BTL/?p=26641&tag=nl.e539
I can get 100's of articles like the above in which county's and
municipalities and school districts on jumping on this bandwagon.
It not me you have to convince here,
it is the millions and millions of customers that choosing otherwise that
you have to convince. Many people did not believe in the advantages of the
GUI, and they not in this business anymore. This is not our choice, and the
boat left the harbor. As you point out, there still many applications that
are
green screen and were never converted. However, the GUI was not a fad.
That no question that there's tons of legacy green screen application left
over from that era, however we're not seeing you develop a new architectures
and there really no new industry work being created for those legacy green
screen applications. And, they don't solve any of the new business needs
either. The issue is not that there still some green screen applications
being used, or that some are still viable, they don't represent anything in
terms of creating new work or the future of our industry.
people by the millions are making the clout choice, it's not my decision to
make here.
While software as service is going to fit certain kinds of
companies, I think it is not going to fit a large number of them.
Cloud computing
by definition requires offline editing or it's useless (since you're
dead in the water if the Internet is down)
Most business today generally shutdown without their phones, or without
electricity . In fact, most of my customers, if their internet is down, they
very much
can't work and tend to all go home...
I've been heavily committed to Windows Terminal Server andremote desktop access for a very, very long time, so perhaps my
clients have been getting the majority of the benefits from the
standpoint of access without using this particular buzzword
technology.
Yes, but on the other side, there not a architecture that scales to
millions of
users at a reasonable cost. Sure the customer side gets thin client with TS,
but on the supply side it would be far too expensive to have human labor to
setup the individual servers etc..
The "new" cloud operating systems such as
azure have the ability to censure, build and put on line computers with the
correct services you need. They do this dynamic in real time. So, they
tend to have a top level system called the "fabric controller" that goes out
to the millions of computers, and figures out which ones has the correct
services your
software needs. If your software needs some particular type of database
system such as sql server, then the top level management systems system
will go out and get the best available resources that are currently running,
and if they're not running, then it'll will start those services up on most
readily available computers.
Again, all this stuff is not a buzz word, it's a different way and different
architecture of doing things and accomplishing that goal which allows you to
deliver software as a service **and** supply those services at a very low
cost.
So, cloud computing is all about utility computing just like electricity
is). So, yes, TS has the benefits, but does not have an architecture that
truly scales like Amazon's , or Google, or now azure. Those systems are
built from the ground up to scale on demand.
Here some reading on Amazons service:
http://aws.amazon.com/ec2/
and, here is some on Azure:
http://en.wikipedia.org/wiki/Azure_Services_Platform
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
.
- Follow-Ups:
- Re: Access 2010 with Sharepoint 2010
- From: David W. Fenton
- Re: Access 2010 with Sharepoint 2010
- References:
- Access 2010 with Sharepoint 2010
- From: Bob Alston
- Re: Access 2010 with Sharepoint 2010
- From: Albert D. Kallal
- Re: Access 2010 with Sharepoint 2010
- From: David W. Fenton
- Re: Access 2010 with Sharepoint 2010
- From: Albert D. Kallal
- Re: Access 2010 with Sharepoint 2010
- From: David W. Fenton
- Re: Access 2010 with Sharepoint 2010
- From: Albert D. Kallal
- Re: Access 2010 with Sharepoint 2010
- From: David W. Fenton
- Re: Access 2010 with Sharepoint 2010
- From: Albert D. Kallal
- Re: Access 2010 with Sharepoint 2010
- From: David W. Fenton
- Re: Access 2010 with Sharepoint 2010
- From: Albert D. Kallal
- Re: Access 2010 with Sharepoint 2010
- From: David W. Fenton
- Re: Access 2010 with Sharepoint 2010
- From: Albert D. Kallal
- Re: Access 2010 with Sharepoint 2010
- From: David W. Fenton
- Access 2010 with Sharepoint 2010
- Prev by Date: Re: Export to Excel
- Next by Date: Re: Access 2010 with Sharepoint 2010
- Previous by thread: Re: Access 2010 with Sharepoint 2010
- Next by thread: Re: Access 2010 with Sharepoint 2010
- Index(es):
Relevant Pages
|