the future for Access?

[jlute]

With all of the web development going on and the lean towards web-
based applications in general - what's the future for Access? Will it
continue to be a viable database tool or will it die a quick and
painless death at the hands of Oracle, ASP.net, and the like?

Interested in any opinions.

Thanks!

 

[aaron_kempf]

Oracle?

Oracle has no friggin future kid.
Check out these sites

www.tpc.org
www.olapreport.com/market.htm

The future is _NOT_ web development.
And ASP.net is _NOT_ the future of web development.

The future of web development is php/mysql.

Access is a great tool-- you can use it over the internet, VPN,
wireless; WAN; etc.
Of course-- I'm talking about ADP, not MDB / ACCDB.

Because MDB / ACCDB don't work over _ANY_ networks reliably-- hell yah
you should grow up and lose the training wheels.

-Aaron

 

[boblarson]

Access 2007 (and beyond) is designed to integrate with SharePoint Services
and therefore CAN be used as a Web Application with the front end on the
user's machine and the data residing on the Internet/Intranet. This is the
path that Microsoft is moving towards.

You can also use an Access backend file with ASP.NET.


--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com

__________________________________

 

[jlute]

Interesting stuff, so far. I hope to hear more opinions. I'm curious
about gathering a more general idea from a diverse group of users.

I can attest that Access is HORRIBLE over our WAN. Forget about it.
Maybe a small database of 5-8 MB's but my "monster" database with a BE
and FE both over 40 MB's is an absolute nightmare over our WAN.

 

[Cheyanne]

hi Hannah!

 

[boblarson]

Access was NEVER intended to be used on a WAN:

http://members.shaw.ca/AlbertKallal/Wan/Wans.html



--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com

__________________________________

 

[Arvin Meyer [MVP]]

The only way that Access can be used over a WAN is with a web front-end or a
Terminal Server. Unless it's a small application (40 MB is small) with less
than 20 or 30 users, you'd be better off with a SQL-Server back-end and a
web front-end over a WAN. Access shines on a LAN not on a WAN.

 

[aaron.kempf]

Just because _YOUR_ piece of crap database doesn't work on a WAN-- it
doesn't mean that _ACCESS_DOES_NOT_WORK_OVER_A_WAN_.

Microsoft Access works great over a WAN.
_IF_ you simply upsize your db to SQL Server and ADP-- you'll be
amazed with how flawlessly it runs over the WAN.

Shit, do you want me to _EMAIL_ you an ADP and you can run it over the
public internet?

Stop making excuses for the stupid fucking loser database that these
assholes try to con you with.

ACCESS MDB / ACCDB is DEAD and it has been for a decade.

-Aaron

 

[aaron.kempf]

ADP works _FLAWLESSLY_ over a WAN.

Stick a fork in it; _LIAR_.

Terminal Services is a bigger waste of money than even _ORACLE_.

-Aaron

 

[aaron.kempf]

Dude that dipshit can't even differentiate between KiloBYTE and
KiloBIT.

A 56 KILOBIT modem can deliver 7 KILOBYTE per second.

And you guys listen to this idiot?

GET REAL.

Access works great over _ANY_ wan. It's JET that sucks balls.

-Aaron


---------------
And, all those cool commercials about how fast high speed internet is
compared to phone lines are correct. A 56k dial up line is rated at .
056. Actually, the phone line is closer to about .04 (you never get an
actual 56k connection). So, high speed internet is about 1/.04 = 25
times faster then phone dialup. And, yes those TV commercials are
about right when they say they are about 30 times faster then your
dialup line. So, we have;

Office network = 100

High speed internet = 1

Dialup modem = .04
-------------------

Access was NEVER intended to be used on a WAN:

http://members.shaw.ca/AlbertKallal/Wan/Wans.html

--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials athttp://www.btabdevelopment.com

__________________________________






- Show quoted text -

7

 

[aaron.kempf]

You can take your sharePoint shit and shove it dog.

SharePoint is a _CON_. I mean; it doesn't support 10k records in a
list!!
Why would I move from one _HANDICAPPED_ database to another?

Seriously!

Would you rather have

Access on top of SharePoint on top of SQL Server
or
Access on top of SQL Server

I mean.. 2 layers or 3 layers.. which -- by definition- is more
efficient?

-Aaron

 

[aaron.kempf]

Again-- upsize to SQL Server and use an ADP.

These people around here aren't smart enough to follow a simple
wizard.

-Aaron

 

[aaron.kempf]

PS - Microsoft has published-- in many places-- that they STRONGLY
suggest that you do not use access MDB for a website.

It's kinda like having fiber optics run to your mailbox.. and then use
dialup to get to your mailbox

 

[Rick Brandt]

With all of the web development going on and the lean towards web-
based applications in general - what's the future for Access? Will it
continue to be a viable database tool or will it die a quick and
painless death at the hands of Oracle, ASP.net, and the like?

Interested in any opinions.

Thanks!

If/when Access dies it will be neither quick nor painless.

In my opinion the future of web development against databases will be flash
and silverlight based. I currently build web apps with AJAX front ends
against Java web services interacting with either SQL Server or UDB400
databases.

It's good stuff, but it's awkward or (in some cases impossible) to support
all browsers on all platforms. With Adobe Flex (runs inside the flash
plugin) you get full support in any environment that supports the flash
engine (which is pretty wide support these days) and you get the same
appearance and behavior in all of them. If silverlight can do the same (and
not just run in Internet Explorer) then I expect it will get a large chunk
of this pie as well.

 

[NetworkTrade]

Web based is more (much more) expensive and with many other considerations,
including firewalls, dns names, etc.

Also one should not confused web based, with remote accessibility. Not all
remote accessibility is or needs to be web based. One can
tunnel/vpn/terminal server as if you are actually in the office. You don't
need to make something web based to offer remote accessibility.

Oracle, DB2, SQL Server are like 18 wheelers; while Access is like a PickUp
truck. It is not lesser technology per se - primarily it is a smaller size.
Access is a very viable vehicle for small business, non profits, and
departmental use. Access would not disappear due to the web development
industry any more than would Excel. It is not a technology question - it is
a market segment issue.

 

[Tony Toews [MVP]]

The only way that Access can be used over a WAN is with a web front-end or a
Terminal Server. Unless it's a small application (40 MB is small) with less
than 20 or 30 users, you'd be better off with a SQL-Server back-end and a
web front-end over a WAN. Access shines on a LAN not on a WAN.

Actually David Fenton reported good results with a NY state wide 100
Mpbs LAN. Although I do agree using SQL Server would make me a lot
more comfortable.

I would not recommend ADPs as they haven't been enhanced in a few
releases now.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

Again-- upsize to SQL Server and use an ADP.

Upswing to SQL Server sure. ADPs not recommended as they haven't been
enhanced in the last few releases of Access. In other words they're a
dead end.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

With all of the web development going on and the lean towards web-
based applications in general - what's the future for Access? Will it
continue to be a viable database tool or will it die a quick and
painless death at the hands of Oracle, ASP.net, and the like?

Access will not die even a slow, painful death. It will be usable for
many years to come. Others have expounded on why.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

Actually David Fenton reported good results with a NY state wide 100
Mpbs LAN.

Make that 100 Mbps. And I guess that would be considered a WAN.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Arvin Meyer [MVP]]

Make that 100 Mbps. And I guess that would be considered a WAN.

That would make it the same speed as a Fast Ethernet LAN, which should pose
no problems for Access.